RFC 6266 on Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)

rfc-editor@rfc-editor.org Mon, 06 June 2011 16:08 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E584711E8168 for <ietf-announce@ietfa.amsl.com>; Mon, 6 Jun 2011 09:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level:
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M-T3olK3-qSo for <ietf-announce@ietfa.amsl.com>; Mon, 6 Jun 2011 09:08:51 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 9024B11E8137 for <ietf-announce@ietf.org>; Mon, 6 Jun 2011 09:08:51 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 97E4898C4F7; Mon, 6 Jun 2011 09:08:50 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6266 on Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)
From: rfc-editor@rfc-editor.org
Message-Id: <20110606160850.97E4898C4F7@rfc-editor.org>
Date: Mon, 06 Jun 2011 09:08:50 -0700
Cc: ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Mon, 06 Jun 2011 16:08:52 -0000

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

        
        RFC 6266

        Title:      Use of the Content-Disposition Header 
                    Field in the Hypertext Transfer Protocol 
                    (HTTP) 
        Author:     J. Reschke
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2011
        Mailbox:    julian.reschke@greenbytes.de
        Pages:      14
        Characters: 26080
        Updates:    RFC2616

        I-D Tag:    draft-ietf-httpbis-content-disp-09.txt

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

RFC 2616 defines the Content-Disposition response header field, but
points out that it is not part of the HTTP/1.1 Standard.  This
specification takes over the definition and registration of
Content-Disposition, as used in HTTP, and clarifies internationalization
aspects.  [STANDARDS-TRACK]

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

This is now a Proposed Standard Protocol.

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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
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