Re: Last-Modified HTTP header from mod_dav_svn

On Fri, Nov 25, 2005 at 10:57:31PM +0200, Kalle Olavi Niemitalo wrote:
>...
> However, if a "casual HTTP browser" contacts a Subversion repository,
> it will be using GET, which could be cacheable.

Yup.

>...
> I suppose there could be two advantages with reporting Last-Modified
> in addition to ETag:
>
> - Perhaps some older caches support Last-Modified but not ETag.
>
> - A cache can guess an expiry date based on how long the resource
> has already been unmodified.
>
> - RFC 2616 section 13.3.4 says servers SHOULD do so.

This last part is good enough. We have the date, so we may as well put
it into the response (depending upon the type of resource, of course).

For (at least) version resources, we should also be setting the
Cache-Control header. The max-age should be set to some ridiculously
high number since a version resource can't change.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org