It's been a long time since I've messed with cgi & cookies but if I
remember right the session cookies were hard to pass (no pun intended)
Persistent Cookies = true
will allow you to deal with them in a more normal manner. Also, with
either of them, if you used STM and recalled the cookie into the page
it was more apt to pass through. Make sense?
There have been cgi changes since then so it's also possible you found
a bug.
----- Original Message -----
From: "Joe Byrne" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, 31 May, 2002 15:01
Subject: [sambar] SSI Variables {01}
According to the DOCs:
" By default the PATH_INFO and QUERY_STRING of the original request
are passed to the cgi/wincgi executable." It goes on to list a number
of CGI variables and indicates that "most" CGI variables are
available. However, after much testing, it appears that the
HTTP_COOKIE variable is not one of them.
#1. Can someone confirm that using something like <!--#exec
cgi="cgihello.exe"--> (or a WinCGI=) will not provide access to the
HTTP_Cookie variable
#2. Does anyone know of a work around if #1 is confirmed.
Thanks!
--Joe
-------------------------------------------------------
To unsubscribe please go to http://www.sambar.ch/list/
-------------------------------------------------------
To unsubscribe please go to http://www.sambar.ch/list/
