[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2302: update the Content-Disposition and filename stuff for modern standards and practice

[Tahoe-LAFS]

#2302: update the Content-Disposition and filename stuff for modern standards and
practice
-------------------------------+------------------------
 Reporter:  zooko              |          Owner:
     Type:  defect             |         Status:  new
 Priority:  normal             |      Milestone:  1.12.0
Component:  code-frontend-web  |        Version:  1.10.0
 Keywords:  unicode i18n       |  Launchpad Bug:
-------------------------------+------------------------
 I was just looking at
 [source:trunk/docs/frontends/webapi.rst?rev=0ef593947755a8b81edc73d033219724268faf80#id3
 webapi.rst], and wondering how relevant is the discussion of Internet
 Explorer 7's limitations. I looked at http://www.w3counter.com/trends and
 it told me that currently IE7 accounts for 2.1% of all web browsers. I
 also followed the links to the web standards and determined that the
 modern [https://tools.ietf.org/html/rfc5987#section-3.2 RFC 5987 §3.2]
 requires user agents to support UTF-8, and that it forbids implementations
 from ''failing'' to specify the charset. Great! But, it turns out that the
 new standard applies to a new key, spelled {{{filename*}}} instead of
 {{{filename}}}.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2302>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage