Bug 475787 - mod_proxy_balancer: strange behaviour of multiple session identifiers
Summary: mod_proxy_balancer: strange behaviour of multiple session identifiers
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: httpd
Version: 5.3
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Luboš Uhliarik
QA Contact: BaseOS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-10 14:31 UTC by Josef Zila
Modified: 2021-01-14 09:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-27 13:28:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Josef Zila 2008-12-10 14:31:57 UTC
Description of problem:
see Bug 439218
when httpd is configured to stickysession=BALANCED|balanced session identifier works for both lowercase and uppercase variant, but if there is stickysession=balanced|BALANCED, it seems to work only for lowercase.
 
Version-Release number of selected component:
httpd-2.2.3-22.el5

How reproducible:
see Bug 439218

Actual results:
with stickysession=balanced|BALANCED, only "balanced" works as session identifier.

Expected results:
with stickysession=balanced|BALANCED, both lowercase and uppercase variant should work as session identifier, as it does with stickysession=BALANCED|balanced.

Comment 1 Jan Kaluža 2011-10-19 10:16:00 UTC
I'm not sure what your configuration was exactly, but I'm not able to reproduce it. The part before '|' is the name of the cookie and latter one the name of the url parametr. This has to be to set to values used by loadbalanced server (Tomcat for example...).

So for example tomcat uses "JSESSIONID" as cookie name and "jsessionid" as url parametr, therefore it has to be "JSESSIONID|jsessionid".

What server have you used together with apache and in what configuration?

Comment 3 Jan Kaluža 2013-03-27 13:28:27 UTC
We've been unable to reproduce this internally; I'm closing this bug.


Note You need to log in before you can comment on or make changes to this bug.