Bug 51127 - Make ProxyPassReverseCookiePath work as expected
Summary: Make ProxyPassReverseCookiePath work as expected
Status: RESOLVED DUPLICATE of bug 48295
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy_http (show other bugs)
Version: 2.5-HEAD
Hardware: All All
: P3 normal with 3 votes (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL: http://httpd.apache.org/docs/trunk/mo...
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 17:08 UTC by Luke Meyer
Modified: 2018-05-28 18:17 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Luke Meyer 2011-04-27 17:08:05 UTC 
Refer to 51126 for details. In 2.2, this directive doesn't work like ProxyPassReverse. Given this directive:

ProxyPassReverseCookiePath / /apps/

I would expect that if the backend creates a cookie with path /example, the directive would rewrite it to /apps/example. Instead, it is written to /apps/ on the proxy.

If my backend had a bunch of apps with different paths (/app1 /app2 /app3 etc) and each wanted a separate cookie, I'd need a separate directive for each.

I expect this change might break some < 2.3 configurations, but at least it could go in trunk for the next major release.
Comment 1 Christophe JAILLET 2018-05-28 18:17:16 UTC 

*** This bug has been marked as a duplicate of bug 48295 ***