Thanks for the reply.
When I set the quick_abort_min directive to be a large number such as 1000 KB, then I see that the files are getting cached as expected. Hence it seems that quick abort is indeed the problem.
Can you give more details about how Squid determines that the client has aborted. Even though the socket connection is alive, I see that Squid determines that the connection is aborted.
What can client do (any specific header for example) to prevent squid from thinking that the client is aborting?
Thanks Marc
From: Henrik Nordstrom <[EMAIL PROTECTED]> To: osuser os <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED], <[EMAIL PROTECTED]> Subject: Re: [squid-users] Squid 2.5 and Range requests Date: Sun, 25 Apr 2004 23:12:35 +0200 (CEST)
On Sun, 25 Apr 2004, osuser os wrote:
> >The default setting is to abort any downloads when the client disconnects
> >if more than 16 KB remains when the client disconnected.
>
> I see the same behavior even if the client sends "Proxy-Connection:
> Keep-alive" header. Squid is also responding with "Proxy-Connection:
> Keep-alive" and the connection is not aborted. But the file still doesnt get
> cached.
> Is there any way of modifying the default setting to abort the download?
See the quick_abort_* directives.
Regards Henrik
_________________________________________________________________
Stop worrying about overloading your inbox - get MSN Hotmail Extra Storage! http://join.msn.com/?pgmarket=en-us&page=hotmail/es2&ST=1/go/onm00200362ave/direct/01/
