hello!
thank you for all the answers!
yes, this is an big need for us because we are using pound as loadbalancer for a big tomcat farm and tomcat clusters.
currently it works with the cookie option, but if a client has cookies denied he could not login to the application.
the applications are using cookies as primary storage place for the jsessionid. if this is not possible the application passes the jsessionid to the client via hidden parameter.
we are using pound as load balancer because it is more scaleable as an apache ajp13 load balancer.
apache is slowing down if there are more den 650 active sessions. as i have read in the apache documentation
the newer module mod_proxy_ajp should be better BUT pound does not cache the connections!
and this is an great advantage because if an backend dies it will not try to cache the connections until he self dies like apache do (out of session, the hole loadbalancer dies).
so pound runs without problems even the last clusternode dies and not before!
so if it will not be too difficult to implement such an session option it would be an great advantage for pound.
if you want i can test beta releases in our tomcat test cluster if this feature will be present.
thank you very much for all you help!
mario
2007/9/13, Ted Dunning <tdunning@veoh.com>:
This is a very common mechanism on Tomcat based servers.
On 9/13/07 9:19 AM, "Robert Segall" <roseg@apsis.ch> wrote:
> ...[cookies disabled pushes jsessionid into query string] ...
> Adding a session option to support this would not be too difficult, but
> is it worth it? Who needs this?
--
To unsubscribe send an email with subject unsubscribe to
pound@apsis.ch.
Please contact roseg@apsis.ch for questions.