ietf-822
[Top] [All Lists]

Re: RFC2231 encoding in parameters.

2002-12-13 11:19:36

Valdis(_dot_)Kletnieks(_at_)vt(_dot_)edu wrote:

1) Are any MUAs "in the wild" currently actually using the 2047-style encoding
in parameters rather than the 2231 syntax?  If so, who are they, and who wants
to send the authors a note? ;)

As of a couple of months ago, Netscape/Mozilla did so by default.
There is an obscure, undocumented configuration parameter that
can be placed in the configuration file to change that to use
2231 encoding, but (again, as of a couple of months ago) it did
not work:
1. 8-bit file names were first 2047-encoded, then that encoded via
   the 2231 mechanism
2. instead of a single language tag, a language list was used under
   some circumstances.

I think a bug report was submitted, but a quick search at bugzilla
today didn't show anything relevant.

With the obscure configuration parameter in place, Mozilla 1.2a
produced the following (which, as the filename is us-ascii, does not
show problem #1):

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2a) Gecko/20020910
Content-Type: application/excel;
 name*=ISO-8859-1'en-us, en, fr, ru, ja'membership.xls




<Prev in Thread] Current Thread [Next in Thread>
  • Re: RFC2231 encoding in parameters., Bruce Lilly <=