Bug 34405 - adds DOCUMENT_NAME_WITHOUT_SUFFIX to mod_include
Summary: adds DOCUMENT_NAME_WITHOUT_SUFFIX to mod_include
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_include (show other bugs)
Version: 2.1-HEAD
Hardware: Other All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate, PatchAvailable
Depends on:
Blocks:
 
Reported: 2005-04-11 19:36 UTC by David McKellar
Modified: 2018-11-07 21:08 UTC (History)
0 users



Attachments
diff -u mod_include.c-old mod_include.c (517 bytes, text/plain)
2005-04-11 19:37 UTC, David McKellar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David McKellar 2005-04-11 19:36:18 UTC
Using server side includes (SSI) <!--#echo var="DOCUMENT_NAME"--> the basename
of the path is available.
Usually, the name ends with ".shtml".  The dot means the name can't be used for
some purposes.
This patch adds <!--#echo var="DOCUMENT_NAME_WITHOUT_SUFFIX"--> which can be
used as a javaScript or
Style Sheet variable name.  This example uses it to automatically
make the "you are here" link red:

<style type="text/css">
#<!--#echo var="DOCUMENT_NAME_WITHOUT_SUFFIX"--> { background-color: red }
</style>

<td id="index"><a href=index.shtml>home</a></td>
<td id="contact"><a href=contact.shtml>home</a></td>

There will many uses for this.
Comment 1 David McKellar 2005-04-11 19:37:45 UTC
Created attachment 14681 [details]
diff -u mod_include.c-old  mod_include.c
Comment 2 William A. Rowe Jr. 2018-11-07 21:08:32 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.