- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 06 Feb 2012 10:07:44 +0100
- To: Henrik Nordström <henrik@henriknordstrom.net>
- CC: Willy Tarreau <w@1wt.eu>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
On 2012-02-06 09:42, Henrik Nordström wrote: > mån 2012-02-06 klockan 08:51 +0100 skrev Julian Reschke: > >> It will break some uses of Content-Disposition. It will not fix >> authentication. > > Sorry bad wording from my part. I meant that it breaks some and fix > some, mainly affecting authentication. But yes, the same reasoning also It doesn't affect Basic auth at all, because Basic uses plain-ASCII (so the encoding happens on a different layer). > applies to Content-Disposition. But I do not think that I have seen > non-ascii characters ever work well in Content-Disposition.. Check the issue trackers for Firefox and Chrome, or browse StackOverflow :-) >> But it's a bad idea to open for I18N in field names. >> >> Sure. Did anybody propose that? > > I do not think so. Only mentioned it in case someone had doubts. ok!
Received on Monday, 6 February 2012 09:30:28 UTC