Bug 51491 - mod_dir breaks POSTs to URLs not ending in /
Summary: mod_dir breaks POSTs to URLs not ending in /
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_dir (show other bugs)
Version: 2.2.17
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2011-07-08 19:58 UTC by eboregelna
Modified: 2018-11-07 21:09 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description eboregelna 2011-07-08 19:58:35 UTC
The HTTP spec *requires* a user agent to use GET or HEAD in a redirected request if it is not using user interaction to confirm otherwise. (http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3)

A redirect of a POST not ending in a / is therefore likely to corrupt the intent of the request, or at the very best result in an ungainly request for user interaction.

Therefore I believe mod_dir should be configured by default *NOT* to redirect POST requests.

This is encountered quite often and without reasonable workarounds IMO when using a framework such as Sling where POST requests to a directory with a trailing / mean something usefully different from a request without a trailing /.

Yes it can be made to work by explictly disabling or configuring DirectorySlash off for the relevant URLs. But other uses of the same URL prefix may benefit from DirectorySlash. And configuration of Apache shouldn't be needed to avoid a behavior that is more often than not disruptive.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:01 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.