Protocol Cookie

Details: Protocol Cookie

Protocol cookie is not so much a standalone protocol as a sub-protocol. While a secure protocol cookie has been proposed by Alex Liu, Jason Kovacs, Chin-Tser Huang, and Mohammad Gouda, cookies are generally standardized under RFC 2965: HTTP State Management Mechanism which was proposed in October 2000. Under RFC 2965, new headers (Cookie, Cookie2, and Set-Cookie2) were described for carrying state information between user agents and origin servers. Cookies are used for several purposes including for Web applications authenticating HTTP requests as well as maintaining state. Many computer users use cookies without realizing it. For example, cookies allow users to personalize Web sites and remember login information. The cookie itself is a small text file containing state information and residing either on the user’s hard disk or in the user’s computer’s memory. This cookie is retrieved whenever the user revisits the issuing Web site. While there are some privacy concerns surrounding the use of cookies and the protocol cookie headers, computer users can control how their computers handle cookies. A user can adjust the Web browser’s security options to block cookies altogether or accept cookies based on specific criteria such as whether the cookies are from sites with compact security policies. In general, computers do not need to recognize “protocol cookie” as cookies are defined through the headers under the HTTP protocol. As technology evolves, a protocol cookie may eventually be described.

Associated Protocol Cookie Applications:

Web browsers

Download to Troubleshoot and Fix Protocol Cookie Problems - PC Health Advisor