Bug 43679

Summary: Contributed tests for checking that subrequests take into account directives found in .htaccess, <LocationMatch>, and <Directory>
Product: Apache httpd-2 Reporter: Jose Kahan <jose>
Component: CoreAssignee: Apache HTTPD Bugs Mailing List <bugs>
Status: RESOLVED LATER    
Severity: enhancement Keywords: MassUpdate, PatchAvailable
Priority: P2    
Version: 2.2.6   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
URL: http://mail-archives.apache.org/mod_mbox/httpd-dev/200710.mbox/%3c20071001144439.GA13145@rakahanga.inrialpes.fr%3e
Attachments: perl framework tests for verifying that subrequests take into account directives found in .htaccess, <LocationMatch>, <Directory>

Description Jose Kahan 2007-10-23 06:56:24 UTC
I'm resubmitting this contribution, originally sent to the apache-dev mailing 
list. At least bugzilla keeps a record :)

These tests check that the directives inside <LocationMatch>, 
<Directory> sections as well as .htaccess are taken into
account when processing internal subrequests. The test
case consists in using AddCharset to add a bogus charset in the
configuration and using conneg to trigger a subrequest. e.g.,

       <LocationMatch  "^/apache/subrequests/location_override/">
          Options +MultiViews
	  AddCharset bogus .bc
       </LocationMatch>

Although there are six tests, only test four fails when
PR 41960 is not applied. I added the extra five just to make 
sure the flaw won't appear in the other sections.

You will find here attached a diff file against the svn trunk version
of the perl test framework.

Feel free to request further changes.

-jose
Comment 1 Jose Kahan 2007-10-23 06:57:44 UTC
Created attachment 21024 [details]
perl framework tests for verifying that subrequests take into account directives found in .htaccess, <LocationMatch>, <Directory>

svn made against trunk
Comment 2 William A. Rowe Jr. 2018-11-07 21:08:45 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.