Content-Disposition filename encoding, was: IRIs, IDNAbis, and HTTP [i74]

Hi,

our discussion about RFC2047 reminded me of an interop problem that I 
encountered years ago when serving content "for download", using the 
Content-Disposition header in general and the "filename" parameter in 
particular.

The only documented and partly implemented solution for I18N is RFC2231, 
which is supported by FF and Opera (atleast the essential parts). IE 
doesn't support this, and Safari apparently doesn't yet (but has an 
issue open regarding this).

I raised the topic on the HTML WG's mailing list, but so far nobody 
seems to believe it's something they should include (quite surprisingly 
to me...).

As RFC2616 doesn't really include Content-Disposition, nor requires 
RFC2231, it doesn't seem to be in our charter to do something.

Any suggestions about what should be done here; except for waiting that 
the remaining UA vendors just implement this?

BR, Julian

Received on Sunday, 16 March 2008 19:16:11 UTC