On Sep 15, 2006, at 12:29 AM, Plüm, Rüdiger, VF EITO wrote:
-----Ursprüngliche Nachricht----- Von: Sander Temme Gesendet: Freitag, 15. September 2006 01:02 An: [email protected] Betreff: Re: load balancer and http(s) sticky sessions On Sep 14, 2006, at 3:49 PM, Ruediger Pluem wrote:On 09/14/2006 06:14 PM, Jim Jagielski wrote:That's what I'm thinking, sort of like an 'autostickysession' attribute. We could even have it default to cookies but add something like 'autostickysession=url' to force URL rewriting and adding a tag to the end of the URL (for sites that don't like cookies)....I guess URL rewriting can be tricky when you have no idea of the application on the backend. How do you handle POST requests?Wouldn't we get the pathinfo back that we tack onto the action attribute of a form?But what if you need to switch the backend due to a failure there and adjustthe routing information?
Same as when the LB session ID comes in as a cookie? The pathinfo would contain the same or similar information as the cookie and be used for the same purpose. I don't know if we want to put explicit route information in the tag in the way we do now (cookievalue.route) or keep that state on the server, but the result would be the same.
What happens today when a request arrives with cookie value.tomcat1 and tomcat1 is out of commission? It gets routed to tomcat2, right?
S. -- [EMAIL PROTECTED] http://www.temme.net/sander/ PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF
smime.p7s
Description: S/MIME cryptographic signature
