2616: Hypertext Transfer Protocol -- HTTP/1.1.
HTML
TXT
PS
PDF
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.
Status DRAFT STANDARD
Format TXT=422317, PS=5529857, PDF=550558 bytes
Authors
T. Berners-Lee
P. Leach
L. Masinter
H. Frystyk
J. Mogul
J. Gettys
Date June 1999
Keyphrases header response request entity
Updated by
Obsoletes
References
Referenced by
- RFC2617: HTTP Authentication: Basic and Digest Access Authentication.
- RFC2639: Internet Printing Protocol/1.0: Implementer's Guide.
- RFC2653: CIP Transport Protocols.
- RFC2660: The Secure HyperText Transfer Protocol.
- RFC2756: Hyper Text Caching Protocol (HTCP/0.0).
- RFC2781: UTF-16, an encoding of ISO 10646.
- RFC2801: Internet Open Trading Protocol - IOTP Version 1.0.
- RFC2817: Upgrading to TLS Within HTTP/1.1.
- RFC2818: HTTP Over
- RFC2828: Internet Security Glossary.
- RFC2831: Using Digest Authentication as a SASL Mechanism.
- RFC2854: The 'text/html' Media Type.
- RFC2910: Internet Printing Protocol/1.1: Encoding and Transport.
- RFC2911: Internet Printing Protocol/1.1: Model and Semantics.
- RFC2914: Congestion Control Principles.
- RFC2935: Internet Open Trading Protocol (IOTP) HTTP Supplement.
- RFC2936: HTTP MIME Type Handler Detection.
- RFC2965: HTTP State Management Mechanism.
- RFC3002: Overview of 2000 IAB Wireless Internetworking Workshop.
- RFC3023: XML Media Types.
- RFC3040: Internet Web Replication and Caching Taxonomy.
- RFC3050: Common Gateway Interface for
- RFC3066: Tags for the Identification of Languages.
- RFC3075: XML-Signature Syntax and Processing.
- RFC3117: On the Design of Application Protocols.
- RFC3143: Known HTTP Proxy/Caching Problems.
- RFC3150: End-to-end Performance Implications of Slow Links.
- RFC3155: End-to-end Performance Implications of Links with Errors.
- RFC3157: Securely Available Credentials - Requirements.
- RFC3165: Definitions of Managed Objects for the Delegation of Management Scripts.
- RFC3196: Internet Printing Protocol/1.1: Implementor's Guide.
- RFC3205: On the use of HTTP as a Substrate.
- RFC3229: Delta encoding in
- RFC3230: Instance Digests in
- RFC3234: Middleboxes: Taxonomy and Issues.
- RFC3239: Internet Printing Protocol (IPP): Requirements for Job, Printer, and Device Administrative Operations.
- RFC3253: Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning).
- RFC3261: SIP: Session Initiation Protocol.
- RFC3265: Session Initiation Protocol (SIP)-Specific Event Notification.
- RFC3275: (Extensible Markup Language) XML-Signature Syntax and Processing.
- RFC3282: Content Language Headers.
- RFC3288: Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP).
- RFC3297: Content Negotiation for Messaging Services based on Email.
- RFC3305: Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations.
- RFC3367: Common Name Resolution Protocol (CNRP).
- RFC3380: Internet Printing Protocol (IPP): Job and Printer Set Operations.
- RFC3381: Internet Printing Protocol (IPP): Job Progress Attributes.
- RFC3382: Internet Printing Protocol (IPP): The 'collection' attribute syntax.
- RFC3390: Increasing TCP's Initial Window.
- RFC3395: Remote Network Monitoring MIB Protocol Identifier Reference Extensions.
- RFC3450: Asynchronous Layered Coding (ALC) Protocol Instantiation.
- RFC3451: Layered Coding Transport (LCT) Building Block.
- RFC3466: A Model for Content Internetworking (CDI).
- RFC3489: STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs).
- RFC3507: Internet Content Adaptation Protocol (ICAP).
- RFC3510: Internet Printing Protocol/1.1: IPP URL Scheme.
- RFC3511: Benchmarking Methodology for Firewall Performance.
- RFC3529: Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP).
- RFC3546: Transport Layer Security (TLS) Extensions.
- RFC3552: Guidelines for Writing RFC Text on Security Considerations.
- RFC3568: Known Content Network (CN) Request-Routing Mechanisms.
- RFC3617: Uniform Resource Identifier (URI) Scheme and Applicability Statement for the Trivial File Transfer Protocol (TFTP).
- RFC3648: Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol.
- RFC3675: .sex Considered Dangerous.
- RFC3696: Application Techniques for Checking and Transformation of Names.
- RFC3709: Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates.
- RFC3739: Internet X.509 Public Key Infrastructure: Qualified Certificates Profile.
- RFC3744: Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol.
- RFC3752: Open Pluggable Edge Services (OPES) Use Cases and Deployment Scenarios.
- RFC3760: Securely Available Credentials (SACRED) - Credential Server Framework.
- RFC3778: The application/pdf Media Type.
- RFC3795: Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents.
- RFC3805: Printer MIB v2.
- RFC3819: Advice for Internet Subnetwork Designers.
- RFC3835: An Architecture for Open Pluggable Edge Services (OPES).
- RFC3836: Requirements for Open Pluggable Edge Services (OPES) Callout Protocols.
- RFC3838: Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES).
- RFC3862: Common Presence and Instant Messaging (CPIM): Message Format.
- RFC3864: Registration Procedures for Message Header Fields.
- RFC3875: The Common Gateway Interface (CGI) Version 1.1.
- RFC3903: Session Initiation Protocol (SIP) Extension for Event State Publication.
- RFC3914: Open Pluggable Edge Services (OPES) Treatment of IAB Considerations.
- RFC3920: Extensible Messaging and Presence Protocol (XMPP): Core.
- RFC3926: FLUTE - File Delivery over Unidirectional Transport.
- RFC3977: Network News Transfer Protocol (NNTP).
- RFC3983: Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP).
- RFC3987: Internationalized Resource Identifiers (IRIs).
- RFC3995: Internet Printing Protocol (IPP): Event Notifications and Subscriptions.
- RFC3996: Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event Notifications.
- RFC3997: Internet Printing Protocol (IPP): Requirements for IPP Notifications.
- RFC3998: Internet Printing Protocol (IPP): Job and Printer Administrative Operations.
- RFC4002: IANA Registration for Enumservice 'web' and 'ft'.
- RFC4037: Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core.
- RFC4047: MIME Sub-type Registrations for Flexible Image Transport System (FITS).
- RFC4130: MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2).
- RFC4145: TCP-Based Media Transport in the Session Description Protocol (SDP).
- RFC4227: Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP).
- RFC4229: HTTP Header Field Registrations.
- RFC4236: HTTP Adaptation with Open Pluggable Edge Services (OPES).
- RFC4249: Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components.
- RFC4263: Media Subtype Registration for Media Type text/troff.
- RFC4297: Remote Direct Memory Access (RDMA) over IP Problem Statement.
- RFC4325: Internet X.509 Public Key Infrastructure Authority Information Access Certificate Revocation List (CRL) Extension.
- RFC4356: Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail.
- RFC4366: Transport Layer Security (TLS) Extensions.
- RFC4367: What's in a Name: False Assumptions about DNS Names.
- RFC4387: Internet X.509 Public Key Infrastructure Operational Protocols: Certificate Store Access via
- RFC4403: Lightweight Directory Access Protocol (LDAP) Schema for Universal Description, Discovery, and Integration version 3 (UDDIv3).
- RFC4416: Goals for Internet Messaging to Support Diverse Service Environments.
- RFC4435: A Framework for the Usage of Internet Media Guides (IMGs).
- RFC4437: Web Distributed Authoring and Versioning (WebDAV) Redirect Reference Resources.
- RFC4463: A Media Resource Control Protocol (MRCP) Developed by Cisco, Nuance, and Speechworks.
- RFC4473: Requirements for Internet Media Guides (IMGs).
- RFC4485: Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP).
- RFC4496: Open Pluggable Edge Services (OPES) SMTP Use Cases.
- RFC4559: SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows.
- RFC4639: Cable Device Management Information Base for Data-Over-Cable Service Interface Specification (DOCSIS) Compliant Cable Modems and Cable Modem Termination Systems.
- RFC4647: Matching of Language Tags.
- RFC4682: Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant Devices.
- RFC4695: RTP Payload Format for
- RFC4707: Netnews Administration System (NAS).
- RFC4709: Mounting Web Distributed Authoring and Versioning (WebDAV) Servers.
- RFC4758: Cryptographic Token Key Initialization Protocol (CT-KIP) Version 1.0 Revision 1.