W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2010

Re: Age response header and HTTP/1.0 requests

From: Adrien de Croy <adrien@qbik.com>
Date: Tue, 06 Apr 2010 14:50:13 +1200
Message-ID: <4BBAA165.40003@qbik.com>
To: Mark Nottingham <mnot@mnot.net>
CC: Eric Lawrence <ericlaw@exchange.microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>

sorry to cry wolf... turns out it was another problem in our filtering 
API.  Looks like IE is behaving fine.

apologies again

Adrien


On 6/04/2010 1:43 p.m., Mark Nottingham wrote:
> HTTP/1.1 caching headers are perfectly valid in HTTP/1.0 responses; e.g., if a 1.0 cache is in front of a 1.1 server, it can't know which headers to strip, and a client has to be able to handle the response (indeed, it will still be interested in these headers, and the 1.1 caching model is designed with this scenerio in mind).
>
> I'm having a bit of trouble reproducing this, however; if I browse with IE8 (cache cleared) behind a HTTP/1.0 proxy (Squid), a 200 response with a non-zero Age header is displayed correctly -- even if it spans multiple packets.
>
> Cheers,
>
>
>
> On 06/04/2010, at 11:11 AM, Adrien de Croy wrote:
>
>    
>> Hi all
>>
>> I'm finding some odd behaviour with browsers when serving from cache to an HTTP/1.0 request.
>>
>> I'm finding IE8 disconnects after the first buffer if the Age header is present (this is the only difference between success and failure scenarios).
>>
>> So, do we need some text in the http1.1 bis caching document about sending cache headers in respect of the version of the request?  E.g. safety issues of sending HTTP/1.1 headers back to an HTTP/1.0 response.
>>
>> Regards
>>
>> Adrien
>>
>>      
>
> --
> Mark Nottingham     http://www.mnot.net/
>
>
>    
Received on Tuesday, 6 April 2010 02:50:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:17 GMT