[NTLUG:Discuss] cookies and ssi - problem solved
David Camm
bbai at onramp.net
Fri Mar 24 22:45:43 CST 2000
the answer is that without a path=/, the path parameter in the cookie
defaults to the path of the program that set it - e.g. /cgi-bin/
the path of the ssi document is generally NOT the same (it's a document
path), and hence the cookie does not get sent by the browser.
explicitly setting path=/ in the cookie solves the problem.
sounds somewhat convoluted, but welcome to the web <grin>.
now that i've got that one knocked, here's the next one....
in the situation i'm working on, the program that executes under ssi is
used for validation. if the cookie is 'good', it basically returns
nothing. however, if it discovers that the cookie is not 'valid' and the
client should not see the document, what would one return to make this
occur? it's too late to return a location: header.
any ideas would be greatly appreciated.
david camm
@dvanced web systems
More information about the Discuss
mailing list