atom feed22 messages in org.w3.public-htmlRe: UA support for Content-Dispositio...
FromSent OnAttachments
Julian ReschkeMar 14, 2008 6:48 am 
Lachlan HuntMar 14, 2008 7:42 am 
Julian ReschkeMar 14, 2008 7:50 am 
Julian ReschkeMar 14, 2008 7:54 am 
Lachlan HuntMar 14, 2008 8:01 am 
Julian ReschkeMar 14, 2008 8:17 am 
Michael A. Puls IIMar 14, 2008 9:25 am 
Julian ReschkeMar 14, 2008 9:38 am 
Brian SmithMar 14, 2008 11:45 am 
Julian ReschkeMar 14, 2008 12:04 pm 
Maciej StachowiakMar 15, 2008 10:54 pm 
Julian ReschkeMar 16, 2008 4:02 am 
Maciej StachowiakMar 16, 2008 11:34 am 
Julian ReschkeMar 16, 2008 12:00 pm 
Maciej StachowiakMar 16, 2008 3:46 pm 
Karl DubostMar 16, 2008 10:56 pm 
Leif Halvard SilliMar 17, 2008 11:45 am 
Julian ReschkeMar 17, 2008 2:35 pm 
Brian SmithMar 18, 2008 9:01 am 
Julian ReschkeMar 18, 2008 9:58 am 
Brian SmithMar 21, 2008 9:24 am 
Julian ReschkeMar 21, 2008 5:07 pm 
Subject:Re: UA support for Content-Disposition header (filename parameter)
From:Michael A. Puls II (shad@gmail.com)
Date:Mar 14, 2008 9:25:50 am
List:org.w3.public-html

On 3/14/08, Julian Reschke <juli@gmx.de> wrote:

Here's a problem that plagued me a few years ago, and I'm pretty sure the situation hasn't improved since then, at least not in IE. Maybe HTML5 should say something about it.

Use case: have the UA offer a "save as" dialogue, including the filename.

Mechanism: Content-Disposition HTTP header, as defined in RFC2616 (<http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.19.5.1>)

Example:

Content-Disposition: attachment; filename=fname.ext

Problem: this works fine in all browsers, as long as the filename does not contain non-Latin1 characters.

RFC 2231 (<http://greenbytes.de/tech/webdav/rfc2231.html>) defines an escaping, and that is supported by Firefox. Example:

Content-Disposition: attachment; filename*=utf8''D%C3%BCrst.ext

IE does not support RFC 2231 (as of IE7), but allows percent escaped UTF-8, such as in:

Content-Disposition: attachment; filename=D%C3%BCrst.ext

However, that only works when IE is configured for UTF-8 URL encoding, which is (as far as I recall) not the default in countries using Asian languages.

Proposal: require UAs to support RFC 2231 (UTF-8 variant).

Reminds me of this thread: < http://my.opera.com/community/forums/topic.dml?id=118971 >

The solution at the end was to detect IE via the user agent header, do IE's way for the filename and do the RFC 2231 way for others. But, that's assumes UTF-8 URL encoding is turned on in IE.

It'd be nice if IE supported the RFC 2231 way.