HTTP/1.1 Drafts: Combined Table of Contents

HTTP/1.1, part 1: URIs, Connections, and Message Parsing

• 1.   Introduction
  • 1.1   Purpose
  • 1.2   Requirements
  • 1.3   Terminology
  • 1.4   Overall Operation
• 2.   Notational Conventions and Generic Grammar
  • 2.1   Augmented BNF
  • 2.2   Basic Rules
  • 2.3   ABNF Rules defined in other Parts of the Specification
• 3.   Protocol Parameters
  • 3.1   HTTP Version
  • 3.2   Uniform Resource Identifiers
    • 3.2.1   General Syntax
    • 3.2.2   http URL
    • 3.2.3   URI Comparison
  • 3.3   Date/Time Formats
    • 3.3.1   Full Date
  • 3.4   Transfer Codings
    • 3.4.1   Chunked Transfer Coding
  • 3.5   Product Tokens
• 4.   HTTP Message
  • 4.1   Message Types
  • 4.2   Message Headers
  • 4.3   Message Body
  • 4.4   Message Length
  • 4.5   General Header Fields
• 5.   Request
  • 5.1   Request-Line
    • 5.1.1   Method
    • 5.1.2   Request-URI
  • 5.2   The Resource Identified by a Request
• 6.   Response
  • 6.1   Status-Line
    • 6.1.1   Status Code and Reason Phrase
• 7.   Connections
  • 7.1   Persistent Connections
    • 7.1.1   Purpose
    • 7.1.2   Overall Operation
      • 7.1.2.1   Negotiation
      • 7.1.2.2   Pipelining
    • 7.1.3   Proxy Servers
    • 7.1.4   Practical Considerations
  • 7.2   Message Transmission Requirements
    • 7.2.1   Persistent Connections and Flow Control
    • 7.2.2   Monitoring Connections for Error Status Messages
    • 7.2.3   Use of the 100 (Continue) Status
    • 7.2.4   Client Behavior if Server Prematurely Closes Connection
• 8.   Header Field Definitions
  • 8.1   Connection
  • 8.2   Content-Length
  • 8.3   Date
    • 8.3.1   Clockless Origin Server Operation
  • 8.4   Host
  • 8.5   TE
  • 8.6   Trailer
  • 8.7   Transfer-Encoding
  • 8.8   Upgrade
  • 8.9   Via
• 9.   IANA Considerations
  • 9.1   Message Header Registration
• 10.   Security Considerations
  • 10.1   Personal Information
  • 10.2   Abuse of Server Log Information
  • 10.3   Attacks Based On File and Path Names
  • 10.4   DNS Spoofing
  • 10.5   Proxies and Caching
  • 10.6   Denial of Service Attacks on Proxies
• 11.   Acknowledgments
• 12.   References
  • 12.1   Normative References
  • 12.2   Informative References
• Authors' Addresses
• A.   Internet Media Types
  • A.1   Internet Media Type message/http
  • A.2   Internet Media Type application/http
• B.   Tolerant Applications
• C.   Conversion of Date Formats
• D.   Compatibility with Previous Versions
  • D.1   Changes from HTTP/1.0
    • D.1.1   Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses
  • D.2   Compatibility with HTTP/1.0 Persistent Connections
  • D.3   Changes from RFC 2068
  • D.4   Changes from RFC 2616
• E.   Change Log (to be removed by RFC Editor before publication)
  • E.1   Since RFC2616
  • E.2   Since draft-ietf-httpbis-p1-messaging-00
  • E.3   Since draft-ietf-httpbis-p1-messaging-01
  • E.4   Since draft-ietf-httpbis-p1-messaging-02
• Intellectual Property and Copyright Statements
• Index

HTTP/1.1, part 2: Message Semantics

• 1.   Introduction
  • 1.1   Requirements
• 2.   Notational Conventions and Generic Grammar
• 3.   Method
• 4.   Request Header Fields
• 5.   Status Code and Reason Phrase
  • 5.1   Status Code Registry
