Maximum amount of time in which the user agent should return theĬookie, the servers to which the user agent should return the cookie,Īnd the URI schemes for which the cookie is applicable.įor historical reasons, cookies contain a number of security and For example, the server indicates a scope for eachĬookie when sending it to the user agent.
Return the name/value pairs in the Cookie header.Īlthough simple on their surface, cookies have a number ofĬomplexities. The user agent makes subsequent requests to the server, the userĪgent uses the metadata and other information to determine whether to Pairs and associated metadata (called cookies) to a user agent. Using the Set-Cookie header field, an HTTP server can pass name/value RFC 6265 HTTP State Management Mechanism April 2011 7.1. It for publication as an RFC or to translate it into languages otherġ. Not be created outside the IETF Standards Process, except to format
Outside the IETF Standards Process, and derivative works of it may The copyright in such materials, this document may not be modified Without obtaining an adequate license from the person(s) controlling Modifications of such material outside the IETF Standards Process. Material may not have granted the IETF Trust the right to allow The person(s) controlling the copyright in some of this This document may contain material from IETF Documents or IETFĬontributions published or made publicly available before Novemberġ0, 2008. RFC 6265 HTTP State Management Mechanism April 2011 The Trust Legal Provisions and are provided without warranty as Include Simplified BSD License text as described in Section 4.e of
#LONG PATH TOOL 5.1.4 LICENSE KEY CODE#
Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal
#LONG PATH TOOL 5.1.4 LICENSE KEY HOW TO#
Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained atĬopyright (c) 2011 IETF Trust and the persons identified as the Internet Standards is available in Section 2 of RFC 5741. Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This is an Internet Standards Track document. AlthoughĬookies have many historical infelicities that degrade their securityĪnd privacy, the Cookie and Set-Cookie header fields are widely used Stateful session over the mostly stateless HTTP protocol. (called cookies) at HTTP user agents, letting the servers maintain a These header fields can be used by HTTP servers to store state This document defines the HTTP Cookie and Set-Cookie header fields. Internet Engineering Task Force (IETF) A.