diff options
Diffstat (limited to 'lynx_help/keystrokes/cookie_help.html')
| -rw-r--r-- | lynx_help/keystrokes/cookie_help.html | 45 |
1 files changed, 26 insertions, 19 deletions
diff --git a/lynx_help/keystrokes/cookie_help.html b/lynx_help/keystrokes/cookie_help.html index 60920128..0f7378b8 100644 --- a/lynx_help/keystrokes/cookie_help.html +++ b/lynx_help/keystrokes/cookie_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: cookie_help.html,v 1.8 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: cookie_help.html,v 1.9 2014/01/07 09:14:46 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -10,29 +10,33 @@ <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "Lynx provides a page show shows information about all of the unexpired cookies, including their fully qualified domain name, expiration time and name/value pairs."> + </head> <body> - <h1>Cookie Jar Page Help</h1> + <h2>Overview</h2> - <p>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#Cookies">State Management</a> across - successive requests to the servers.</p> + <p><strong>Lynx</strong>'s <em>Cookie Jar Page</em> 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#Cookies">State + Management</a> across successive requests to the servers.</p> <p>The cookies are listed by <em>domain</em> (server's Fully Qualified Domain Name, or site-identifying portion of the FQDN), and in order of decreasing specificity (number of slash-separated symbolic elements in the <em>path</em> attribute of the cookie). - When Lynx sends requests to an http server whose address - tail-matches a <em>domain</em> in the <em>Cookie Jar</em>, all - its cookies with a <em>path</em> which head-matches the path in - the URL for that request are included as a <em>Cookie</em> MIME - header. The 'allow' setting for accepting cookies from each - domain (always, never, or via prompt) also is indicated in the - listing.</p> + When <strong>Lynx</strong> sends requests to an http server whose + address tail-matches a <em>domain</em> in the <em>Cookie + Jar</em>, all its cookies with a <em>path</em> which head-matches + the path in the URL for that request are included as a + <em>Cookie</em> MIME header. The 'allow' setting for accepting + cookies from each domain (always, never, or via prompt) also is + indicated in the listing.</p> + + <h2>Cookie Details Shown</h2> <p>The listing also shows the <em>port</em> (normally 80) of the URL for the request which caused the cookie to be sent, and @@ -41,9 +45,12 @@ SSL). The <em>Maximum Gobble Date</em>, i.e., when the cookie is intended to 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> + replies to subsequent requests from <strong>Lynx</strong>. If the + server included any explanatory comments in its + <em>Set-Cookie</em> MIME headers, those also are displayed in the + listing.</p> + + <h2>Removing Cookies</h2> <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 |