118:. The token has no intrinsic meaning, but its uniqueness allows it to be exchanged for the correct coat when returned to the coat check counter. The coat check token is opaque because the way in which the counter staff are able to find the correct coat when the token is presented is immaterial to the person who wishes their coat returned. In other cases (as is possible with
173:
A handle, transaction ID, or other token of agreement between cooperating programs. "I give him a packet, he gives me back a cookie." The claim check you get from a dry-cleaning shop is a perfect mundane example of a cookie; the only thing it's useful for is to relate a later transaction to this one
51:
and not usually interpreted until the recipient passes the cookie data back to the sender or perhaps another program at a later time.
185:
UNIX Programmer's Manual, 7th
Edition, Vol. 1, FSEEK (3S), Bell Telephone Laboratories, Murray Hill, New Jersey, January 1979.
93:. It is measured in bytes on UNIX; on some other systems it is a magic cookie, and the only foolproof way to obtain an
207:, Revised and expanded version of 7th Edition, Volume 1, page 263. New York: Holt, Rinehart and Winston, 1983.
89:
returns the current value of the offset relative to the beginning of the file associated with the named
226:
129:, the remote server may leave an HTTP cookie on one's computer, where they are often used to
54:
In some cases, recipient programs are able to meaningfully compare two cookies for equality.
58:
39:
or as "handle, transaction ID, or other token of agreement between cooperating programs".
8:
122:), the actual data of interest can be stored as name–value pairs directly on the cookie.
115:
125:
Cookies are used as identifying tokens in many computer applications. When one visits a
208:
81:
routine in the C standard library, dating back at least to 1979, where it was stated:
158:
36:
47:
Cookie data is typically not meaningful to the recipient program. The contents are
48:
32:
137:
130:
194:
UNIX Programmer's Manual, Vol. II (Library), FSEEK (3S), 4.2 BSD, 12 Feb 1983.
220:
136:
Cookies are a component of the most common authentication method used by the
31:
for short, is a token or short packet of data passed between communicating
119:
111:
20:
74:
126:
78:
203:
Bell
Telephone Laboratories, Incorporated. "FSEEK(3S)." In
209:
https://archive.org/details/unixtimesharings0001bell
35:. The cookie is often used to identify a particular
205:UNIX Time-Sharing System: UNIX Programmer’s Manual
110:An analogy is the token supplied at a coat check (
218:
133:identity upon returning to the website.
219:
16:Type of data passed between programs
174:(so you get the same clothes back).
156:
13:
105:
14:
238:
197:
188:
179:
150:
57:The cookie can be used like a
1:
143:
64:
7:
10:
243:
42:
227:Data transmission
234:
211:
201:
195:
192:
186:
183:
177:
176:
170:
169:
154:
242:
241:
237:
236:
235:
233:
232:
231:
217:
216:
215:
214:
202:
198:
193:
189:
184:
180:
167:
165:
163:The Jargon File
157:Raymond, Eric.
155:
151:
146:
138:X Window System
108:
106:Cookie as token
73:appears in the
67:
45:
17:
12:
11:
5:
240:
230:
229:
213:
212:
196:
187:
178:
148:
147:
145:
142:
107:
104:
103:
102:
66:
63:
44:
41:
15:
9:
6:
4:
3:
2:
239:
228:
225:
224:
222:
210:
206:
200:
191:
182:
175:
164:
160:
153:
149:
141:
139:
134:
132:
128:
123:
121:
117:
114:) counter in
113:
100:
96:
92:
88:
84:
83:
82:
80:
76:
72:
62:
60:
55:
52:
50:
40:
38:
34:
30:
26:
22:
204:
199:
190:
181:
172:
166:. Retrieved
162:
152:
135:
131:authenticate
124:
120:HTTP cookies
109:
98:
94:
90:
86:
71:magic cookie
70:
68:
56:
53:
46:
28:
25:magic cookie
24:
18:
168:2022-01-04
144:References
27:, or just
116:real life
112:cloakroom
69:The term
65:Early use
21:computing
221:Category
159:"Cookie"
77:for the
75:man page
33:programs
127:website
95:offset
91:stream
59:ticket
49:opaque
29:cookie
99:fseek
87:ftell
79:fseek
43:Usage
37:event
97:for
23:, a
19:In
223::
171:.
161:.
140:.
101:."
61:.
85:"
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.