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 2009/02/04 16:26:40 UTC
DO NOT REPLY [Bug 46665] New: Regexp parsing problem in
ProxyPassMatch
https://issues.apache.org/bugzilla/show_bug.cgi?id=46665
Summary: Regexp parsing problem in ProxyPassMatch
Product: Apache httpd-2
Version: 2.2.11
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: mod_proxy
AssignedTo: bugs@httpd.apache.org
ReportedBy: gerard2.chevalier@schneider-electric.com
I setup a proxy to a tomcat server and I have problem with the ProxyPassMatch
directive.
If I write :
ProxyPassMatch ^(/.*\.page)$ ajp://hostname:8009$1
then I get the following error :
Syntax error on line 573 of C:/Program Files/Apache Software
Foundation/Apache2.2/conf/httpd.conf:
ProxyPass Unable to parse URL
I noticed that it is the concatenation of hostname + port + $1 that causes
trouble.
If I remove :8009 or $1, the directive can be parsed, but of course it is not
what I want !
I found the following workaroud :
ProxyPassMatch ^/(.*\.page)$ ajp://hostname:8009/$1
That makes it work.
Do you confirm that the initial syntax should work ?
--
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
DO NOT REPLY [Bug 46665] Regexp parsing problem in ProxyPassMatch
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46665
Nick Kew <ni...@webthing.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Platform|PC |All
Resolution| |WONTFIX
OS/Version|Windows XP |All
Severity|normal |minor
--- Comment #3 from Nick Kew <ni...@webthing.com> 2009-08-27 01:48:32 PDT ---
Thanks for the report and analysis.
Fixing this would be disproportionately disruptive, so instead I'm documenting
it and pointing to this bug report for explanation and workaround ideas.
Marking WONTFIX.
--
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
DO NOT REPLY [Bug 46665] Regexp parsing problem in ProxyPassMatch
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46665
--- Comment #2 from Tim Funk <fu...@apache.org> 2009-08-26 11:55:01 PDT ---
I just noticed this error occurs regardless whether one is using ajp or not.
The docs for ProxyPassMatch give this reference:
^(/.*\.gif)$ http://backend.example.com$1
But if backend.example.com is on a non-default port - you get the error
"ProxyPass Unable to parse URL" - for example:
ERROR
ProxyPassMatch (/foo.+) http://backend.example.com:2829$1
But if you add a / after the port and before the regex substitution, then all
is OK (as long as the regex is fixed so as no to provide an extra prefixed / )
OK
ProxyPassMatch /(foo.+) http://backend.example.com:2829/$1
--
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
DO NOT REPLY [Bug 46665] Regexp parsing problem in ProxyPassMatch
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46665
--- Comment #1 from Dan Poirier <po...@pobox.com> 2009-02-04 08:29:04 PST ---
Looking at the code, the proxy does try to parse the second parameter as a URL
before ever substituting anything into it, so your workaround makes sense.
I don't know the proxy well enough to say if it's necessary for it to work that
way, though.
--
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