|
Ed,
Thank you! That was it
exactly. I never saw the path parameter in the cookie RFC before
(actually, just never paid attention to it). A few small mods and now
things are working just as I need.
Appreciate the help!
--Joe
----- Original Message -----
Sent: Wednesday, July 23, 2003 5:34
AM
Subject: [sambar] Problems with
cookies
The most likely explanation is that the cookie
you see when running showenv.exe was "set" by one of your cgi scripts and
defined with a path definition. If one of your perl scripts set
the cookie, it could just as easily set the path to www.mydomain.com/cgi-bin/ and
not just the root of the server www.mydomain.com/ When
you call debug.exe as an SSI, the client (Netscape or Internet Explorer) does
not see the cgi-bin directly at all but, rather the directory in which you
have the .stm page, e.g, you www.mydomain.com/docs/
(or what ever) directory and, therefore, does not send the cookie as part
of the header. Therefore, the script which shows all env variables
would never get the cookie from which to set the $ENV{HTTP_COOKIE}
variable.
----- Original Message -----
Sent: Wednesday, July 23, 2003 1:32
AM
Subject: [sambar] Problems with
cookies
Can someone tell me if this is how things
should work or not?
I have a Win32 executable as a cgi application
to dump all environment variable to a page. If I call the program
directly as in: www.mydomain.com/cgi-bin/showenv.exe
all cookie values are listed. However, if I call the exact same
program via SSI with the command: <!--#exec cgi="debug.exe"
--> in an STM page, everything BUT the cookie values are
returned.
Weird, eh? -------------------------------------------------------
To unsubscribe please go to http://www.sambar.ch/list/
-------------------------------------------------------
To unsubscribe please go to http://www.sambar.ch/list/
-------------------------------------------------------
To unsubscribe please go to http://www.sambar.ch/list/
|
