Re: [SQU] hit on a pending transfer

From: Henrik Nordstrom <hno@dont-contact.us>
Date: Wed, 14 Feb 2001 10:22:43 +0100

The normal action is to hit the pending transfer, not to open yet
another retreival.

This problem only happens if the pending transfer is not cacheable, or
if the new request is a no-cache request.

--
Henrik Nordstrom
Squid hacker
Chandrasekhar KRISHNAN wrote:
> 
> Hi all,
> 
> Apparently, when Squid receives request for an object that it is still
> retrieving, it creates a new StoreEntry and starts a new transfer with the
> origin server. I'd expect Squid to mark it as a hit and use the same
> StoreEntry structure for both the requests. Is there some easy way to
> achieve this or does the source code need to be changed?
> 
> Thanks,
> Chandrasekar Krishnan
> 
> Graduate Student,
> Department of Computer Science,
> Rutgers University,
> New Jersey.
> 
> --
> To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
Received on Wed Feb 14 2001 - 02:37:41 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:58:00 MST