lynx-dev extended cookie control (was: more help trying to get lynx 2.8.2dev17 to eat all cookies)

[Klaus Weide]

On Sat, 27 Feb 1999, Larry W. Virden wrote:

> accept_all_cookies=TRUE
> cookie_accept_domains=
> cookie_reject_domains=
> cookie_loose_invalid_domains=.com,.edu,.net
> cookie_strict_invalid_domains=
> cookie_query_invalid_domains=

Seeing these together reminds me -

What do you think (Brian, especially) about extending the syntax
of those lists to allow "*"?  For example,

  cookie_loose_invalid_domains=.remarq.com
  cookie_query_invalid_domains=*

would set the default behavior, for domains that are not otherwise
listed, to "query".  accept_all_cookies=TRUE would be redundant
(but could be kept for compatibility) for cookie_accept_domains=*
[I think].

This wouldn't be trivial to implement in a meaningful way though,
regarding precedence / order of processing.  Basically first all
the "*" from all the options would have to be handled (in a to-be-
determined order or precedence), then all the specific domains.
It gets more complicate because there are two places where these
can be set, lynx.cfg and .lynxrc.  It would make sense to first
collect all the strings without setting anything yet, then when
the strings from both potential sources are there determine the
precedence (something like that seems to be already there, I admit
I haven't looked closely).

(This is not the same as allowing sub-domains to match - that would
be much more complicated.)

   Klaus