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

rfc-editor@rfc-editor.org Sat, 07 June 2014 01:16 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 385771A0264 for <ietf-announce@ietfa.amsl.com>; Fri, 6 Jun 2014 18:16:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Iywxf9KpyRxA for <ietf-announce@ietfa.amsl.com>; Fri, 6 Jun 2014 18:16:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) by ietfa.amsl.com (Postfix) with ESMTP id 8ABF21A025F for <ietf-announce@ietf.org>; Fri, 6 Jun 2014 18:16:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 63A0418000D; Fri, 6 Jun 2014 18:15:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7230 on Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140607011547.63A0418000D@rfc-editor.org>
Date: Fri, 6 Jun 2014 18:15:47 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/ImkWWTgk3caynZFu_IbpLK9tta0
Cc: drafts-update-ref@iana.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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: Sat, 07 Jun 2014 01:16:59 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7230

        Title:      Hypertext Transfer Protocol (HTTP/1.1): Message 
                    Syntax and Routing 
        Author:     R. Fielding, Ed.,
                    J. Reschke, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2014
        Mailbox:    fielding@gbiv.com, 
        Pages:      89
        Characters: 205947
        Obsoletes:  RFC 2145, RFC 2616
        Updates:    RFC 2817, RFC 2818

        I-D Tag:    draft-ietf-httpbis-p1-messaging-26.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7230.txt

The Hypertext Transfer Protocol (HTTP) is a stateless
application-level protocol for distributed, collaborative, hypertext
information systems.  This document provides an overview of HTTP
architecture and its associated terminology, defines the "http" and
"https" Uniform Resource Identifier (URI) schemes, defines the
HTTP/1.1 message syntax and parsing requirements, and describes
related security concerns for implementations.

This document is a product of the Hypertext Transfer Protocol Bis Working Group of the IETF.

This is now a Proposed 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 Internet
Official Protocol Standards (STD 1) 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

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

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