- From: Adam Barth <w3c@adambarth.com>
- Date: Sun, 3 Oct 2010 14:04:51 -0700
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
On Sun, Oct 3, 2010 at 1:59 PM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote: > * Adam Barth wrote: >>Concretely, my proposal is that the specification should not forbid >>user agents from %-decoding the value of the filename parameter. >>Julian has agreed that neither Internet Explorer nor Chrome is going >>to stop %-decoding the filename parameter anytime soon. Forbidding >>user agent from processing these messages in this way is fiction. > > The file name is advisory only. Implementations removing %-encoding may > be unfortunate, just like implementations stripping all but the first > eight [a-z] characters may be unfortunate, but they are not in violation > of the specification, as the file name is advisory only. That there may > be problems using % in file names is already noted in the draft. So, we > can move on with the draft as it is. I am glad we cleared this up. So, your position is that the document is meaningless then? That's silly. Why bother introducing filename* then if we don't care how user agents actually interpret the file name? Adam
Received on Sunday, 3 October 2010 21:12:10 UTC