• 6.   Response Header Fields
• 7.   Entity
• 8.   Method Definitions
  • 8.1   Safe and Idempotent Methods
    • 8.1.1   Safe Methods
    • 8.1.2   Idempotent Methods
  • 8.2   OPTIONS
  • 8.3   GET
  • 8.4   HEAD
  • 8.5   POST
  • 8.6   PUT
  • 8.7   DELETE
  • 8.8   TRACE
  • 8.9   CONNECT
• 9.   Status Code Definitions
  • 9.1   Informational 1xx
    • 9.1.1   100 Continue
    • 9.1.2   101 Switching Protocols
  • 9.2   Successful 2xx
    • 9.2.1   200 OK
    • 9.2.2   201 Created
    • 9.2.3   202 Accepted
    • 9.2.4   203 Non-Authoritative Information
    • 9.2.5   204 No Content
    • 9.2.6   205 Reset Content
    • 9.2.7   206 Partial Content
  • 9.3   Redirection 3xx
    • 9.3.1   300 Multiple Choices
    • 9.3.2   301 Moved Permanently
    • 9.3.3   302 Found
    • 9.3.4   303 See Other
    • 9.3.5   304 Not Modified
    • 9.3.6   305 Use Proxy
    • 9.3.7   306 (Unused)
    • 9.3.8   307 Temporary Redirect
  • 9.4   Client Error 4xx
    • 9.4.1   400 Bad Request
    • 9.4.2   401 Unauthorized
    • 9.4.3   402 Payment Required
    • 9.4.4   403 Forbidden
    • 9.4.5   404 Not Found
    • 9.4.6   405 Method Not Allowed
    • 9.4.7   406 Not Acceptable
    • 9.4.8   407 Proxy Authentication Required
    • 9.4.9   408 Request Timeout
    • 9.4.10   409 Conflict
    • 9.4.11   410 Gone
    • 9.4.12   411 Length Required
    • 9.4.13   412 Precondition Failed
    • 9.4.14   413 Request Entity Too Large
    • 9.4.15   414 Request-URI Too Long
    • 9.4.16   415 Unsupported Media Type
    • 9.4.17   416 Requested Range Not Satisfiable
    • 9.4.18   417 Expectation Failed
  • 9.5   Server Error 5xx
    • 9.5.1   500 Internal Server Error
    • 9.5.2   501 Not Implemented
    • 9.5.3   502 Bad Gateway
    • 9.5.4   503 Service Unavailable
    • 9.5.5   504 Gateway Timeout
    • 9.5.6   505 HTTP Version Not Supported
• 10.   Header Field Definitions
  • 10.1   Allow
  • 10.2   Expect
  • 10.3   From
  • 10.4   Location
  • 10.5   Max-Forwards
  • 10.6   Referer
  • 10.7   Retry-After
  • 10.8   Server
  • 10.9   User-Agent
• 11.   IANA Considerations
  • 11.1   Status Code Registry
  • 11.2   Message Header Registration
• 12.   Security Considerations
  • 12.1   Transfer of Sensitive Information
  • 12.2   Encoding Sensitive Information in URIs
  • 12.3   Location Headers and Spoofing
• 13.   Acknowledgments
• 14.   References
  • 14.1   Normative References
  • 14.2   Informative References
• Authors' Addresses
• A.   Compatibility with Previous Versions
  • A.1   Changes from RFC 2068
  • A.2   Changes from RFC 2616
• B.   Change Log (to be removed by RFC Editor before publication)
  • B.1   Since RFC2616
  • B.2   Since draft-ietf-httpbis-p2-semantics-00
  • B.3   Since draft-ietf-httpbis-p2-semantics-01
  • B.4   Since draft-ietf-httpbis-p2-semantics-02
• Intellectual Property and Copyright Statements
• Index

HTTP/1.1, part 3: Message Payload and Content Negotiation

• 1.   Introduction
  • 1.1   Requirements
• 2.   Notational Conventions and Generic Grammar
• 3.   Protocol Parameters
  • 3.1   Character Sets
    • 3.1.1   Missing Charset
  • 3.2   Content Codings
  • 3.3   Media Types
    • 3.3.1   Canonicalization and Text Defaults
    • 3.3.2   Multipart Types
  • 3.4   Quality Values
  • 3.5   Language Tags
• 4.   Entity
  • 4.1   Entity Header Fields
  • 4.2   Entity Body
    • 4.2.1   Type
    • 4.2.2   Entity Length
