incomplete upload to bzr.dev

[James Henstridge]

On 21/03/06, Martin Pool <mbp at sourcefrog.net> wrote:
> > From the server side, sending "Cache-Control: proxy-revalidate" or
> > "Cache-Control: must-revalidate" in the response headers might help
> > for the specific case of bzr.dev.  That doesn't help bzr with any
> > other branches though.
> >
> > As far as request headers, "Cache-Control: max-stale=0" might make a
> > difference.  I don't know if there is a way for a client to instruct
> > the cache to revalidate.
>
> Yes, there is 'Cache-control: must-revalidate' -- but we already send
> that and it doesn't seem to be respected.

That's because "must-revalidate" is defined as a value for the
Cache-Control response header rather than the Cache-Control request
header (i.e. it is something sent by the http server rather than http
client).

There are some details here:
    http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9

James.