You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2006/05/15 17:20:10 UTC

DO NOT REPLY [Bug 38357] - mod_proxy_balancer doesn't support sticky session

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38357>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38357


brectanu@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|2.2.0                       |2.2.2




------- Additional Comments From brectanu@gmail.com  2006-05-15 15:20 -------
So, the backend server is responsible for adding the .route?  This needs to be
documented better.  Here is what the docs do say route is (no mention of who
sets this route or that the separator is a dot)...

"route - Route of the worker when used inside load balancer. The route is a
value appended to seesion id."

Also, I don't think that this works very well.

* Dot seems to be a bad separator
  - mod_usertrack uses dots and thus incompatible
  - Many other vendor session ids use dots
  - Need a way to change that seperator to something else?
  - Maybe option to store route in it's own var/cookie by proxy server?
  - Maybe use last dot, not first dot?  After all, you are appending to the
session id value, not prepending.

* If backend must add route, then it means that the app server (or app) must be
aware that it is being balanced.
  - I don't think that is a valid assumption
  - Some vendor app servers may not allow the addition of route
  - Changing the proxy config requires changes to the backend servers
  - Proxy server knows what route that was used and should be able to append the
value, then strip it off before proxying the request (the backend server may not
like it there).  Backend server has no way of knowing what arbitrary route you
used on the proxy side.
  - Maybe set env var to route value (and/or member value) that was used in the
proxy server so this info can be used to append the .route if the backend is not
capable of it?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org