Summary: | ProxyPass regex destination is not recognized | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | Alexandre Schaff <alexandre.schaff> |
Component: | mod_proxy | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 2.4.37 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
Alexandre Schaff
2018-10-29 16:22:54 UTC
It probably should be ProxyPassMatch in this case, apr_fnmatch_test() is just a easy try to "fix" a ProxyPass, but there is no way to do that absolutely anyway (e.g. "/api" is a valid regex although it won't match the same if it's used as a path or a regex). (In reply to Yann Ylavic from comment #1) > It probably should be ProxyPassMatch in this case, apr_fnmatch_test() is > just a easy try to "fix" a ProxyPass, but there is no way to do that > absolutely anyway (e.g. "/api" is a valid regex although it won't match the > same if it's used as a path or a regex). Thank you Yvan, this makes sense. Expecting ProxyPass to "fix more" is not the solution. |