Content deleted Content added
Pleasancoder (talk | contribs) |
Pleasancoder (talk | contribs) |
||
Line 111:
Cookies are arbitrary pieces of data, usually chosen and first sent by the web server, and stored on the client computer by the web browser. The browser then sends them back to the server with every request, introducing [[state (computer science)|states]] (memory of previous events) into otherwise stateless [[HTTP]] transactions. Without cookies, each retrieval of a [[web page]] or component of a web page would be an isolated event, largely unrelated to all other page views made by the user on the website. Although cookies are usually set by the web server, they can also be set by the client using a scripting language such as [[JavaScript]] (unless the cookie's <code>HttpOnly</code> flag is set, in which case the cookie cannot be modified by scripting languages).
The cookie specifications<ref name="httponlyrfc">IETF [//tools.ietf.org/html/rfc6265 HTTP State Management Mechanism, Apr, 2011] Obsoletes RFC 2965</ref><ref>{{cite web |title=Persistent client state HTTP cookies: Preliminary specification |url=http://wp.netscape.com/newsref/std/cookie_spec.html |archiveurl=https://web.archive.org/web/20070805052634/http://wp.netscape.com/newsref/std/cookie_spec.html |publisher=Netscape |archivedate=2007-08-05 |date=c. 1999 }}
* Can support cookies as large as 4,096 [[byte]]s in size.
* Can support at least 50 cookies per [[Internet ___domain|___domain]] (i.e. per website).
| |||