www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ken Coar <Ken.C...@Golux.Com>
Subject mod_include/4697: SERVER_PROTOCOL SSI environment variable not always set to "INCLUDED"
Date Mon, 05 Jul 1999 18:51:29 GMT

>Number:         4697
>Category:       mod_include
>Synopsis:       SERVER_PROTOCOL SSI environment variable not always set to "INCLUDED"
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Jul  5 13:10:02 PDT 1999
>Originator:     Ken.Coar@Golux.Com
>Release:        1.3.6
The SERVER_PROTOCOL environment variable is supposedly set to
"INCLUDED" if the resource was accessed through a subrequest
or a server-side include.  Unfortunately, this appears to
reliably be the case only if the document is a CGI script;
server-parsed SSI documents still get the value of the parent
Create a CGI script and an SSI document, each of which simply
displays the value of the SERVER_PROTOCOL environment variable.
Then access them from an SSI document with 'include virtual="file"'.
r->protocol is set to "INCLUDED" in routine ap_set_sub_req_protocol()
in http_protocol.c.  I suspect that this is either not being invoked
in all the correct codepaths, or else that mod_include.c should be
setting the field directly.
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message