incomplete upload to bzr.dev

[Martin Pool]

On 21 Mar 2006, James Henstridge <james.henstridge at gmail.com> wrote:
> On 21/03/06, Martin Pool <mbp at sourcefrog.net> wrote:
> > I'm going to do a few things now:
> >
> >  * Try to confirm this is the problem
> >
> >  * See if there are any additional headers we can set in urllib or
> >    pycurl to get the right behaviour.  I'm not too optimistic; Microsoft
> >    ISA is pretty bad.
> 
> >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.

-- 
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060321/765e739e/attachment.pgp