Summary: | Certain types of encoding generate proxy errors | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | Mark <mark> |
Component: | mod_proxy_balancer | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 2.2.3 | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | other |
Description
Mark
2007-02-14 12:26:32 UTC
Here's another sample URL that results in "Not Found" from mongrel (serving the Rails app with Apache as the reverse proxy frontend) which means that Apache with mod_proxy_balancer somehow doesn't like the encoded forward slash char (%2F). If we remove that / char (as encoded), the URL works fine. % /articles/show/127139-Date+In+The+Title+-+Test+4%2F27 Actual URL looks like this /articles/show/127139-Date+In+The+Title+-+Test+4/27 Forgot to mention that in that last example with the forward slash encoded char, Apache sends the request to mongrel, but it's returned as not found. However using the encoded URL via wget directly to the mongrel server works fine. Somewhere along the line Apache is messing up the request. |