On Wed, 8 Mar 2000, David Combs wrote:
> Well, (for the first time ever) I tried the ^K command.
> (which means I'm a good one to suggest possible confusions --
> because I was confused -- and suggested improvements
> in what's typed out).
>
> 1: First I tried it at lynx start-up, on my bookmarks file.
>
> I got "cookie jar is empty".
Well, then it *is* empty.
> Which confused me, because I had just been looking at
> my .lynx_cookies, which was anything BUT empty.
>
> What it MIGHT have said (as I learned by experimentation)
> is something like:
>
> cookie jar has nothing FOR THIS DOMAIN, "<theDomainName>"
No, you have drawn the wrong conclusions.
If .lynx_cookies isn't empty, but the "cookie jar" is:
then either lynx was not using that file at all, or all cookies
in it were found to be expired or maybe otherwise invalid.
Lynx's "cookie jar" isn't bound to any specific "DOMAIN".
After all, it lists cookies for various domains.
> 2: (Would "site" be equivalent to "domain"?)
I don't know what exactly "site" means. People seem to use it
inconsistently for various things.
> I just looked at the (local 2.8.2) users guide (why not just
> call it the "manual" -- much easier to type in, takes less
> room on the line, ...), and saw no DEFINITION of "domain".
>
> Nor when I downloaded it to my shell acct and grepped
> for domain -- no DEFINITION of what it meant.
The term "domain" is used as defined in the cookie specs.
It's a piece of information that is attached to a cookie
(either explicitly or implied).
> 4: MISSING: a nice similarly-formatted page for the ENTIRE
> cookie "jar". Sure, I can cat .lynx_cookies, but who
> can make any SENSE of it, except for that first column?
After startup, and before accessing any page that modifies the
cookie jar (by sending cookies), the cookie jar contains all
cookies from your persisten cookie file - if you have one, and
have configured lynx to use it -, minus those that have expired
since they were written to the file.
Klaus
