W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2010

Re: [#259] Handling invalid Content-Dispostion headers

From: Maciej Stachowiak <mjs@apple.com>
Date: Thu, 04 Nov 2010 17:48:17 +0100
Cc: httpbis Group <ietf-http-wg@w3.org>, Adam Barth <ietf@adambarth.com>
Message-id: <CF0ECFA0-5F00-4C06-88A9-88B83B36D970@apple.com>
To: Mark Nottingham <mnot@mnot.net>

I think such a profile would be useful, both for Content-Disposition and potentially for other HTTP header values.


On Nov 4, 2010, at 3:42 AM, Mark Nottingham wrote:

> In looking at Adam's feedback and the resulting discussion, I'm considering whether we should try to define an OPTIONAL error-handling profile that defines a method of handling invalid Content-Disposition field-values.
> E.g., this could be an appendix to the specification that lists a set of behaviours, such as:
>  - when there are multiple parameters with the same value, choose the first one
>  - when there are characters that aren't allowed in the BNF, transform them to...
>  - etc.
> that implementers could follow if they wish to. Other specifications could, at their option, require conformance to such a profile.
> By necessity, such a thing would not duplicate requirements from the authoritative text, would not override those requirements, and it would not provide alternate algorithms.
> To help figure out if this is a productive way to go, I'd like to hear:
> a) thoughts from folks about this approach, and 
> b) some indication of who'd be willing to contribute text and/or time for testing, and 
> c) expressions of interest from implementers in such an optional profile (i.e., an indication that it's something they'd find useful).
> </chair hat>
> Regards,
> --
> Mark Nottingham   http://www.mnot.net/
Received on Thursday, 4 November 2010 16:48:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:55 UTC