DO NOT REPLY [Bug 7988] - Include variables not inherited correctly in mod_include

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7988>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7988

Include variables not inherited correctly in mod_include

paul@murph.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|mod_autoindex               |mod_include
            Summary|DOCUMENT_URI incorrect in   |Include variables not
                   |mod_autoindex header        |inherited correctly in
                   |                            |mod_include



------- Additional Comments From paul@murph.org  2002-04-14 19:33 -------
I have done a bit more digging and found that this problem is not mod_autoindex 
specific, but more mod_include specific, so have changed the description 
from "DOCUMENT_URI incorrect in mod_autoindex header" to "Include variables not 
inherited correctly in mod_include" and updated the category accordingly.  My 
patch to revert to 1.3.x behaviour for mod_autoindex does not fix the problem I 
have discovered with nested include files.

I have also set up some more specific test pages at 
http://www.murph.org:81/test/ (Apache 1.3.22) and http://www.murph.org:82/test/ 
(Apache 2.0.35) (my port 80 server is now 2.0.35).

The variables which should be inherited from the document requested by the user 
(not necessarily the current .shtml file) are:

    DOCUMENT_NAME 
    DOCUMENT_URI 
    LAST_MODIFIED 

This behaviour is documented at:

    http://httpd.apache.org/docs-2.0/mod/mod_include.html#includevars


The main reason for me wanting this behaviour is to have a standard footer 
included as <!--#include virtual="/include/footer" --> on each page (using 
MultiViews as well so that I can change the type and/or language of the footer 
file at a later date, if desired, without updating all of the individual pages).