| 1 |
README.cookies |
| 2 |
|
| 3 |
Cookie handling when using the lynx browser: |
| 4 |
|
| 5 |
General Usage on a unix system: |
| 6 |
|
| 7 |
Cookie handling may be set so that you read them in on session start up from a |
| 8 |
saved file, and to restore all cookies to that file on session close. |
| 9 |
|
| 10 |
Warning and Disclaimer: |
| 11 |
|
| 12 |
The lynx browser provides great opportunity to examine and make decisions about |
| 13 |
cookies by default, but some users just want the speed benefits of the lynx |
| 14 |
browser without the prompting for a decision to accept or reject the cookie. |
| 15 |
Should you think that this is your situation, please read this: |
| 16 |
|
| 17 |
There are a number of privacy issues with accepting all cookies blindly, not |
| 18 |
the least of which is that you are storing evidence of your browsing activity |
| 19 |
into a regular disk file. |
| 20 |
|
| 21 |
You have been warned. There are many resources available that will provide you |
| 22 |
with more information about making informed choices about this subject. |
| 23 |
|
| 24 |
With that in mind, here is how to accept all cookies transparently and rapidly: |
| 25 |
|
| 26 |
The following .lynxrc or lynx.cfg settings provide the user with the ability |
| 27 |
to by default accept all cookies transparently. |
| 28 |
|
| 29 |
SET_COOKIES:TRUE |
| 30 |
ACCEPT_ALL_COOKIES:TRUE |
| 31 |
PERSISTENT_COOKIES:TRUE |
| 32 |
COOKIE_FILE:/path/to/directory/.lynx_cookies |
| 33 |
COOKIE_SAVE_FILE:/path/to/directory/.lynx_cookies |
| 34 |
COOKIE_LOOSE_INVALID_DOMAINS:sports.espn.go.com,espn.go.com,.go.com, |
| 35 |
FORCE_SSL_COOKIES_SECURE:FALSE |
| 36 |
|
| 37 |
You must have a "cookie save file" that you own and for which you have |
| 38 |
read/write permission; cookies are flushed out to that disk location when you |
| 39 |
exit lynx, and are read in for use at the start of a lynx session from there. |
| 40 |
Cookies do not persist unless this happens. |
| 41 |
|
| 42 |
If you wish to see for yourself that this actually happens, please use the |
| 43 |
-trace command line option and then read the resulting file "Lynx.trace". |
| 44 |
It will show the cookies being read in at the start of a session, and being |
| 45 |
written out at the conclusion of a session. |
| 46 |
|
| 47 |
FORCE_SSL_COOKIES_SECURE is for ebay and the like, or they won't remember you; |
| 48 |
(their login is secure but everything else isn't, like a lot of big sites). |
| 49 |
If lynx attempts to transmit the ebay cookie securely, it's not taken. |
| 50 |
This doesn't affect cookie acceptance but it's a functionality issue for users. |
| 51 |
|
| 52 |
The COOKIE_LOOSE_INVALID_DOMAINS is for botched cookies from sites you read a |
| 53 |
lot. This causes a great deal of prompting and if you are a frequent site user |
| 54 |
you may want to convenience yourself with a set of loose invalid domains. |
| 55 |
|
| 56 |
|
| 57 |
Stef Caunter |
| 58 |
http://caunter.ca/contact.html |
| 59 |
http://caunter.ca/README.cookies |
| 60 |
|