STD 99, RFC 9112 on HTTP/1.1
rfc-editor@rfc-editor.org Mon, 06 June 2022 20:08 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28746C15AAD5 for <ietf-announce@ietfa.amsl.com>; Mon, 6 Jun 2022 13:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.656
X-Spam-Level:
X-Spam-Status: No, score=-1.656 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NyZRQQ_N_2by for <ietf-announce@ietfa.amsl.com>; Mon, 6 Jun 2022 13:08:34 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DBB1C024CCD for <ietf-announce@ietf.org>; Mon, 6 Jun 2022 13:06:22 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 9A01E32F68; Mon, 6 Jun 2022 13:06:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: STD 99, RFC 9112 on HTTP/1.1
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ietf-http-wg@w3.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220606200622.9A01E32F68@rfcpa.amsl.com>
Date: Mon, 06 Jun 2022 13:06:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Yf8COn9bBfxuaUTOVQ68hf_vLEY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2022 20:08:35 -0000
A new Request for Comments is now available in online RFC libraries.
STD 99
RFC 9112
Title: HTTP/1.1
Author: R. Fielding, Ed.,
M. Nottingham, Ed.,
J. Reschke, Ed.
Status: Standards Track
Stream: IETF
Date: June 2022
Mailbox: fielding@gbiv.com,
mnot@mnot.net,
julian.reschke@greenbytes.de
Pages: 46
Obsoletes: RFC 7230
See Also: STD 99
I-D Tag: draft-ietf-httpbis-messaging-19.txt
URL: https://www.rfc-editor.org/info/rfc9112
DOI: 10.17487/RFC9112
The Hypertext Transfer Protocol (HTTP) is a stateless
application-level protocol for distributed, collaborative, hypertext
information systems. This document specifies the HTTP/1.1 message
syntax, message parsing, connection management, and related security
concerns.
This document obsoletes portions of RFC 7230.
This document is a product of the HTTP Working Group of the IETF.
This is now an Internet Standard.
STANDARDS TRACK: 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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
- STD 99, RFC 9112 on HTTP/1.1 rfc-editor