From: mpd@netcom.com (Mike Duvos)
To: cypherpunks@toad.com
Message Hash: 611f06d76404d22b541e2b29f5924960e138723a0fb15871b8e5f80c7a365451
Message ID: <199606300159.SAA08486@netcom3.netcom.com>
Reply To: <199606292334.QAA20775@infinity.c2.org>
UTC Datetime: 1996-06-30 06:51:33 UTC
Raw Date: Sun, 30 Jun 1996 14:51:33 +0800
From: mpd@netcom.com (Mike Duvos)
Date: Sun, 30 Jun 1996 14:51:33 +0800
To: cypherpunks@toad.com
Subject: Re: Cookies anyone?
In-Reply-To: <199606292334.QAA20775@infinity.c2.org>
Message-ID: <199606300159.SAA08486@netcom3.netcom.com>
MIME-Version: 1.0
Content-Type: text/plain
A Nym Writes:
> While rummaging around in my cookie jar, I found this message--
> along with some cookies.
>
> :Netscape HTTP Cookie File
> :# http://www.netscape.com/newsref/std/cookie_spec.html
> :# This is a generated file! Do not edit.
>
> Rather than bring down my system by experimenting, I thought I'd ask the list, "What happens if I delete this file?" and "What happens if I
> delete (edit) the cookies?"
>
> This may have been discussed before, but until now I never checked for
> cookies.
>
> Thanks for your consideration of this matter.
HTTP servers are permitted to store up to 4k bytes of information of their
choice on your machine, which is returned to them upon request the next
time you access their system.
This allows the servers to maintain a client state which persists
across separate accesses.
Nothing will happen if you delete the file, other than that servers
will not remember information they stored on the client side during
your previous visits. If you edit the file, which is binary, you may
possibly mess it up and choke the software that uses it.
There are some minor privacy implications for "Cookies", but they
have been discussed on the list before.
--
Mike Duvos $ PGP 2.6 Public Key available $
mpd@netcom.com $ via Finger. $
Return to July 1996
Return to “vanished@alpha.c2.org”