shibboleth-dev - Re: [Shib-Dev] Last-Modified vs Etag for metadata modification checking
Subject: Shibboleth Developers
List archive
- From: Kaspar Brand <>
- To:
- Subject: Re: [Shib-Dev] Last-Modified vs Etag for metadata modification checking
- Date: Thu, 04 Dec 2008 08:06:55 +0100
> So, my general question is, should I be checking the Etag or the
> Last-Modified header in order to detect changes?
If the server provides an ETag header in his response, then you should
(or MUST, as per RFC 2616, actually) use that one:
> HTTP/1.1 clients:
>
> - If an entity tag has been provided by the origin server, MUST
> use that entity tag in any cache-conditional request (using If-
> Match or If-None-Match).
Otherwise you should use If-Modified-Since (provided that the server's
response had a Last-Modified field).
Setting both If-Match/If-None-Match and If-Modified-Since in a request
has an "undefined" result according to the spec.
Kaspar
- Last-Modified vs Etag for metadata modification checking, Chad La Joie, 12/03/2008
- Re: [Shib-Dev] Last-Modified vs Etag for metadata modification checking, Kaspar Brand, 12/04/2008
- Re: [Shib-Dev] Last-Modified vs Etag for metadata modification checking, Chad La Joie, 12/04/2008
- Re: [Shib-Dev] Last-Modified vs Etag for metadata modification checking, Kaspar Brand, 12/04/2008
Archive powered by MHonArc 2.6.16.