Changes between Version 15 and Version 16 of ContentDispositionErrorHandling


Ignore:
Timestamp:
13/12/10 09:56:00 (10 years ago)
Author:
ietf@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ContentDispositionErrorHandling

    v15 v16  
    11= A proposal for optional error handling in processing the Content-Disposition header field =
     2
     3== Text from Julian ==
     4
     55.  Parsing
     6
     7  This document does not require any specific handling of invalid
     8  header field values.  With this in mind, the text below describes a
     9  simple strategy for parsing the header field and detecting problems
     10  in general, or in specific parameters.
     11
     125.1.  Combine Multiple Instances of Content-Disposition
     13
     14  If the HTTP message contains multiple instances of the Content-
     15  Disposition header field, combine all field values into a single one
     16  as specified in Section 4.2 of [RFC2616].
     17
     185.2.  Parsing for Disposition Type and Parameters
     19
     20  Using the simplified grammar below:
     21
     22    field-value = disp-type *( ";" param )
     23    disp-type   = token
     24    param       = token "=" value
     25
     26  ...parse the field value into a disp-type (disposition type) and a
     27  sequence of parameters (pairs of name (token) and value).
     28
     29  If the field value does not conform to the grammar (such as when not
     30  exactly one disposition type is specified), ignore the whole header
     31  field.
     32
     335.3.  Checking Cardinality Constraints
     34
     35  If the parameter sequence contains multiple instances of the same
     36  parameter name, ignore the whole header field.
     37
     385.4.  Post-Process Parameter Values
     39
     40  For each parameter, post-process the associated value part according
     41  to the grammar:
     42
     43  o  According to Section 3.2.1 of [RFC5987] for parameters using the
     44     RFC 5987 syntax (such as "filename*").  If this fails, just ignore
     45     this parameter.
     46
     47  o  According to the grammar for quoted-string (Section 2.2 of
     48     [RFC2616]) for values starting with a double quote character (").
     49
     50  o  Verbatim otherwise.
     51
     52  Note that this step starts with an octet sequence obtained from the
     53  HTTP message, and results in a sequence of Unicode characters.
     54
     55
    256
    357== Extracting Parameter Values From Header Fields ==