Bug 46830 - Directive AllowEncodedSlashes seems not to be documented correctly
Summary: Directive AllowEncodedSlashes seems not to be documented correctly
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 2.2.0
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: HTTP Server Documentation List
URL: http://httpd.apache.org/docs/2.2/mod/...
Depends on:
Reported: 2009-03-10 11:33 UTC by Dennis Birkholz
Modified: 2011-03-17 14:48 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Birkholz 2009-03-10 11:33:56 UTC
If "AllowEncodedSlashes On" is set in the global context, it is not inherited by virtual hosts. You must explicitly set "AllowEncodedSlashes On" in every <VirtalHost> container. I think this should be documented as it took me a while to find that out!
Comment 1 Dan Poirier 2009-03-10 14:31:14 UTC
It seems to me that the behavior of AllowEncodedSlashes is wrong.  The documentation for how the different configuration sections are merged (http://httpd.apache.org/docs/2.2/sections.html) says "Sections inside <VirtualHost> sections are applied after the corresponding sections outside the virtual host definition. This allows virtual hosts to override the main server configuration."

This sounds to me as if the configuration in the main server ought to apply to the virtual host as well, unless overridden in the virtual host.

Comment 2 Dennis Birkholz 2009-03-10 21:05:59 UTC
I agree with you, Dan, that AllowEncodedSlashes does not work the way it should according to the section merge order. But my primary intention is to document the way AllowEncodedSlashes actually works.
The bug in the merge order can than be fixed later, i don't think this has a high priority.
Comment 3 Rich Bowen 2010-10-29 11:05:38 UTC
Moving docs bugs to docs@httpd.a.o ownership.
Comment 4 Dan Poirier 2011-03-17 14:48:45 UTC
Changed in trunk and next 2.2 release, hopefully in a way that will satisfy most users.  

AllowEncodedSlashes On still decodes slashes, but new option AllowEncodedSlashes NoDecode will allow the slashes and not decode them.  

Doc has been updated, so closing doc bug as well.

trunk r1082196
2.2.x r1082630