----- Original Message -----
From: "Scott Laplante" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 23, 2001 1:57 PM
Subject: Re: [AOLSERVER] Form Posting
> 1. what you describe is exactly what we're doing, in a filter, to ensure a
> sessionId on every request.
I am using a sessionid to keep people out who have not logged in via my main
form..
> 2. "setting a cookie" really means "adding a set-cookie header to the
> outputheaders, the value of which is "name=value;
[path|expires|domain=...]"
> this odesn't get sent to the browser until a response is made- so it won't
> be in the request headers until the browser's next request.
I know :) I am using Daniel Stasinski's fantastic cookie library for
AolServer (you can get it at www.scriptkitties.com in the projects section)
> 2a.a. if the page where the cookie is set and the redirected location are
in
> different directory paths, you'll want to set the path attribute to
> something standard- we use "/", since the only cookie we're using is
Thats what I am using..
> sesionId- things other than that are set using an nsv which is looked up
> based upon the sessionId cookie. also, if you want to store the cookie on
> the users' disks, you'll have to set the expires to something in the
future.
> an unset expires means "only in the browser session" which really means
> "until the user closes the browser". a favorite resource of mine is:
Thats what I want for a session cookie, so I have it set to expire when
browser is closed.. in some circumstances I even remove the content of the
cookie and force them to log back in again
> http://home.netscape.com/newsref/std/cookie_spec.html
I keep meaning to read that... :)
> 2a. this assumes that you include the aforementioned outputheaders in the
> request. note that ns_returnredirect doesn't allow for a -headers
> arguement. we instead use a wrapper around ns_respond, which isn't as bad
> as it first seems.
heh, first I have looked at ns_respond... now I have to figure out how to
handle headers.. :)
> 2b. there was a bug a while back i noted but never took the time to
> duplicate, about ns_conn outputheaders not working. it might be part of
> your problem. do a search of the archives for the string "TCL_OUTHDRS" or
> "ns_conn outputheaders does not work" and you'll probably hit the bug i'm
> talking about.
might be..
> i think in general you'll want to switch to using ns_respond and setting
> your own outputheaders, but ns_returnredirect should pass along the
correct
> headers- i.e. including the ones you've set.
it hasn't so far for me :) but I should have this all straightened out and
finished this weekend (hope hope hope) then I can write up my trials and
tribulations of getting the ccBill credit card charging system to work with
Aolserver.. (I had to *shudder* call tcl scripts from perl scripts)....
>
> folks, is this last assumption correct?
>
--
Patrick Spence <[EMAIL PROTECTED]>
Want weather reports delevered to your desktop?
http://ww2.weatherbug.com/aff/default.asp?ZCode=z3345
