|Summary:||<Limit> Does Not Apply When URI Is Folder|
|Product:||Apache httpd-2||Reporter:||Brandon Kirsch <brandonkirsch>|
|Component:||Core||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
Description Brandon Kirsch 2011-12-08 20:06:10 UTC
I'm using the following <Limit> configuration to always allow OPTIONS requests for any path. Trouble begins when a client asks for OPTIONS for any URI that maps to an existing folder. Files, 404s and folders without a trailing slash remain unaffected. # Contrived (but literal!) httpd.conf snippet gets the point across <Location /> Deny from all <Limit OPTIONS> Allow from all Satisfy any </Limit> </Location> Trouble begins when a client asks for OPTIONS for any URI that maps to an existing folder. Example client requests and the Apache response: Client: OPTIONS /isAFile HTTP/1.1 Apache: 200 OK Client: OPTIONS /doesNotExist HTTP/1.1 Apache: 200 OK Client: OPTIONS /doesNotExist/ HTTP/1.1 Apache: 200 OK Client: OPTIONS /isAFolder HTTP/1.1 Apache: 301 Location: /isAFolder/ (mod_dir behavior) Client: OPTIONS /isAFolder/ HTTP/1.1 Apache: 403 Forbidden (PROBLEM RESPONSE!) Correct responses (200 OK) are given to all requests for files or non-existent files or folders. Correct responses (301 Redirect) is also given to requests for real folders that are missing the trailing slash. A problem response occurs when the URI 1) Maps to a real folder and 2) Contains a trailing slash. Summary: I cannot get Apache to always allow OPTIONS requests that map to real folders. I just compiled and installed a vanilla 2.2.21 build on Linux to verify that the problem exists without any third party modules loaded.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:07 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.