Bug 38408 - SSI environment vars not set in spawned processes
Summary: SSI environment vars not set in spawned processes
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_include (show other bugs)
Version: 2.2.0
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2006-01-27 00:11 UTC by Steve Losen
Modified: 2018-11-07 21:09 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Losen 2006-01-27 00:11:41 UTC
Apache 2.2 uses "lazy" evaluation of the SSI specific environment variables
LAST_MODIFIED, DATE_GMT, DATE_LOCAL, etc.  These variables are initialized
with a pointer to a particular null string (LAZY_VALUE). If mod_include
references one of these variables and if its value is LAZY_VALUE, then
mod_include sets the variable to its actual value before using it.

When SSI spawns processes via <!--#exec ... --> or
<!--#include virtual= ... --> nothing is done to evaluate SSI variables
that are still set to LAZY_VALUE, so These variables end up in the
environment of the spawned process with null string values.

For example, suppose you have a CGI program named foo.cgi that uses
LAST_MODIFIED and suppose you have this in a html document:

<!--#include virtual="foo.cgi"-->    LAST_MODIFIED is the null string

<!--#echo var="LAST_MODIFIED"-->     mod_include evaluates LAST_MODIFIED

<!--#include virtual="foo.cgi"-->    Now LAST_MODIFIED has correct value
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:41 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.