Changes between Version 9 and Version 10 of ContentDispositionProducerAdvice


Ignore:
Timestamp:
Jul 14, 2011, 4:55:13 AM (8 years ago)
Author:
mnot@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ContentDispositionProducerAdvice

    v9 v10  
    5858If you are responsible for, or contribute to, one of these frameworks, we'd encourage you to offer a Content-Disposition API along these lines. If you have any questions or problems, please contact [mailto:julian.reschke@gmx.de Julian Reschke] (Content-Disposition editor) or [mailto:mnot@mnot.net Mark Nottingham] (Working Group chair).
    5959
     60=== Framework Tickets and Implementations ===
     61
     62This is a list of implementations and associated tickets that we're aware of:
     63
     64 * [https://github.com/mnot/sweet Sweet] - C-D for Node.JS
     65
    6066
    6167== Frequently Asked Questions ==
     
    7682=== If I follow Appendix D, how will browsers treat it? ===
    7783
    78 Almost all current versions of mainstream browsers will do the right thing; use "filename*" when present. The only exception is Safari, which will fallback to the content of "filename". (Also note that Internet Explorer only started to support RFC 6266 as of version 9).
     84All current releases of mainstream browsers will use "filename*" when present, except for Safari (which falls back to the content of "filename").
     85
     86Internet Explorer versions 6, 7 and 8, as well as Mozilla 3, 3.5 and 4 will use the "filename" parameter even when "filename*" is present.