Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of tjw@omnigroup.com designates
 198.151.161.1 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: If-Match not supported with PROPFIND?
From: Timothy Wood <tjw@omnigroup.com>
In-Reply-To: <5062BBEB.10004@gmx.de>
Date: Wed, 26 Sep 2012 08:41:32 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <58ED47AA-DC51-4804-B9D2-BEFF4E2AF7AB@omnigroup.com>
References: <DF878447-D307-4DB8-A097-713859B45344@omnigroup.com>
 <5062BBEB.10004@gmx.de>
To: "dev@httpd.apache.org" <dev@httpd.apache.org>


On Sep 26, 2012, at 1:25 AM, Julian Reschke <julian.reschke@gmx.de> =
wrote:
> RFC 4918 defines it as a header field that applies to any method (same =
as all RFC 2616 conditional header fields).

Right, which is why I was hoping it would work with PROPFIND.

> 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.

In this case, the change is adding new member being added to a =
collection. Apache does change the ETag in this case (verified in the =
litmus patch), so the If and If-Match headers should work as predicates.

-tim