RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1172226 - stickysessions on ProxyPass doesn't work if balancer is defined outside vhost
Summary: stickysessions on ProxyPass doesn't work if balancer is defined outside vhost
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: httpd
Version: 6.7
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Luboš Uhliarik
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 1172231
TreeView+ depends on / blocked
 
Reported: 2014-12-09 16:24 UTC by Aaron Ogburn
Modified: 2021-01-14 09:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-24 14:57:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
proposed patch (4.78 KB, patch)
2014-12-10 12:32 UTC, Jan Kaluža
no flags Details | Diff
proposed patch v2 (4.86 KB, patch)
2014-12-12 13:48 UTC, Jan Kaluža
no flags Details | Diff

Description Aaron Ogburn 2014-12-09 16:24:52 UTC
Description of problem:

StickySessions doesn't work for mod_proxy_balancer when sticky sessions is defined on a ProxyPass in a vhost, and the balancer is defined outside of the vhost.


Version-Release number of selected component (if applicable):

httpd-2.2.15-39.el6.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Configure a simple balancer like so outside of a vhost with a ProxyPass in a VHost:

<Proxy balancer://mycluster>
    BalancerMember http://localhost:8080 route=node1
    BalancerMember http://localhost:8081 route=node2
</Proxy>
<VirtualHost *:80>
     ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid
</VirtualHost>
2. curl -H "COOKIE: JSESSIONID=foo.node2" localhost
3. Note that stickiness for the above request is not maintained.  Debug logging can confirm no sticky logic is applied.

Actual results:

No stickiness is maintained.

Expected results:

Stickiness is maintained.

Additional info:

This can be avoided by just putting the balancer in the VHost instead with the ProxyPass, or putting "ProxySet stickysession=JSESSIONID|jsessionid" in the balancer when outside of the VHost.

Comment 1 Jan Kaluža 2014-12-10 12:32:31 UTC
Created attachment 966765 [details]
proposed patch

Comment 2 Jan Kaluža 2014-12-12 13:48:30 UTC
Created attachment 967641 [details]
proposed patch v2

Comment 4 Joe Orton 2015-11-24 14:43:02 UTC
On reviewing this we are concerned about the possible impact on backwards compatibility.  Customers could be running with configurations which happen to work because the vhost-specific settings are not applied to the balancers.  Changing the behaviour here could break, or cause surprising behavioural changes to, working configurations.

Given that the workaround required to achieve the desired behaviour is relatively simple, I'm going to decline this bug in RHEL 6.  The fix to the merging behaviour is committed upstream, so will work through into a future RHEL eventually.

Comment 5 RHEL Program Management 2015-11-24 14:57:00 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.


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