[PATCH] httprepo: long arguments support (issue2126)

Martin Geisler mg at aragost.com
Tue Mar 29 08:23:54 CDT 2011


Laurens Holst <laurens.nospam at grauw.nl> writes:

> Long answer:
>
> HTTP caches don’t just blindly return the last result for the same
> URL. First, it only returns a cached copy if one of three caching
> headers were set by the server (so no unsolicited caching is done by
> HTTP, see section 13.4), and if the method and certain headers match.
> Which headers match is indicated by the Vary header on the cached
> response, and iirc some headers are also included by default.
>
> Now Mercurial itself does not currently cache responses to its http
> requests at all.

We do send back ETag headers when you browse hgweb, see

  https://bitbucket.org/mirror/mercurial/src/tip/mercurial/hgweb/common.py#cl-178

It computed from the mtime as you suggest :)

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://aragost.com/en/services/mercurial/blog/


More information about the Mercurial-devel mailing list