HTTP State Management Mechanism
draft-ietf-httpbis-rfc6265bis-00

Document Type Active Internet-Draft (httpbis WG)
Last updated 2016-10-10
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
HTTP Working Group                                              A. Barth
Internet-Draft                                                   M. West
Intended status: Standards Track                             Google, Inc
Expires: April 13, 2017                                 October 10, 2016

                    HTTP State Management Mechanism
                    draft-ietf-httpbis-rfc6265bis-00

Abstract

   This document defines the HTTP Cookie and Set-Cookie header fields.
   These header fields can be used by HTTP servers to store state
   (called cookies) at HTTP user agents, letting the servers maintain a
   stateful session over the mostly stateless HTTP protocol.  Although
   cookies have many historical infelicities that degrade their security
   and privacy, the Cookie and Set-Cookie header fields are widely used
   on the Internet.  This document obsoletes RFC 2965.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 13, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Barth & West             Expires April 13, 2017                 [Page 1]
Internet-Draft       HTTP State Management Mechanism        October 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Conformance Criteria  . . . . . . . . . . . . . . . . . .   4
     2.2.  Syntax Notation . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Server Requirements . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Set-Cookie  . . . . . . . . . . . . . . . . . . . . . . .   8
       4.1.1.  Syntax  . . . . . . . . . . . . . . . . . . . . . . .   8
       4.1.2.  Semantics (Non-Normative) . . . . . . . . . . . . . .  10
     4.2.  Cookie  . . . . . . . . . . . . . . . . . . . . . . . . .  13
       4.2.1.  Syntax  . . . . . . . . . . . . . . . . . . . . . . .  13
       4.2.2.  Semantics . . . . . . . . . . . . . . . . . . . . . .  13
   5.  User Agent Requirements . . . . . . . . . . . . . . . . . . .  13
     5.1.  Subcomponent Algorithms . . . . . . . . . . . . . . . . .  14
       5.1.1.  Dates . . . . . . . . . . . . . . . . . . . . . . . .  14
       5.1.2.  Canonicalized Host Names  . . . . . . . . . . . . . .  15
       5.1.3.  Domain Matching . . . . . . . . . . . . . . . . . . .  16
       5.1.4.  Paths and Path-Match  . . . . . . . . . . . . . . . .  16
     5.2.  The Set-Cookie Header . . . . . . . . . . . . . . . . . .  17
       5.2.1.  The Expires Attribute . . . . . . . . . . . . . . . .  18
       5.2.2.  The Max-Age Attribute . . . . . . . . . . . . . . . .  19
       5.2.3.  The Domain Attribute  . . . . . . . . . . . . . . . .  19
       5.2.4.  The Path Attribute  . . . . . . . . . . . . . . . . .  20
       5.2.5.  The Secure Attribute  . . . . . . . . . . . . . . . .  20
       5.2.6.  The HttpOnly Attribute  . . . . . . . . . . . . . . .  20
     5.3.  Storage Model . . . . . . . . . . . . . . . . . . . . . .  20
     5.4.  The Cookie Header . . . . . . . . . . . . . . . . . . . .  23
   6.  Implementation Considerations . . . . . . . . . . . . . . . .  25
     6.1.  Limits  . . . . . . . . . . . . . . . . . . . . . . . . .  25
     6.2.  Application Programming Interfaces  . . . . . . . . . . .  25
     6.3.  IDNA Dependency and Migration . . . . . . . . . . . . . .  26
Show full document text