Re: caching 206 responses

Henrik Nordstrom schrieb:
>
> No, Squid does not (yet) support caching of 206 responses.
>
> Yes, it can be tuned to issue normal non-range requests instead. See
> range_offset_limit in squid.conf.
>

I've tried this tag before, with
- range_offset_limit 10 MB and
- range_offset_limit -1 ( which should fetch the whole object from the
beginning )
and with the default, but it seems to me, that it has no effect at all,
the result
in the access.log is always the same. something like:
... TCP_HIT/000 65471 GET http://site_to_cache/.../doc.pdf - NONE/- -
... TCP_MISS/206 167804 GET http://site_to_cache/.../doc.pdf -
DIRECT/side_to_cache
    multipart/x-byteranges
If, because of the 206 thing, caching of pdf-files doesn't work, which
proxy software
else can I use on a Linux box?

> Ps. It would be nice if people actually did a search for relevant
> keywords in squid.conf.default every now and then...
>
> --
> Henrik Nordstrom
>
> Christian Schvniger wrote:
> >
> > Hi,
> > is there any way to force squid v2.2.STABLE3 to cache
> > responses with a status code of 206 (Partial Content) ?
> > Does squid support the required "Range and Content-Range
> > headers" according to RFC2616 ?
> > If not, can squid prevent partial GET requests and do "normal"
> > requests instead?
> >
> > chris
> > christian.schoeniger@fes-aes.de
Received on Tue Jun 27 2000 - 01:43:30 MDT