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 2011/04/27 23:08:07 UTC

DO NOT REPLY [Bug 51127] New: Make ProxyPassReverseCookiePath work as expected

https://issues.apache.org/bugzilla/show_bug.cgi?id=51127

           Summary: Make ProxyPassReverseCookiePath work as expected
           Product: Apache httpd-2
           Version: 2.3-HEAD
          Platform: All
               URL: http://httpd.apache.org/docs/trunk/mod/mod_proxy.html#
                    proxypassreversecookiepath
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: mod_proxy_http
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: lmeyer@vmware.com


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.

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

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