On 26.09.2012 17:48, Philip Martin wrote: > Mark Phippard <markp...@gmail.com> writes: > >> I have always been skeptical of the ability to put a cache in front of the >> SVN server. Wouldn't something like this keep a cache from working >> properly? How would a cache know about that header we added and that the >> content we returned to the client cannot be cached? I presume we set >> something in the response that an intelligent cache would look at and know >> that it cannot cache the response. But that effectively means the cache >> would only provide some value on checkout? > I'm no expert but I expect that the cache has to take account of the > significant headers: it could cache multiple versions of the GET one for > each X-SVN-VR-Base. If that is how it is expected to work then perhaps > getting the client to use the lasst changed revision instead of the > current revision would make the cache more effective.
This is how the cache /should/ work, according to any number of HTTP specs. Unfortunately, most proxies that I know about don't attempt anything as "advanced" as that. -- Brane -- Certified & Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
