3 webcookies \- HTTP cookie manager
20 manages a set of HTTP cookies, which are
21 used to associate HTTP requests with persistent state
22 (such as user profiles) on many web servers.
28 .BR $home/lib/webcookies )
32 .BR /mnt/webcookies ).
37 will post a service file descriptor
41 The cookie file contains one cookie per line;
42 each cookie comprises some number of
45 Cookie attributes are:
46 .TF \fBnetscapestyle=flag
49 The name of the cookie on the remote server.
52 The value associated with that name on the remote server.
53 The actual data included when a cookie is sent back
55 .IB \fR``\fIname = value\fR''
60 are the values associated with the
67 The domain within which the cookie can be used.
70 is an IP address, the cookie can only be used when
71 connecting to a web server at that IP address.
74 is a pattern beginning with a dot,
75 the cookie can only be used for servers whose name
79 For example, a cookie with
80 .B domain=.bell-labs.com
81 may be used on the web sites
84 .IR www.research.bell-labs.com .
87 The cookie can only be used for URLs with a path (the part after
88 .BI http:// hostname\fR)
93 The version of the HTTP cookie specification, specified by the server.
96 A comment, specified by the server.
99 The cookie expires at time
101 which is a decimal number of seconds since the epoch.
104 The cookie may only be used over secure
109 The domain associated with this cookie was set by
110 the server (rather than inferred from a URL).
113 The path associated with this cookie was set by the
114 server (rather than inferred from a URL).
117 The server presented the cookie in ``Netscape style,'' which
118 does not conform to the cookie standard, RFC2109.
119 It is assumed that when presenting the cookie to the server,
120 it must be sent back in Netscape style as well.
124 serves a directory containing two files.
127 is a textual representation of the cookie file,
128 which can be edited to change the set of cookies
132 is intended to be used by HTTP clients
136 the client must write a full URL to it.
137 After writing the URL, reading from the file will yield any
140 headers that should be included in the
141 request for this particular URL.
142 Once the request has been made, any
144 lines in the HTTP response header should
145 be written to the file to save them for next time.
148 decides not to accept the cookie (as outlined in
149 RFC2109, section 4.3.4), no indication is given.
153 .BR /mnt/webcookies/http ,
154 when it exists, to manage cookie state.
158 .B /sys/src/cmd/webcookies.c
162 It's not clear what the relationship between