Moves beyond consolidation and actually differs from earlierĭocuments, it supersedes them technically as well as textually.Īlthough SMTP was designed as a mail transport and delivery protocol, Problems of unusual readings or interpretations that have appeared as Mostly by tracking flaming on various lists and newsgroups and This material has been identified in multiple ways, It also includes some additional material from RFC 1123 that requiredĪmplification. RFC 2821 Simple Mail Transfer Protocol April 2001 Those sections are omitted here in the interest of clarity andīrevity readers needing them should refer to RFC 821. Mid-1990s and (in appendices) some additional transport models. Some features that were not in significant use in the Internet by the It obsoletes RFC 821, RFC 974, and updates RFC 1123 (replaces the material drawn from the SMTP Extension mechanisms. the clarifications and applicability statements in RFC 1123 , domain name system requirements and implications for mail the original SMTP (Simple Mail Transfer Protocol) specification of It consolidates, updatesĪnd clarifies, but doesn't add new or change existing functionality This document is a self-contained specification of the basic protocolįor the Internet electronic mail transport. Distribution of this memo is unlimited.Ĭopyright (C) The Internet Society (2001). Official Protocol Standards" (STD 1) for the standardization stateĪnd status of this protocol. Please refer to the current edition of the "Internet Internet community, and requests discussion and suggestions for This document specifies an Internet standards track protocol for the Request for Comments: 2821 AT&T Laboratories Updated by: 5336 Errata Exist Network Working Group J. RFC 7230 HTTP/1.1 Message Syntax and Routing June 2014 1.RFC 2821: Simple Mail Transfer Protocol RFC 7230 HTTP/1.1 Message Syntax and Routing June 2014 8. RFC 7230 HTTP/1.1 Message Syntax and Routing June 2014 3.2.1. http and https URI Normalization and Comparison. It for publication as an RFC or to translate it into languages otherġ. Not be created outside the IETF Standards Process, except to format Outside the IETF Standards Process, and derivative works of it may The copyright in such materials, this document may not be modified Without obtaining an adequate license from the person(s) controlling Modifications of such material outside the IETF Standards Process. Material may not have granted the IETF Trust the right to allow The person(s) controlling the copyright in some of this This document may contain material from IETF Documents or IETFĬontributions published or made publicly available before Novemberġ0, 2008. The Trust Legal Provisions and are provided without warranty as Include Simplified BSD License text as described in Section 4.e of Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal RFC 7230 HTTP/1.1 Message Syntax and Routing June 2014Ĭopyright (c) 2014 IETF Trust and the persons identified as the Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained atįielding & Reschke Standards Track Internet Standards is available in Section 2 of RFC 5741. Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This is an Internet Standards Track document. Syntax and parsing requirements, and describes related security Resource Identifier (URI) schemes, defines the HTTP/1.1 message Its associated terminology, defines the "http" and "https" Uniform This document provides an overview of HTTP architecture and Level protocol for distributed, collaborative, hypertext information The Hypertext Transfer Protocol (HTTP) is a stateless application. Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing Updated by: 8615 Errata Exist Internet Engineering Task Force (IETF) R. Obsoleted by: 9110, 9112 PROPOSED STANDARD RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |