[ Avaa Bypassed ]




Upload:

Command:

hmhc3928@18.227.24.1: ~ $
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
<!-- $LynxId: cookie_help.html,v 1.7 2012/01/31 23:19:37 tom Exp $ -->

<html>
<head>
  <meta name="generator" content=
  "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">

  <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>

  <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>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>

  <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
  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. 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>

  <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 invoke a prompt asking whether all cookies in that
  <em>domain</em> 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>. You will be
  prompted for confirmations of deletions, to avoid any accidental
  <em>Gobbling</em>.</p>
</body>
</html>

Filemanager

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