![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changes between Version 18 and Version 19 of ContentDispositionErrorHandling
- Timestamp:
- 13/12/10 10:01:20 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ContentDispositionErrorHandling
v18 v19 1 1 = A proposal for optional error handling in processing the Content-Disposition header field = 2 3 == Text from Julian ==4 5 5. Parsing6 2 7 3 This document does not require any specific handling of invalid … … 10 6 in general, or in specific parameters. 11 7 12 5.1. Combine Multiple Instances of Content-Disposition 8 == Combine Multiple Instances of Content-Disposition == 13 9 14 10 If the HTTP message contains multiple instances of the Content- … … 16 12 as specified in Section 4.2 of [RFC2616]. 17 13 18 5.2. Parsing for Disposition Type and Parameters 14 == Parsing for Disposition Type and Parameters == 19 15 20 16 Using the simplified grammar below: … … 38 34 field. 39 35 40 5.3. Checking Cardinality Constraints 36 == Checking Cardinality Constraints == 41 37 42 38 If the parameter sequence contains multiple instances of the same 43 39 parameter name, ignore the whole header field. 44 40 45 5.4. Post-Process Parameter Values 41 TODO(abarth): We want to take the first. 42 43 == Post-Process Parameter Values == 46 44 47 45 For each parameter, post-process the associated value part according … … 60 58 HTTP message, and results in a sequence of Unicode characters. 61 59 62 5.5. Extracting the Disposition Type 60 == Extracting the Disposition Type == 63 61 64 62 The parsing step (Appendix 5.2) has returned the disposition type (to … … 67 65 "attachment" (see Section 3.2). 68 66 69 5.6. Determining the File Name 67 == Determining the File Name == 70 68 71 69 The parsing and post-processing steps resulted in a set of parameters … … 82 80 path separator character.]] 83 81 82 = Old text (to be integrated) = 84 83 85 84 == Extracting Parameter Values From Header Fields ==
