[thelist] deleting cookies, front and back

Jeff:

>"what exactly are you doing now to delete the cookie?"

Well, I'm doing it the way one always does, as you described, setting the cookie
to a previous date (actually, *I'm* not doing anything at all, as someone else
asked me to look into the code). But, further investigations reveal that the
cookie being set from the servlet used the default path setting (no setting),
which obviously won't work on the static pages because of the server/JRun
structure. I changed/added the path variable in the servlet. Problem solved.

:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: I suppose the real question is deeper than that... When
: you set a cookie using Perl or Java, etc., you send the cookie
: as a part of the header statement, as an extension of the HTTP
: protocol. But, when you set a cookie with JS, it's a property of
: the document object. I'm not exactly how to reconcile these two
: distinctions, where the overlap, if any, exists.
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

>"actually, they overlap completely.  if you set all your cookies with
>javascript, they're also all available to your server-side scripting
>language of choice.  the same is true if they're set server-side.  every
>last one of them is also a part of the document object in javascript.  when
>it comes down to it, the browser doesn't care how they got there, only that
>there are cookies available for that domain."

So, the fact of the matter is, when setting a cookie backend, the cookie comes
to exist only in browser memory (I'm talking about session cookies only, not
persistent); that is, the cookie is only *launched* from the headers? Yes, I
suppose the real question was where they exist.

Hmm... Okay, I can live with that.

Teresa