Re: What squid does with no cacheable pages?

Thanks for your answer. But being the way you told for
non cacheable pages, Squid doesn't cause any temporary
caching overhead to the user? The only overhead it
causes is the forwarding of data from the origin
server directly for the client?

Regards,
    Leandro

--- Henrik Nordstrom <hno@squid-cache.org> wrote:

> On Wed, 21 Sep 2005, Leandro Scott R.Z. Jacques
> wrote:
>
> > Well, what I want to know is if squid does a
> temporary cache and then
> > forwards that temporary cached page for the client
> and then deletes it
> > from the cache or if squid only makes a bridge
> between the client and
> > the server simply forwarding all the data read
> from the server directly
> > for the client not making any temporary cache.
>
> It's more like a application level bridge in that
> case. On all cache
> misses Squid forwards the response while it is being
> received, only
> waiting for the HTTP headers before the response
> starts to be sent to the
> client.
>
> If the object is cacheable then while this is done a
> copy is also written
> to disk for later reuse by another client. (there is
> also some caching in
> memory, but the basic principle is similar)
>
> Regards
> Henrik
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Received on Wed Sep 21 2005 - 08:35:30 MDT