RFC 2612

위키문헌 ― 우리 모두의 도서관.
둘러보기로 가기 검색하러 가기

RFC 2612는 1999년에 7월에 발행된 문서로서, HTTP/1.1에 관한 내용을 담고 있다.

머리말[편집]

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.

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 [33].

서론[편집]

목적(Purpose)[편집]

원문

The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World-Wide Web global information initiative since 1990. The first version of HTTP, referred to as HTTP/0.9, was a simple protocol for raw data transfer across the Internet. HTTP/1.0, as defined by RFC 1945 [6], improved the protocol by allowing messages to be in the format of MIME-like messages, containing meta information about the data transferred and modifiers on the request/response semantics. However, HTTP/1.0 does not sufficiently take into consideration the effects of hierarchical proxies, caching, the need for persistent connections, or virtual hosts. In addition, the proliferation of incompletely-implemented applications calling themselves "HTTP/1.0" has necessitated a protocol version change in order for two communicating applications to determine each other's true capabilities.

This specification defines the protocol referred to as "HTTP/1.1". This protocol includes more stringent requirements than HTTP/1.0 in order to ensure reliable implementation of its features.

Practical information systems require more functionality than simple retrieval, including search, front-end update, and annotation. HTTP allows an open-ended set of methods and headers that indicate the purpose of a request [47]. It builds on the discipline of reference provided by the Uniform Resource Identifier (URI) [3], as a location (URL) [4] or name (URN) [20], for indicating the resource to which a method is to be applied. Messages are passed in a format similar to that used by Internet mail [9] as defined by the Multipurpose Internet Mail Extensions (MIME) [7].

HTTP is also used as a generic protocol for communication between user agents and proxies/gateways to other Internet systems, including those supported by the SMTP [16], NNTP [13], FTP [18], Gopher [2], and WAIS [10] protocols. In this way, HTTP allows basic hypermedia access to resources available from diverse applications.

번역문

하이퍼텍스는 전송 규약(HTTP)는 분산 정보시스템, 종합 정보시스템 및 하이퍼미디어 정보시스템의 응용계층의 규약이다. HTTP는 World Wide Web의 범 세계적인 계획에 의해서 1990년 이래로 사용되어지고 있다. HTTP의 첫 버전은 HTTP/0.9인데, 이것은 인터넷 상에 존재하는 로우 데이터(raw data) 전송에 관한 단순한 규약이었다. RFC 1945에 의해 정의되어진 HTTP/1.0은 MINE과 같은 형식의 메시지를 허용하고, 전송된 데이터와 요구/응답 의미에 대한 수정자에 관한 메타 정보를 포함시킴으로써 개선시켰다.

필요사항(Requirements)[편집]

용어(Terminology)[편집]

Overall Operation[편집]

표기법에 대한 관례와 일반적인 문법[편집]

프로토콜 피라미터(Protocol Parameter)[편집]

HTTP 메시지(HTTP Message)[편집]

요구(Request)[편집]

응답(Response)[편집]

엔터티(Entity)[편집]

접속(Connection)[편집]

Method 정의(Method Definition)[편집]

상태 코드 정의(Status Code Definition)[편집]

접근 인증(Access Authentication)[편집]

Content Negotiation[편집]

Caching in HTTP[편집]

헤더필드 정의(Header Field Definitions)[편집]

보안에 대한 고려사항(Security Considerations)[편집]

감사의 말(Acknowledgments)[편집]

참고 문헌(References)[편집]

저자 주소(Authors' Addresses)[편집]

부록(Appendices)[편집]

Full Copyright Statement[편집]

Copyright (C) The Internet Society (1999). All Rights Reserved.

  This document and translations of it may be copied and furnished to
  others, and derivative works that comment on or otherwise explain it
  or assist in its implementation may be prepared, copied, published
  and distributed, in whole or in part, without restriction of any
  kind, provided that the above copyright notice and this paragraph are
  included on all such copies and derivative works.  However, this
  document itself may not be modified in any way, such as by removing
  the copyright notice or references to the Internet Society or other
  Internet organizations, except as needed for the purpose of
  developing Internet standards in which case the procedures for
  copyrights defined in the Internet Standards process must be
  followed, or as required to translate it into languages other than
  English.
  The limited permissions granted above are perpetual and will not be
  revoked by the Internet Society or its successors or assigns.
  This document and the information contained herein is provided on an
  "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
  TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
  BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
  HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
  MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

  Funding for the RFC Editor function is currently provided by the
  Internet Society.