Search squid archive

Re: Persistent Server connections, pipelining and matching responses

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Chad - Thanks. How does it work for a single client that has pipelining
implemented. If two GET requests are sent to the server and if
hypothetically  ( a poorly implemented) server responds only to the second
GET, how does squid (and the client) map the response to the second request
? If squid happens to cache that response, any subsequent client requesting
that resource could get the wrong page served. This is possible right ?
Essentially, squid continues to depend on the "sequence" of the responses
from the origin server and has no way of matching responses to particular
request (even from the same client). 

Thanks,
-- 
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Persistent-Server-connections-pipelining-and-matching-responses-tp2540989p2541220.html
Sent from the Squid - Users mailing list archive at Nabble.com.


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux