On Sun, Jan 27, 2002, Li Xiang wrote:
> Hi, all:
>
> >From my knowledge, squid now does not cache the reply of range request
> (HTTP 206). I have heard that such support will be available in the coming
> version, say 2.5 or 2.6. Is that true adn how is that going on? And if
> possible, can anyone give me some rough idea that how the new squid handle
> such partial reply? Like if an object is 100K, and one range request of
> 1-50k issued, how will cache deal with the object? And if later request
> asks for 1-60k, what will happen? Seems the newest version trys to fetch
> the whole object even if the request is a partial one. Will that be
> changed?
Hi,
range replies aren't cacheable in squid25 and I doubt that it'll
be implemented in squid26.
To be perfectly honest, until the internals are reworked range
reply caching/aggregation isn't likely to happen. So unless
someone else has any ideas .. :-)
Part of the reworking (which I'm slowly doing) will involve the
range requests being totally uncacheable - ie, all objects
with a Range header will be passed through rather than the
entire object being read and a part returned. THAT should
be in squid-HEAD soon.
Adrian
Received on Sun Jan 27 2002 - 01:49:26 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:05:57 MST