Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of julian.reschke@gmx.de
 designates 213.165.64.22 as permitted sender)
Message-ID: <5062BBEB.10004@gmx.de>
Date: Wed, 26 Sep 2012 10:25:15 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: dev@httpd.apache.org
CC: Timothy Wood <tjw@omnigroup.com>
Subject: Re: If-Match not supported with PROPFIND?
References: <DF878447-D307-4DB8-A097-713859B45344@omnigroup.com>
In-Reply-To: <DF878447-D307-4DB8-A097-713859B45344@omnigroup.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 2012-09-25 04:38, Timothy Wood wrote:
>
> My reading of the WebDAV spec leads me to believe that PROPFIND should support If-Match, but trying it and looking at the code for dav_method_propfind() I don't see a call to dav_validate_request(), dav_meets_conditions() or ap_meets_conditions().
>
> Is my reading of the spec incorrect, or is this an oversight? I guess I'll work up a patch!
>
> Thanks!

RFC 4918 defines it as a header field that applies to any method (same 
as all RFC 2616 conditional header fields).

That being said, as ETags and timestamps do not necessarily change on 
WebDAV property changes, using it with PROPFIND may be tricky. And, as 
you have seen, support is likely to be spotty.

Best regards, Julian