• 5.   Content Negotiation
  • 5.1   Server-driven Negotiation
  • 5.2   Agent-driven Negotiation
  • 5.3   Transparent Negotiation
• 6.   Header Field Definitions
  • 6.1   Accept
  • 6.2   Accept-Charset
  • 6.3   Accept-Encoding
  • 6.4   Accept-Language
  • 6.5   Content-Encoding
  • 6.6   Content-Language
  • 6.7   Content-Location
  • 6.8   Content-MD5
  • 6.9   Content-Type
• 7.   IANA Considerations
  • 7.1   Message Header Registration
• 8.   Security Considerations
  • 8.1   Privacy Issues Connected to Accept Headers
  • 8.2   Content-Disposition Issues
• 9.   Acknowledgments
• 10.   References
  • 10.1   Normative References
  • 10.2   Informative References
• Authors' Addresses
• A.   Differences Between HTTP Entities and RFC 2045 Entities
  • A.1   MIME-Version
  • A.2   Conversion to Canonical Form
  • A.3   Introduction of Content-Encoding
  • A.4   No Content-Transfer-Encoding
  • A.5   Introduction of Transfer-Encoding
  • A.6   MHTML and Line Length Limitations
• B.   Additional Features
  • B.1   Content-Disposition
• C.   Compatibility with Previous Versions
  • C.1   Changes from RFC 2068
  • C.2   Changes from RFC 2616
• D.   Change Log (to be removed by RFC Editor before publication)
  • D.1   Since RFC2616
  • D.2   Since draft-ietf-httpbis-p3-payload-00
  • D.3   Since draft-ietf-httpbis-p3-payload-01
  • D.4   Since draft-ietf-httpbis-p3-payload-02
• Intellectual Property and Copyright Statements
• Index

HTTP/1.1, part 4: Conditional Requests

• 1.   Introduction
  • 1.1   Requirements
• 2.   Notational Conventions and Generic Grammar
• 3.   Entity Tags
• 4.   Status Code Definitions
  • 4.1   304 Not Modified
  • 4.2   412 Precondition Failed
• 5.   Weak and Strong Validators
• 6.   Rules for When to Use Entity Tags and Last-Modified Dates
• 7.   Header Field Definitions
  • 7.1   ETag
  • 7.2   If-Match
  • 7.3   If-Modified-Since
  • 7.4   If-None-Match
  • 7.5   If-Unmodified-Since
  • 7.6   Last-Modified
• 8.   IANA Considerations
  • 8.1   Message Header Registration
• 9.   Security Considerations
• 10.   Acknowledgments
• 11.   References
  • 11.1   Normative References
  • 11.2   Informative References
• Authors' Addresses
• A.   Compatibility with Previous Versions
  • A.1   Changes from RFC 2616
• B.   Change Log (to be removed by RFC Editor before publication)
  • B.1   Since RFC2616
  • B.2   Since draft-ietf-httpbis-p4-conditional-00
  • B.3   Since draft-ietf-httpbis-p4-conditional-01
  • B.4   Since draft-ietf-httpbis-p4-conditional-02
• Intellectual Property and Copyright Statements
• Index

HTTP/1.1, part 5: Range Requests and Partial Responses

• 1.   Introduction
  • 1.1   Requirements
• 2.   Notational Conventions and Generic Grammar
• 3.   Range Units
• 4.   Status Code Definitions
  • 4.1   206 Partial Content
  • 4.2   416 Requested Range Not Satisfiable
• 5.   Combining Byte Ranges
• 6.   Header Field Definitions
  • 6.1   Accept-Ranges
  • 6.2   Content-Range
  • 6.3   If-Range
  • 6.4   Range
    • 6.4.1   Byte Ranges
    • 6.4.2   Range Retrieval Requests
• 7.   IANA Considerations
  • 7.1   Message Header Registration
• 8.   Security Considerations
• 9.   Acknowledgments
• 10.   References
  • 10.1   Normative References
  • 10.2   Informative References
• Authors' Addresses
• A.   Internet Media Type multipart/byteranges
• B.   Compatibility with Previous Versions
  • B.1   Changes from RFC 2068
  • B.2   Changes from RFC 2616
