Thank you so much, Henrik I really want the persistent connection between Squid and my server because my server dosen't support application level session ID and I use TCP connection ID (socket) to keep talk to my client application until the server or client close the connection. But if our customer choice Squid as their proxy server and Squid dosen't support persistent connection, We will get trouble to the communication.
Would you please let me know if there is a way to set Squid to keep persistent connectiion to send multi requests in one TCP connection if I use other HTTP method but not POST? How about GET or CONNECT or ...? But GET method can not carry large data, but POST do. Other issues are concerned to performance of my server if Squid don't support persistent connection. Best Regards, Chi Sun -----Original Message----- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Thursday, December 11, 2003 1:06 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [squid-users] Squid2.4 supports persistent connection, but why Squid2.5 or Squid3.0 not. On Wed, 10 Dec 2003 [EMAIL PROTECTED] wrote: > Could you let me know how Squid2.5 or 3.0 can keep a TCP connection to allow > client and server send requests and responses in one TCP connection? Works here... But please remember that Squid is a proxy and persistent connections are a hop-by-hop feature of HTTP. There is no guarantee that the next client request will be forwarded to the same server connection. Squid simply selects the best connection to use for forwarding the request. Ah, now I realise what your problem is. You are looking at the POST method. Due to complications on non-indempotent requests in case of server-side timeouts of persistent connections Squid-2.5.STABLE2 and later does not use persistent connections for POST or other "non-indempotent" requests This is also strongly recommended in the HTTP/1.1 specifications for the same reasons. <url:http://www.squid-cache.org/Versions/v2/2.5/bugs/#squid-2.5.STABLE1-inde mpotent>. Regards Henrik
