Changeset 1143 for draft-ietf-httpbis-content-disp
- Timestamp:
- 26/02/11 11:26:02 (12 years ago)
- Location:
- draft-ietf-httpbis-content-disp/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html
r1142 r1143 910 910 <p id="rfc.section.D.p.2"> </p> 911 911 <ul> 912 <li>Include a 'filename'parameter when US-ASCII is sufficiently expressive.</li>912 <li>Include a "filename" parameter when US-ASCII is sufficiently expressive.</li> 913 913 <li>Use the 'token' form of the filename parameter only when it does not contain disallowed characters (e.g., spaces); in such 914 914 cases, the quoted-string form should be used. … … 923 923 some will apply heuristics to detect UTF-8, and thus might fail on certain names. 924 924 </li> 925 <li>Include a 'filename*' parameter where the desired filename cannot be expressed faithfully using the 'filename'form. Note926 that legacy user agents will not process this, and will fall back to using the 'filename'parameter's content.927 </li> 928 <li>When a 'filename*' parameter is sent, to also generate a 'filename'parameter as a fallback for user agents that do not support929 the 'filename*'form, if possible. This can be done by substituting characters with US-ASCII sequences (e.g., Unicode character925 <li>Include a "filename*" parameter where the desired filename cannot be expressed faithfully using the "filename" form. Note 926 that legacy user agents will not process this, and will fall back to using the "filename" parameter's content. 927 </li> 928 <li>When a "filename*" parameter is sent, to also generate a "filename" parameter as a fallback for user agents that do not support 929 the "filename*" form, if possible. This can be done by substituting characters with US-ASCII sequences (e.g., Unicode character 930 930 point U+00E4 (LATIN SMALL LETTER A WITH DIARESIS) by "ae"). Note that this may not be possible in some locales. 931 931 </li> 932 <li>When a 'filename' parameter is included as a fallback (as per above), 'filename'should occur first, due to parsing problems932 <li>When a "filename" parameter is included as a fallback (as per above), "filename" should occur first, due to parsing problems 933 933 in some existing implementations. <span class="comment" id="fallbackbug">[<a href="#fallbackbug" class="smpl">fallbackbug</a>: Firefox is known to pick the wrong parameter; a bug fix is scheduled for Firefox 5. --jre]</span> 934 934 </li> 935 <li>Use UTF-8 as the encoding of the 'filename*'parameter, when present, because at least one existing implementation only implements935 <li>Use UTF-8 as the encoding of the "filename*" parameter, when present, because at least one existing implementation only implements 936 936 that encoding. 937 937 </li> -
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml
r1142 r1143 836 836 <t> 837 837 <list style="symbols"> 838 <t>Include a 'filename'parameter when US-ASCII is sufficiently838 <t>Include a "filename" parameter when US-ASCII is sufficiently 839 839 expressive.</t> 840 840 <t>Use the 'token' form of the filename parameter only when it does not … … 851 851 most existing implementations will decode them as ISO-8859-1, some 852 852 will apply heuristics to detect UTF-8, and thus might fail on certain names.</t> 853 <t>Include a 'filename*'parameter where the desired filename cannot be854 expressed faithfully using the 'filename'form. Note that legacy user855 agents will not process this, and will fall back to using the 'filename'853 <t>Include a "filename*" parameter where the desired filename cannot be 854 expressed faithfully using the "filename" form. Note that legacy user 855 agents will not process this, and will fall back to using the "filename" 856 856 parameter's content. 857 857 </t> 858 <t>When a 'filename*' parameter is sent, to also generate a 'filename'859 parameter as a fallback for user agents that do not support the 'filename*'858 <t>When a "filename*" parameter is sent, to also generate a "filename" 859 parameter as a fallback for user agents that do not support the "filename*" 860 860 form, if possible. This can be done by substituting characters with 861 861 US-ASCII sequences (e.g., Unicode character point U+00E4 (LATIN SMALL … … 863 863 some locales. 864 864 </t> 865 <t>When a 'filename'parameter is included as a fallback (as per above),866 'filename'should occur first, due to parsing problems in some existing865 <t>When a "filename" parameter is included as a fallback (as per above), 866 "filename" should occur first, due to parsing problems in some existing 867 867 implementations. 868 868 <cref anchor="fallbackbug" source="jre"> … … 870 870 Firefox 5.</cref> 871 871 </t> 872 <t>Use UTF-8 as the encoding of the 'filename*'parameter, when present,872 <t>Use UTF-8 as the encoding of the "filename*" parameter, when present, 873 873 because at least one existing implementation only implements that encoding.</t> 874 874 </list>
Note: See TracChangeset
for help on using the changeset viewer.