Revision as of 15:48, 18 January 2016 view source Ntwjswml (talk \| contribs) 1 edit m →History: I am the David Kristol referenced in the article. I never heard of Aron Afatsuom. Lou and I worked on the specification, as is evidenced by both names on RFC 2109. Unfortunately, this Aron Afatsuom's name has proliferated across the web. Tag: Visual edit ← Previous edit		Revision as of 22:31, 18 January 2016 view source 76.126.150.68 (talk) No edit summary Tags: Mobile edit Mobile web edit repeating characters Next edit →
Line 31: Web browsers normally delete session cookies when the user closes the browser.<ref>{{cite web \|url= http://msdn.microsoft.com/en-us/library/ms526029(v=vs.90).aspx \|title=Maintaining session state with cookies \|work=Microsoft Developer Network \|accessdate=22 October 2012}}</ref> Unlike other cookies, session cookies do not have an expiration date assigned to them, which is how the browser knows to treat them as session cookies. Sett wlggwtyf m. RJ Krlmnnbhfjn ~~===Persistent cookie===~~ Instead of expiring when the web browser is closed as session cookies do, persistent cookies expire at a specific date or after a specific length of time. This means that, for the cookie's entire lifespan (which can be as long or as short as its creators want), its information will be transmitted to the server every time the user visits the website that it belongs to, or every time the user views a resource belonging to that website from another website (such as an advertisement). For this reason, persistent cookies are sometimes referred to as '''tracking cookies''' because they can be used by advertisers to record information about a user's web browsing habits over an extended period of time. However, they are also used for "legitimate" reasons as well (such as keeping users logged into their accounts on websites, to avoid re-entering login credentials at every visit). ===Secure cookie===

HTTP cookie: Difference between revisions