• C.   Change Log (to be removed by RFC Editor before publication)
  • C.1   Since RFC2616
  • C.2   Since draft-ietf-httpbis-p5-range-00
  • C.3   Since draft-ietf-httpbis-p5-range-01
  • C.4   Since draft-ietf-httpbis-p5-range-02
• Intellectual Property and Copyright Statements
• Index

HTTP/1.1, part 6: Caching

• 1.   Introduction
  • 1.1   Purpose
  • 1.2   Terminology
  • 1.3   Requirements
• 2.   Notational Conventions and Generic Grammar
• 3.   Overview
  • 3.1   Cache Correctness
  • 3.2   Warnings
  • 3.3   Cache-control Mechanisms
  • 3.4   Explicit User Agent Warnings
  • 3.5   Exceptions to the Rules and Warnings
  • 3.6   Client-controlled Behavior
• 4.   Expiration Model
  • 4.1   Server-Specified Expiration
  • 4.2   Heuristic Expiration
  • 4.3   Age Calculations
  • 4.4   Expiration Calculations
  • 4.5   Disambiguating Expiration Values
  • 4.6   Disambiguating Multiple Responses
• 5.   Validation Model
• 6.   Response Cacheability
• 7.   Constructing Responses From Caches
  • 7.1   End-to-end and Hop-by-hop Headers
  • 7.2   Non-modifiable Headers
  • 7.3   Combining Headers
• 8.   Caching Negotiated Responses
• 9.   Shared and Non-Shared Caches
• 10.   Errors or Incomplete Response Cache Behavior
• 11.   Side Effects of GET and HEAD
• 12.   Invalidation After Updates or Deletions
• 13.   Write-Through Mandatory
• 14.   Cache Replacement
• 15.   History Lists
• 16.   Header Field Definitions
  • 16.1   Age
  • 16.2   Cache-Control
    • 16.2.1   What is Cacheable
    • 16.2.2   What May be Stored by Caches
    • 16.2.3   Modifications of the Basic Expiration Mechanism
    • 16.2.4   Cache Revalidation and Reload Controls
    • 16.2.5   No-Transform Directive
    • 16.2.6   Cache Control Extensions
  • 16.3   Expires
  • 16.4   Pragma
  • 16.5   Vary
  • 16.6   Warning
• 17.   IANA Considerations
  • 17.1   Message Header Registration
• 18.   Security Considerations
• 19.   Acknowledgments
• 20.   References
  • 20.1   Normative References
  • 20.2   Informative References
• Authors' Addresses
• A.   Compatibility with Previous Versions
  • A.1   Changes from RFC 2068
  • A.2   Changes from RFC 2616
• B.   Change Log (to be removed by RFC Editor before publication)
  • B.1   Since RFC2616
  • B.2   Since draft-ietf-httpbis-p6-cache-00
  • B.3   Since draft-ietf-httpbis-p6-cache-01
  • B.4   Since draft-ietf-httpbis-p6-cache-02
• Intellectual Property and Copyright Statements
• Index

HTTP/1.1, part 7: Authentication

• 1.   Introduction
  • 1.1   Requirements
• 2.   Notational Conventions and Generic Grammar
• 3.   Status Code Definitions
  • 3.1   401 Unauthorized
  • 3.2   407 Proxy Authentication Required
• 4.   Header Field Definitions
  • 4.1   Authorization
  • 4.2   Proxy-Authenticate
  • 4.3   Proxy-Authorization
  • 4.4   WWW-Authenticate
• 5.   IANA Considerations
  • 5.1   Message Header Registration
• 6.   Security Considerations
  • 6.1   Authentication Credentials and Idle Clients
• 7.   Acknowledgments
• 8.   References
  • 8.1   Normative References
  • 8.2   Informative References
• Authors' Addresses
• A.   Compatibility with Previous Versions
  • A.1   Changes from RFC 2616
• B.   Change Log (to be removed by RFC Editor before publication)
  • B.1   Since RFC2616
  • B.2   Since draft-ietf-httpbis-p7-auth-00
  • B.3   Since draft-ietf-httpbis-p7-auth-01
  • B.4   Since draft-ietf-httpbis-p7-auth-02
• Intellectual Property and Copyright Statements
• Index