- From: Adam Barth <ietf@adambarth.com>
- Date: Tue, 2 Nov 2010 01:56:30 -0700
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Mark Nottingham <mnot@mnot.net>, httpbis <ietf-http-wg@w3.org>
On Tue, Nov 2, 2010 at 1:49 AM, Julian Reschke <julian.reschke@gmx.de> wrote: >>> http://tools.ietf.org/html/draft-ietf-httpbis-content-disp-03#section-3.3 >>> >>> This section provides very little guidance about how to extract a file >>> name from the filename parameter. For example, it fails to instruct >>> the user agent about how to handle the following test cases: >>> >>> http://greenbytes.de/tech/tc2231/#attwithasciifnescapedquote >>> http://greenbytes.de/tech/tc2231/#attwithasciifilenamenqws >>> http://greenbytes.de/tech/tc2231/#attwithutf8fnplain >>> http://greenbytes.de/tech/tc2231/#attwithfnrawpctenca >>> http://greenbytes.de/tech/tc2231/#attwith2filenames >>> http://greenbytes.de/tech/tc2231/#attfnbrokentoken >>> http://greenbytes.de/tech/tc2231/#attbrokenquotedfn >> >> Ticket: >> http://trac.tools.ietf.org/wg/httpbis/trac/ticket/261 >> >> >>> In particular, this document should define an algorithm that takes as >>> input a sequence of bytes obtained by parsing the Content-Disposition >>> header field value and returns a sequence of characters which is the >>> file name requested by the server. >> >> I'm treating that as editorial advice. > > I'm not sure where to start :-) > > Like it or not, the draft relies on the ABNF for parameter parsing, and > delegates the filename* format to RFC 5987. > > For valid header field instances this is supposed to be sufficient. If it's > not, let's focus on details. Would it be helpful if I went through the valid > header field instances in these test cases and explained how they parse? I'm more interested in the invalid header field instances. This document doesn't explain how to parse them, much less how to process them. Adam
Received on Tuesday, 2 November 2010 08:57:35 UTC