Ignore:
Timestamp:
15/09/10 13:34:47 (12 years ago)
Author:
julian.reschke@…
Message:

rephrase the paragraph defining the filename/filename* fallback behavior

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

    r1010 r1011  
    182182  the encoding defined in <xref target="RFC5987"/>, allowing the use
    183183  of characters not present in the ISO-8859-1 character set (<xref target="ISO-8859-1"/>).
    184   When both "filename" and "filename*" are present, a recipient &SHOULD; pick
    185   "filename*" and ignore "filename" - this will make it possible to send the
    186   same header field value to clients that do not support "filename*".
     184</t>
     185<t>
     186  Many user agent implementations predating this specification
     187  do not understand the "filename*" parameter. Therefore, when both "filename"
     188  and "filename*" are present in a single header field value, recipients
     189  &SHOULD; pick "filename*" and ignore "filename". This way, senders
     190  can avoid special-casing specific user agents by sending both the
     191  more expressive "filename*" parameter, and the "filename" parameter
     192  as fallback for legacy recipients (see <xref target="examples"/> for
     193  an example).
    187194</t>
    188195<t>
     
    231238</section> 
    232239
    233 <section title="Examples">
     240<section title="Examples" anchor="examples">
    234241
    235242<figure>
Note: See TracChangeset for help on using the changeset viewer.