The browser has nothing to do with SSI, the reason you are using CGI::SSI is because the HTTP server will not parse output from a script for SSI directives.
The SSI functionality will be totally dependent on the HTTP SERVER and how it is configured. If it is able to pass the HTTP header, for that is where the cookie is, (or the HTTP request object in Apache terms) to the called script, then yes. But I suspect this is not normally the case. In particular CGI::SSI is very general by nature and doesn't appear to support server dependent tricks. The author does suggest you look at mod_include and Apache::SSI. But I suspecrt the best way to handle this (and the most portable!) is to read the cookie in the wrapper script and pass its contents to the script providing the content to be included. The 'inner' script will always be sure of seeing the correct information.
In reply to Re: CGI:SSI cookies
by jdtoronto
in thread CGI:SSI cookies
by MrForsythExeter
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |