w3m

Unnamed repository; edit this file to name it for gitweb.
git clone https://logand.com/git/w3m.git/
Log | Files | Refs | README

README.cookie (1814B)


      1 cookie support of w3m
      2 
      3 
      4                                                          (2000/11/07)  K. Okada
      5                                                         okabek@guitar.ocn.ne.jp
      6 
      7  * Support of version 0 (http://www.netscape.com/newsref/std/cookie_spec.html)
      8    and version 1 (http://www.ics.uci.edu/pub/ietf/http/rfc2109.txt,
      9    http://www.ics.uci.edu/pub/ietf/http/draft-ietf-http-state-man-mec-12.txt)
     10    cookie.
     11    
     12  * If you wont to disable cookie support, run configure script with
     13     --disable-cookie option.
     14    
     15  * You can choose to use cookie or not on the Option Setting Panel or
     16    -cookie and -no-cookie option.
     17    
     18  * You can disable cookie on the Option Setting Panel. In this case
     19     all cookies are rejected, however, cookies which accepted before
     20     disable cookie are used.
     21    
     22  * You can see list of accepted cookies with C-k. In this panel, you
     23     can choose to use each cookie or not.
     24    
     25  * You can specify domains accept or not accept cookies on the Option
     26     Setting Panel. Domains are specified with following format.
     27    
     28       domain-list = domains
     29                   | ""
     30       domains     = domain
     31                   | domain + "," + domains
     32       domain      = "." + domain-name      ; match with domain name
     33                   | host-domain-name       ; match with HDN
     34                   | ".local"               ; match with all HDN except which include  "."
     35                   | "."                    ; match with all
     36 
     37                               (HDN: host domain name)
     38 
     39 
     40  ¡¦ If the number of "." in domain name is lesser than 2, it is
     41     assumed as invalid cookie (cf. RFC 2109 4.3.2), however, you can
     42     use cookie_avoid_wrong_number_of_dots to avoid this
     43     restriction. You can set this in "Domains to avoid [wrong number
     44     of dots]" on the Option Setting Panel.