RFC 2616:Hypertext Transfer Protocol -- HTTP/1.1
RFC-Ref

RFC - 2616

Hypertext Transfer Protocol -- HTTP/1.1

Original: ftp://ftp.isi.edu/in-notes/rfc2616.txt
Authors: R. Fielding [Compaq/W3C], UC Irvine [Compaq/W3C], J. Gettys [Compaq/W3C], J. Mogul [Compaq], H. Frystyk [W3C/MIT], L. Masinter [Xerox], P. Leach [Microsoft], T. Berners-Lee [W3C/MIT]
Date: June 1999
Category: Draft Standard



Obsoletes:
RFC-2068 Hypertext Transfer Protocol -- HTTP/1.1 (Obsoleted by RFC-2616draft)

Updated by:
RFC-2817 Upgrading to TLS Within HTTP/1.1

Referred by: 134 RFC
Refers to: 42 RFC

Status

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.

Abstract

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(-> 2616draft) [33].


About Resource

Google
Web
RFC-Ref