webcookies – HTTP cookie manager
manages a set of HTTP cookies, which are
used to associate HTTP requests with persistent state
(such as user profiles) on many web servers.
and mounts itself at
will post a service file descriptor
The cookie file contains one cookie per line;
each cookie comprises some number of
Cookie attributes are:
The name of the cookie on the remote server.
The value associated with that name on the remote server.
The actual data included when a cookie is sent back
to the server is
are the values associated with the
The domain within which the cookie can be used.
is an IP address, the cookie can only be used when
connecting to a web server at that IP address.
is a pattern beginning with a dot,
the cookie can only be used for servers whose name
as a suffix.
For example, a cookie with
may be used on the web sites
The cookie can only be used for URLs with a path (the part after
The version of the HTTP cookie specification, specified by the server.
A comment, specified by the server.
The cookie expires at time
which is a decimal number of seconds since the epoch.
The cookie may only be used over secure
The domain associated with this cookie was set by
the server (rather than inferred from a URL).
The path associated with this cookie was set by the
server (rather than inferred from a URL).
The server presented the cookie in “Netscape style,” which
does not conform to the cookie standard, RFC2109.
It is assumed that when presenting the cookie to the server,
it must be sent back in Netscape style as well.
serves a directory containing two files.
is a textual representation of the cookie file,
which can be edited to change the set of cookies
is intended to be used by HTTP clients
to access cookies.
the client must write a full URL to it.
After writing the URL, reading from the file will yield any
headers that should be included in the
request for this particular URL.
Once the request has been made, any
lines in the HTTP response header should
be written to the file to save them for next time.
decides not to accept the cookie (as outlined in
RFC2109, section 4.3.4), no indication is given.