From: The IESG <email@example.com>
To: IETF-Announce <firstname.lastname@example.org>
Cc: RFC Editor <email@example.com>,
httpbis mailing list <firstname.lastname@example.org>,
httpbis chair <email@example.com>
Subject: Protocol Action: 'Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)' to Proposed Standard (draft-ietf-httpbis-content-disp-09.txt)
The IESG has approved the following document:
- 'Use of the Content-Disposition Header Field in the Hypertext Transfer
(draft-ietf-httpbis-content-disp-09.txt) as a Proposed Standard
This document is the product of the Hypertext Transfer Protocol Bis
The IESG contact persons are Alexey Melnikov and Peter Saint-Andre.
A URL of this Internet Draft is:
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
Working Group Summary
During Last Call, it was asserted that the draft should also specify
error handling for browsers in detail. We improved some aspects
of this in ways that were compatible with existing behaviour,
but did not attempt to proactively specify additional error handling,
as we didn't see broad engagement in the discussion from implementers.
This resolution was not contentious.
There are many existing implementations;
Based on public statements and bug activity, we believe that
implementations will continue to improve.
Mark Nottingham is the Document Shepherd for this document.
Alexey Melnikov is the Responsible Area Director.