Re: lynx-dev Problem with COOKIE_ACCEPT_DOMAINS

[Klaus Weide]

On Fri, 7 Apr 2000, Jens Schleusener wrote:
> I have problems with the COOKIE_ACCEPT_DOMAINS run-time variable (using 
> lynx under AIX 4.1.4). I have configured in lynx.cfg
> 
>  #SET_COOKIES:TRUE
>  #ACCEPT_ALL_COOKIES:FALSE
>  COOKIE_ACCEPT_DOMAINS:.dlr.de
>  #COOKIE_REJECT_DOMAINS:
>  #COOKIE_LOOSE_INVALID_DOMAINS:
>  #COOKIE_STRICT_INVALID_DOMAINS:
>  #COOKIE_QUERY_INVALID_DOMAINS:
>  #PERSISTENT_COOKIES:FALSE
> 
> but if I access for e.g. http://www.dlr.de I am nevertheless prompted with
> 
>  www.dlr.de cookie: sk=018E2091003DB559  Allow? (Y/N/Always/neVer)

Lynx behaves as expected, so far.  (Not as exected by you, but as
intended and, I think, documented.)

> The expected behaviour (no prompt, automatically accept cookies without
> asking for confirmation) occurs if I changed the definition of
> COOKIE_ACCEPT_DOMAINS to
> 
>  COOKIE_ACCEPT_DOMAINS:.dlr.de,www.dlr.de

Also as expected.

> Definitions like
> 
>  COOKIE_ACCEPT_DOMAINS:www.dlr.de
>  COOKIE_ACCEPT_DOMAINS:www.dlr.de,.dlr.de
> 
> also don't work. 

They both should suppress the prompt.  Only listing ".dlr.de" alone
should not have this effect.  In fact, ".dlr.de" is irrelevant in
this case, only "www.dlr.de" matters.  (I am talking only about the
initial URL you gave, not any successive pages which might set different
cookies.)

I get the expected behavior with dev.18-based code.  I'm not aware
of code changes since then that would change anything in this area, so
please double-check.

> I hope I haven't overseen some documentation.

Well, this text in lynx.cfg is supposed to tell you what to put in
the list:

# Note that in order to match cookies, domains have to be spelled out exactly
# in the form in which they would appear on the Cookie Jar page (case is
# insignificant).  They are not wildcards.  Domains that apply to more than
# one host have a leading '.', but have to match *the cookie's* domain
# exactly.


   Klaus