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:Brian Smith (bri@briansmith.org)
Date:Mar 14, 2008 11:45:04 am
List:org.w3.public-html

Julian Reschke wrote:

Michael A. Puls II wrote:

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.

Right, and that's what we did back then. That worked for FF users, IE users in western countries, but not for Asian users.

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

Right.

And, to get there, I think it would be good if HTML5 stated that as a requirement.

The IE encoding is a lot better. In order to support clients using it in
requests, I have to be able to parse the filename, and the IE syntax is much,
much easier to parse than the 2231-based syntax. Why not file a bug report
against IE so that it works all the time?

I also agree with the others that this isn't something that should be
standardized in HTML, because it is not specific to HTML. I am implementing
support for this (in both requests and responses) to my AtomPub implementations,
for example. A seperate RFC for a *HTTP* Content-Disposition mechanism makes
much more sense for use by non-HTML software. Make the IE syntax for the
"filename" parameter the standard, and allow an additional "filename*" parameter
for backwards-compatibility with UA's that implement the 2231 mechanism.

- Brian