www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Pisoni <da...@cnation.com>
Subject mod_include/411: SSI's with '#exec cgi' not passing CGI headers through
Date Fri, 18 Apr 1997 00:30:03 GMT

>Number:         411
>Category:       mod_include
>Synopsis:       SSI's with '#exec cgi' not passing CGI headers through
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache (Apache HTTP Project)
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Apr 17 17:30:02 1997
>Originator:     david@cnation.com
>Release:        1.2b8
Linux 2.0.27, GCC 2.7.2, libc.so.5.4.23
I have noticed this before, but have heretofore been able to work around it.  Now I'm stuck.

If you use an SSI to execute a CGI, all the headers from the CGI are not passed through to
the browser.
Specifically, I have tried this with headers "Set-cookie" and "Expires", with no luck.  I
think "Status"
goes through, but have not verified that.

The reason why I have encountered this now is because Netscape will (moronically) cache SSI's
or CGI's if 
you set it to 'never' check cached items.  By sending an 'Expires' header, a CGI will be forced
to decache.
Just make a simple CGI that sets a cookie, and call it with an SSI.  Did you get the cookie?
Certainly -- send those headers on through! :-)

View raw message