Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Subject: Re: thoughts on ETags and mod_dav
From: Henrik Nordstrom <henrik@henriknordstrom.net>
To: dev@httpd.apache.org
In-Reply-To: <470EF739.8040004@pearsoncmg.com>
References: <470E9A9F.8020202@pearsoncmg.com>
	 <470EF739.8040004@pearsoncmg.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="=-q5FNHgq5uOjZ4PkYUw+P"
Date: Fri, 12 Oct 2007 14:49:40 +0200
Message-Id: <1192193380.12138.9.camel@henriknordstrom.net>
Mime-Version: 1.0


--=-q5FNHgq5uOjZ4PkYUw+P
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On fre, 2007-10-12 at 00:25 -0400, Chris Darroch wrote:

>    RFC 2616 section 14.24 (and 14.26 is similar) says, "If the request
> would, without the If-Match header field, result in anything other than a
> 2xx or 412 status, then the If-Match header MUST be ignored."  Thus in
> the typical case, if a resource doesn't exist, 404 should be returned,
> so ap_meets_conditions() doesn't need to handle this case at all.

There is more to HTTP than only GET/HEAD.

If-Match: *
and
If-None-Match: *

is quite relevant only taking 2616 into account

Most notably If-None-Match in combination with PUT, used for creating a
new resource IFF one do not already exists.

The first examples of PR #38024 is also quite speaking for itself on
If-Match: *.

Regards
Henrik

--=-q5FNHgq5uOjZ4PkYUw+P
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iQCVAwUARw9tYUNPQ5Kbx8daAQKPhwQAkItducRZB5AMvC9Z2AqqSEMsjQ9xGg7D
35k6VwzB3/bhxRlir9PJ9xE3Q1CzF2Viw802b7ahvfxVuUWGr6nQIoIHrKHXm7mZ
V5PQ3EyCLap/Gfeo9j80hVxf87AIGxzqusRx5ZbYC1oyrH3WXc1BZNUgF8QgqzHz
G3nZHDWuxPQ=
=2w+p
-----END PGP SIGNATURE-----

--=-q5FNHgq5uOjZ4PkYUw+P--