RFC du protocole HTTP : sommaire
J. Mogul
Compaq
H. Frystyk
W3C/MIT
L. Masinter
Xerox
P. Leach
Microsoft
T. Berners-Lee
W3C/MIT
June 1999
Hypertext Transfer Protocol -- HTTP/1.1
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved.
The Hypertext Transfer Protocol (HTTP) is an application-level
protocol for distributed, collaborative, hypermedia information
systems. It is a generic, stateless, protocol which can be used for
many tasks beyond its use for hypertext, such as name servers and
distributed object management systems, through extension of its
request methods, error codes and headers [47]. A feature of HTTP is
the typing and negotiation of data representation, allowing systems
to be built independently of the data being transferred.
HTTP has been in use by the World-Wide Web global information
initiative since 1990. This specification defines the protocol
referred to as "HTTP/1.1", and is an update to RFC 2068 [33].
Table of Contents
- 1.0 Introduction
- 1.1 Purpose
- 1.2 Requirements
- 1.3 Terminology
- 1.4 Overall Operation
- 2.0 Notational Conventions and Generic Grammar
- 2.1 Augmented BNF
- 2.2 Basic Rules
- 3.0 Protocol Parameters
- 3.1 HTTP Version
- 3.2 Uniform Resource Identifiers
- 3.3 Date/Time Formats
- 3.4 Character Sets
- 3.5 Content Codings
- 3.6 Transfer Codings
- 3.6.1 Chunked Transfer Coding
- 3.7 Media Types
- 3.7.1 Canonicalization and Text Defaults
- 3.7.2 Multipart Types
- 3.8 Product Tokens
- 3.9 Quality Values
- 3.10 Language Tags
- 3.11 Entity Tags
- 3.12 Range Units
- 4.0HTTP Message
- 4.1 Message Types
- 4.2 Message Headers
- 4.3 Message Body
- 4.4 Message Length
- 4.5 General Header Fields
- 5.0 Request
- 5.1 Request-Line
- 5.2 The Resource Identified by a Request
- 5.3 Request Header Fields
- 6.0 Response
- 6.1 Status-Line
- 6.1.1 Status Code and Reason Phrase
- 6.2 Response Header Fields
- 7.0 Entity
- 7.1 Entity Header Fields
- 7.2 Entity Body
- 8.0 Connections
- 8.1 Persistent Connections
- 8.2 Message Transmission Requirements
- 8.2.1 Persistent Connections and Flow Control
- 8.2.2 Monitoring Connections for Error Status Messages
- 8.2.3 Use of the 100 (Continue) Status
- 8.2.4 Client Behavior if Server Prematurely Closes Connection
- 9.0 Method Definitions
- 10. Status Code Definitions
- 10.1 Informational 1xx
- 10.2 Successful 2xx
- 10.3 Redirection 3xx
- 10.4 Client Error 4xx
- 10.5 Server Error 5xx
- 11.0 Access Authentication
- 12. Content Negotiation
- 12.1 Server-driven Negotiation
- 12.2 Agent-driven Negotiation
- 12.3 Transparent Negotiation
- 13.0 Caching in HTTP
- 13.1.1 Cache Correctness
- 13.1.2 Warnings
- 13.1.3 Cache-control Mechanisms
- 13.1.4 Explicit User Agent Warnings
- 13.1.5 Exceptions to the Rules and Warnings
- 13.1.6 Client-controlled Behavior
- 13.2 Expiration Model
- 13.2.1 Server-Specified Expiration
- 13.2.2 Heuristic Expiration
- 13.2.3 Age Calculations
- 13.2.4 Expiration Calculations
- 13.2.5 Disambiguating Expiration Values
- 13.2.6 Disambiguating Multiple Responses
- 13.3 Validation Model
- 13.3.1 Last-Modified Dates
- 13.3.2 Entity Tag Cache Validators
- 13.3.3 Weak and Strong Validators
- 13.3.4 Rules for When to Use Entity Tags and Last-Modified Dates.89
- 13.3.5 Non-validating Conditionals
- 13.4 Response Cacheability
- 13.5 Constructing Responses From Caches
- 13.5.1 End-to-end and Hop-by-hop Headers
- 13.5.2 Non-modifiable Headers
- 13.5.3 Combining Headers
- 13.5.4 Combining Byte Ranges
- 13.6 Caching Negotiated Responses
- 13.7 Shared and Non-Shared Caches
- 13.8 Errors or Incomplete Response Cache Behavior
- 13.9 Side Effects of GET and HEAD
- 13.10 Invalidation After Updates or Deletions
- 13.11 Write-Through Mandatory
- 13.12 Cache Replacement
- 13.13 History Lists
- 14.0 Header Field Definitions
- 15.0 Security Considerations
- 15.1 Personal Information
- 15.1.1 Abuse of Server Log Information
- 15.1.2 Transfer of Sensitive Information
- 15.1.3 Encoding Sensitive Information in URI's
- 15.1.4 Privacy Issues Connected to Accept Headers
- 15.2 Attacks Based On File and Path Names
- 15.3 DNS Spoofing
- 15.4 Location Headers and Spoofing
- 15.5 Content-Disposition Issues
- 15.6 Authentication Credentials and Idle Clients
- 15.7 Proxies and Caching
- 15.7.1 Denial of Service Attacks on Proxies
- 16.0 Acknowledgments
- 17.0 References
- 18.0 Authors' Addresses
- 19.0 Appendices
- 19.1 Internet Media Type message/http and application/http
- 19.2 Internet Media Type multipart/byteranges
- 19.3 Tolerant Applications
- 19.4 Differences Between HTTP Entities and RFC 2045 Entities
- 19.4.1 MIME-Version
- 19.4.2 Conversion to Canonical Form
- 19.4.3 Conversion of Date Formats
- 19.4.4 Introduction of Content-Encoding
- 19.4.5 No Content-Transfer-Encoding
- 19.4.6 Introduction of Transfer-Encoding
- 19.4.7 MHTML and Line Length Limitations
- 19.5 Additional Features
- 19.6 Compatibility with Previous Versions
- 19.6.1 Changes from HTTP/1.0
- 19.6.2 Compatibility with HTTP/1.0 Persistent Connections
- 19.6.3 Changes from RFC 2068
- 20.0 Index
- 21.0 Full Copyright Statement
|