Changes between Version 16 and Version 17 of ContentDispositionErrorHandling


Ignore:
Timestamp:
Dec 13, 2010, 1:57:48 AM (9 years ago)
Author:
ietf@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ContentDispositionErrorHandling

    v16 v17  
    2525
    2626  ...parse the field value into a disp-type (disposition type) and a
    27   sequence of parameters (pairs of name (token) and value).
     27  sequence of parameters (pairs of name (token) and value). Lower-case
     28  all disposition types and parameter names.
    2829
    2930  If the field value does not conform to the grammar (such as when not
     
    5354  HTTP message, and results in a sequence of Unicode characters.
    5455
     565.5.  Extracting the Disposition Type
     57
     58  The parsing step (Appendix 5.2) has returned the disposition type (to
     59  be matched case-insensitively), which can be "attachment", "inline",
     60  or an extension type.  If the type is unknown, treat it like
     61  "attachment" (see Section 3.2).
     62
     635.6.  Determining the File Name
     64
     65  The parsing and post-processing steps resulted in a set of parameters
     66  (name/value pairs).  The suggested file name is the value of the
     67  "filename*" parameter (when present), otherwise the value of the
     68  "filename" parameter.
     69
     70  If neither is given, the UA can determine a name based on the
     71  associated URI; for instance based on the last path segment.
     72
     73  Otherwise, the UA ought to post-process the suggested filename
     74  according following Section 3.3. [[anchor10: We could say here that
     75  UAs may reject filenames for security reasons, such as those with a
     76  path separator character.]]
    5577
    5678