Changes between Version 4 and Version 5 of ContentDispositionErrorHandling


Ignore:
Timestamp:
Dec 2, 2010, 12:08:17 AM (9 years ago)
Author:
ietf@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ContentDispositionErrorHandling

    v4 v5  
    1717parsed by the grammar above, return the empty string.
    1818
    19 
    2019== Decoding the File Name ==
    2120
     
    3231they appear in the encoded-string:
    3332
    34   1) If the gramatical element is a delimiter, emit a SP character.
    35 
    36   2) If the gramatical element is a word, process the element as follows:
    37 
    38        a) If the word contains non-ASCII characters, emit the word (decoded as ISO-8859-1) and proceed to the next gramatical element.
    39 
    40        b) Let the url-unescaped-word be the word %-unescaped.
    41 
    42        c) Emit the url-unescaped-word (decoded as UTF-8) and proceed to the next grammatical element.  (There's actually more sadness here if the url-unescaped-word isn't valid UTF-8.)
     33 1. If the gramatical element is a delimiter, emit a SP character.
     34 2. If the gramatical element is a word, process the element as follows:
     35  a. If the word contains non-ASCII characters, emit the word (decoded as ISO-8859-1) and proceed to the next gramatical element.
     36  b. Let the url-unescaped-word be the word %-unescaped.
     37  c. Emit the url-unescaped-word (decoded as UTF-8) and proceed to the next grammatical element.  (There's actually more sadness here if the url-unescaped-word isn't valid UTF-8.)
    4338
    4439The emitted characters are the decoded file name.
    45 
    4640
    4741== Determining the File Name ==
     
    5044the following algorithm:
    5145
    52   1) Let filename-star be the value extracted from the Content-Disposition header field for for the "filename*" parameter.
    53 
    54   2) If filename-star parses as a RFC5987-value, return the RFC5987-value of filename-star and abort these steps.
    55 
    56   3) Let filename be the value extracted from the Content-Disposition header field for the "filename" parameter.
    57 
    58   4) If filename is empty, instead let filename be the value extracted from the Content-Disposition header field for the "name" parameter.
    59 
    60   5) If filename is empty, return the empty string and abort these steps.
    61 
    62   6) Return the filename-decoding of filename.
    63 
     46 1. Let filename-star be the value extracted from the Content-Disposition header field for for the "filename*" parameter.
     47 2. If filename-star parses as a RFC5987-value, return the RFC5987-value of filename-star and abort these steps.
     48 3. Let filename be the value extracted from the Content-Disposition header field for the "filename" parameter.
     49 4. If filename is empty, instead let filename be the value extracted from the Content-Disposition header field for the "name" parameter.
     50 5. If filename is empty, return the empty string and abort these steps.
     51 6. Return the filename-decoding of filename.
    6452
    6553== Determining the Disposition ==
     
    8270To process the Content-Disposition header field, use the following algorithm:
    8371
    84   1) Determine the disposition-type.
    85 
    86   2) If the disposition-type is "inline", then ...
    87 
    88   3) If the disposition-type is "attachment", then let filename be the file name indicated by the header field.  ...
     72 1. Determine the disposition-type.
     73 2. If the disposition-type is "inline", then ...
     74 3. If the disposition-type is "attachment", then let filename be the file name indicated by the header field.  ...