Hello,
Can two separate web sessions going to the same IP address share the same
TCP session?
We are having a problem when two different clients go through squid
(2.3.STABLE4-hno.20000819) to access a web site that is load-balanced
through an F5 BIG-IP box to two web servers. The BIG-IP is using cookies to
get the user back to the same web server each time, so once a user has
established a session with a web server they will be routed back to the same
web server each time.
Here's the problem: User1 logs on to web server A and waits. Now User2
logs on to web server B. The next time that User1 accesses a web page the
request is sent on User2 TCP session to web server B.
We were able to do a trace and see that coming from the squid proxy User1's
first access of the web page happened from port 3017 on the squid box.
User2 session came from port 3018 on the squid box. While User2's requests
are still happening, the following User1 requests were also passed along
User2 TCP session coming from port 3018 -- which is destined to web server
B.
Is squid doing this on purpose? I could see that there might be a
performance gain by sending data to the same web server over one TCP
session. But in this case, the one ip address of the web server is actually
two web servers, and we need the users to be routed back to the same web
server. Is it possible to stop this?
Thank you much for the help...
-Dan Schuster
-- To unsubscribe, see http://www.squid-cache.org/mailing-lists.htmlReceived on Thu Feb 01 2001 - 15:27:04 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:57:45 MST