-
Bug
-
Resolution: Done
-
Major
-
httpd 2.4.23 ER2, httpd 2.4.23 CR4, httpd 2.4.23 SP1 DR3
-
None
When we call http://127.0.0.1/abc/3.2/js/abc-3.2-47E.js
and the related is not present, even with different case, we should have a HTTP 404.
But what we have today is a HTTP 300 with the following proposal:
Multiple Choices
The document name you requested (/abc/3.2/js/abc-3.2-47E.js) could not be found on this server. However, we found documents with names similar to the one you requested.
Available documents:
/abc/3.2/js/abc-3.2-42.js (common basename)
/abc/3.2/js/abc-3.2-57D.js (common basename)
/abc/3.2/js/abc-3.2-25A.js (common basename)
/abc/3.2/js/abc-3.2-68E.js (common basename)
/abc/3.2/js/abc-3.2-79A.js (common basename)
/abc/3.2/js/abc-3.2-81A.js (common basename)
/abc/3.2/js/abc-3.2-52.js (common basename)
/abc/3.2/js/abc-3.2-25B.js (common basename)
The following bug [1] states the Directive CheckBasenameMatch to use.
[1]https://bz.apache.org/bugzilla/show_bug.cgi?id=44221
After looking into the jboss-ews-2.1.0 Apache httpd source code it looks by default WANT_BASENAME_MATCH is hard coded and is not configurable. There isn't any "CheckBasenameMatch" directive available.