[Fwd: RFC 2183 on Content-Disposition]

There are two issues currently labelled 'DISPOSITION', 43 and 204.
The additional issue that Content-Disposition in HTTP isn't the
same as RFC 2183 is either an augmentation, or, more likely,
a separate issue.


Forwarded message 1

  • From: RFC Editor <rfc-ed@ISI.EDU>
  • Date: Tue, 2 Sep 1997 09:25:06 PDT
  • Subject: RFC 2183 on Content-Disposition
  • cc: rfc-ed@ISI.EDU
  • Message-ID: <199709021625.AA22676@zephyr.isi.edu>
A new Request for Comments is now available in online RFC libraries.

        RFC 2183:  

        Title:      Communicating Presentation Information in
                    Internet Messages:
                    The Content-Disposition Header Field
	Author:     R. Troost, S. Dorner, K. Moore, Editor
        Date:       August 1997
        Mailbox:    rens@century.com, sdorner@qualcomm.com,
        Pages:      12
        Characters: 23158
        Updates:    1806

        URL:        ftp://ds.internic.net/rfc/rfc2183.txt

This memo provides a mechanism whereby messages conforming to the MIME
specifications [RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049] can
convey presentational information.  It specifies the
"Content-Disposition" header field, which is optional and valid for
any MIME entity ("message" or "body part").

This is now a Proposed Standard Protocol.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

Received on Tuesday, 2 September 1997 17:26:16 UTC