diff options
author | Thomas E. Dickey <dickey@invisible-island.net> | 1998-11-10 19:47:00 -0500 |
---|---|---|
committer | Thomas E. Dickey <dickey@invisible-island.net> | 1998-11-10 19:47:00 -0500 |
commit | d3f9d5478df478427c2aa5db4507ddd0a38f0eb6 (patch) | |
tree | e27eacd6bbda653dd77f11cc020b9e0a59f7f4fc /lynx_help/keystrokes/cookie_help.html | |
parent | 18024037b515bfff83e0230b35151babe6005e18 (diff) | |
download | lynx-snapshots-d3f9d5478df478427c2aa5db4507ddd0a38f0eb6.tar.gz |
snapshot of project "lynx", label v2-8-2dev_2
Diffstat (limited to 'lynx_help/keystrokes/cookie_help.html')
-rw-r--r-- | lynx_help/keystrokes/cookie_help.html | 15 |
1 files changed, 6 insertions, 9 deletions
diff --git a/lynx_help/keystrokes/cookie_help.html b/lynx_help/keystrokes/cookie_help.html index 0fd5b255..081bb3e5 100644 --- a/lynx_help/keystrokes/cookie_help.html +++ b/lynx_help/keystrokes/cookie_help.html @@ -10,7 +10,7 @@ The Cookie Jar Page displays all of the unexpired cookies you have accumulated in the hypothetical <em>Cookie Jar</em>. The cookies are obtained via <em>Set-Cookie</em> MIME headers in replies from http servers, -and are used for <A HREF="../Lynx_users_guide.html#30">State Management</A> +and are used for <A HREF="../Lynx_users_guide.html#Cookies">State Management</A> across successive requests to the servers. <p>The cookies are listed by <em>domain</em> (server's Fully Qualified @@ -29,13 +29,10 @@ for the request which caused the cookie to be sent, and whether the <em>secure</em> flag is set for the cookie, in which case it will be sent only via secure connections (presently, only SSL). The <em>Maximum Gobble Date</em>, i.e., when the cookie is intended to -expire, also is indicated. Note, however, that Lynx presently gobbles -all of it's accumulated cookies on exit from the current session, even -if the server indicated an expiration in the distant future. Also, a -server may change the expiration date, or cause the cookie to be deleted, -in its replies to subsequent requests from Lynx. If the server included -any explanatory comments in its <em>Set-Cookie</em> MIME headers, those -also are displayed in the listing. +expire, also is indicated. Also, a server may change the expiration date, +or cause the cookie to be deleted, in its replies to subsequent requests +from Lynx. If the server included any explanatory comments in its +<em>Set-Cookie</em> MIME headers, those also are displayed in the listing. <p>The <em>domain</em>=value pairs, and each cookie's name=value, are links in the listing. Activating a <em>domain</em>=value link will @@ -44,7 +41,7 @@ should be <em>Gobbled</em> (deleted from the <em>Cookie Jar</em>), and/or whether the <em>domain</em> entry should be <em>Gobbled</em> if all of its cookies have been <em>Gobbled</em>, or whether to change the 'allow' setting for that <em>domain</em>. Activating a cookie's -name=value link will cause that particular cookie to be <em>Gobbled</em>. +name=value link will cause that particular cookie to be <em>Gobbled</em>. You will be prompted for confirmations of deletions, to avoid any accidental <em>Gobbling</em>. </BODY> |