RE: caching 206 responses

>-----Original Message-----
>From: Christian Schöniger [mailto:christian.schoeniger@fes-aes.de]
>Sent: Monday, June 26, 2000 3:30 PM
>
>Hi,

Hi,

>is there any way to force squid v2.2.STABLE3 to cache
>responses with a status code of 206 (Partial Content) ?

i guess there isn't any way completely, at least now. But there is a detail
about this.

Changes to Squid-2.0 (October 2, 1998):
- changed the way Range requests are handled:
                - do not "advertise" our ability to process ranges at
                  all
                - on hits, handle simple ranges and forward complex
                  ones
                - on misses, fetch the whole document for simple ranges
                  and forward range request for complex ranges
          The change is supposed to decrease the number of cases when
          clients such as Adobe acrobat reader get confused when we
          send a "200" response instead of "206" (because we cannot
          handle complex ranges, even for hits) Note: Support for
          complex ranges requires storage of partial objects.

>Does squid support the required "Range and Content-Range
>headers" according to RFC2616 ?

If it supports it. It could cache responsed 206 Partial Content.

>If not, can squid prevent partial GET requests and do "normal"
>requests instead?
In here I do not understand what you mean. But Squid has already prevented
partial GET requests.

Greetings from Istanbul,
Ilker G.
Received on Mon Jun 26 2000 - 09:02:34 MDT