RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing

request for comments publication

RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing is …
instance of (P31):
Request for CommentsQ212971

External links are
P8978DBLP publication IDjournals/rfc/rfc7230
P356DOI10.17487/RFC7230
P953full work available at URLhttps://tools.ietf.org/html/rfc7230
https://tools.ietf.org/rfc/rfc7230.txt
https://www.rfc-editor.org/pdfrfc/rfc7230.txt.pdf
https://www.rfc-editor.org/rfc/rfc7230.txt
P892RfC ID7230

P2567amended byRFC 8615: Well-Known Uniform Resource Identifiers (URIs)Q64831214
P50authorRoy FieldingQ93076
Julian ReschkeQ53929736
P144based onRFC 2818: HTTP Over TLSQ47466349
RFC 2817: Upgrading to TLS Within HTTP/1.1Q47484555
P2860cites workRFC 5234: Augmented BNF for Syntax Specifications: ABNFQ26701848
RFC 1951: DEFLATE Compressed Data Format Specification version 1.3Q27196723
RFC 1952: GZIP file format specification version 4.3Q27907428
RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): CachingQ47271545
RFC 6585: Additional HTTP Status CodesQ47285048
RFC 6838: Media Type Specifications and Registration ProceduresQ47397229
RFC 3040: Internet Web Replication and Caching TaxonomyQ47455099
RFC 2047: MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII TextQ47455314
RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsQ47458862
RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2Q47461639
RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message BodiesQ47464154
RFC 2145: Use and Interpretation of HTTP Version NumbersQ47464293
RFC 2818: HTTP Over TLSQ47466349
RFC 793: Transmission Control ProtocolQ47466552
RFC 4559: SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft WindowsQ47468571
RFC 4033: DNS Security Introduction and RequirementsQ47469381
RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1Q47469725
RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCsQ47470377
RFC 4395: Guidelines and Registration Procedures for New URI SchemesQ47470429
RFC 1919: Classical versus Transparent IP ProxiesQ47470440
RFC 3986: Uniform Resource Identifier (URI): Generic SyntaxQ47470736
RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and ContentQ47470878
RFC 2068: Hypertext Transfer Protocol -- HTTP/1.1Q47470889
RFC 6265: HTTP State Management MechanismQ47472198
RFC 7232: Hypertext Transfer Protocol (HTTP/1.1): Conditional RequestsQ47472234
RFC 1945: Hypertext Transfer Protocol -- HTTP/1.0Q47472343
RFC 7233: Hypertext Transfer Protocol (HTTP/1.1): Range RequestsQ47473076
RFC 3864: Registration Procedures for Message Header FieldsQ47477108
RFC 7235: Hypertext Transfer Protocol (HTTP/1.1): AuthenticationQ47477946
RFC 1950: ZLIB Compressed Data Format Specification version 3.3Q47480254
RFC 2817: Upgrading to TLS Within HTTP/1.1Q47484555
RFC 5322: Internet Message FormatQ47485091
P407language of work or nameEnglishQ1860
P921main subjectHTTP/1.1Q30500573
P1104number of pages89
P577publication date2014-06-01
P123publisherInternet Engineering Task ForceQ217082
P1366replaced byRFC 9110: HTTP SemanticsQ112263672
RFC 9112: HTTP/1.1Q112264943
P1365replacesRFC 2145: Use and Interpretation of HTTP Version NumbersQ47464293
RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1Q47469725
P1476titleHypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing

Reverse relations

replaces (P1365)
Q112263672RFC 9110: HTTP Semantics
Q112264943RFC 9112: HTTP/1.1

replaced by (P1366)
Q47464293RFC 2145: Use and Interpretation of HTTP Version Numbers
Q47469725RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1

amended by (P2567)
Q47484555RFC 2817: Upgrading to TLS Within HTTP/1.1
Q47466349RFC 2818: HTTP Over TLS

cites work (P2860)
Q57881483InterPlanetary Wayback: Peer-To-Peer Permanence of Web Archives
Q47205413RFC 7301: Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension
Q47477144RFC 7826: Real-Time Streaming Protocol Version 2.0
Q56055033RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3

implementation of (P4428)
Q28916296Apache HttpComponents Client
Q28916297Apache HttpComponents Core

Q64831214RFC 8615: Well-Known Uniform Resource Identifiers (URIs)based onP144
Q30500573HTTP/1.1described by sourceP1343

Search more.