Gecko [ www.casapremiada.novaexata.com.br ]

Name	Size	Permission
alt_edit_help.html	2.79 KB	-rw-r--r--
bashlike_edit_help.html	9.8 KB	-rw-r--r--
bookmark_help.html	1.21 KB	-rw-r--r--
cookie_help.html	2.75 KB	-rw-r--r--
dired_help.html	2.28 KB	-rw-r--r--
edit_help.html	2.88 KB	-rw-r--r--
environments.html	21.58 KB	-rw-r--r--
follow_help.html	10.09 KB	-rw-r--r--
gopher_types_help.html	1.64 KB	-rw-r--r--
history_help.html	2.07 KB	-rw-r--r--
keystroke_help.html	7.87 KB	-rw-r--r--
movement_help.html	2.02 KB	-rw-r--r--
option_help.html	20.36 KB	-rw-r--r--
other_help.html	7.99 KB	-rw-r--r--
print_help.html	1.52 KB	-rw-r--r--
scrolling_help.html	2.86 KB	-rw-r--r--
test_display.html	1.93 KB	-rw-r--r--
visited_help.html	1.86 KB	-rw-r--r--
xterm_help.html	1.44 KB	-rw-r--r--

Code Editor : cookie_help.html

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">

<title>Help on the Cookie Jar Page</title>
 <link rev="made" href="mailto:lynx-dev@nongnu.org">
 <meta http-equiv="Content-Type" content=
 "text/html; charset=us-ascii">
</head>

<body>
 <h1>Cookie Jar Page Help</h1>

The Cookie Jar Page displays all of the unexpired cookies you
 have accumulated in the hypothetical Cookie Jar. The
 cookies are obtained via Set-Cookie 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.

The cookies are listed by domain (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 path attribute of the cookie).
 When Lynx sends requests to an http server whose address
 tail-matches a domain in the Cookie Jar, all
 its cookies with a path which head-matches the path in
 the URL for that request are included as a Cookie MIME
 header. The 'allow' setting for accepting cookies from each
 domain (always, never, or via prompt) also is indicated in the
 listing.

The listing also shows the port (normally 80) of the
 URL for the request which caused the cookie to be sent, and
 whether the secure flag is set for the cookie, in which
 case it will be sent only via secure connections (presently, only
 SSL). The Maximum Gobble Date, 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 Set-Cookie MIME headers,
 those also are displayed in the listing.

The domain=value pairs, and each cookie's name=value,
 are links in the listing. Activating a domain=value link
 will invoke a prompt asking whether all cookies in that
 domain should be Gobbled (deleted from the
 Cookie Jar), and/or whether the domain entry
 should be Gobbled if all of its cookies have been
 Gobbled, or whether to change the 'allow' setting for
 that domain. Activating a cookie's name=value link will
 cause that particular cookie to be Gobbled. You will be
 prompted for confirmations of deletions, to avoid any accidental
 Gobbling.
</body>
</html>

${this.title}

Code Editor : cookie_help.html