source: draft-ietf-httpbis/latest/auth48/rfc7231.abdiff.txt @ 2679

Last change on this file since 2679 was 2679, checked in by julian.reschke@…, 7 years ago

Apply Roy Fielding's feedback to P2 (#553)

  • Property svn:eol-style set to native
File size: 46.0 KB
Line 
1
2INTRODUCTION, paragraph 1:
3OLD:
4
5 HTTPbis Working Group                                   R. Fielding, Ed.
6 Internet-Draft                                                     Adobe
7 Obsoletes: 2616 (if approved)                            J. Reschke, Ed.
8 Updates: 2817 (if approved)                                   greenbytes
9 Intended status: Standards Track                            May 16, 2014
10 Expires: November 17, 2014
11
12NEW:
13
14 Internet Engineering Task Force (IETF)                  R. Fielding, Ed.
15 Request for Comments: 7231                                         Adobe
16 Obsoletes: 2616                                          J. Reschke, Ed.
17 Updates: 2817                                                 greenbytes
18 Category: Standards Track                                       May 2014
19 ISSN: 2070-1721
20
21
22INTRODUCTION, paragraph 2:
23OLD:
24
25      Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
26                  draft-ietf-httpbis-p2-semantics-latest
27
28NEW:
29
30      Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
31
32
33INTRODUCTION, paragraph 5:
34OLD:
35
36 Editorial Note (To be removed by RFC Editor)
37 
38    Discussion of this draft takes place on the HTTPBIS working group
39    mailing list (ietf-http-wg@w3.org), which is archived at
40    <http://lists.w3.org/Archives/Public/ietf-http-wg/>.
41 
42    The current issues list is at
43    <http://tools.ietf.org/wg/httpbis/trac/report/3> and related
44    documents (including fancy diffs) can be found at
45    <http://tools.ietf.org/wg/httpbis/>.
46 
47    _This is a temporary document for the purpose of tracking the
48    editorial changes made during the AUTH48 (RFC publication) phase._
49 
50 Status of This Memo
51
52NEW:
53
54 Status of This Memo
55
56
57INTRODUCTION, paragraph 6:
58OLD:
59
60    This Internet-Draft is submitted in full conformance with the
61    provisions of BCP 78 and BCP 79.
62 
63    Internet-Drafts are working documents of the Internet Engineering
64    Task Force (IETF).  Note that other groups may also distribute
65    working documents as Internet-Drafts.  The list of current Internet-
66    Drafts is at http://datatracker.ietf.org/drafts/current/.
67
68NEW:
69
70    This is an Internet Standards Track document.
71
72
73INTRODUCTION, paragraph 7:
74OLD:
75
76    Internet-Drafts are draft documents valid for a maximum of six months
77    and may be updated, replaced, or obsoleted by other documents at any
78    time.  It is inappropriate to use Internet-Drafts as reference
79    material or to cite them other than as "work in progress."
80
81NEW:
82
83    This document is a product of the Internet Engineering Task Force
84    (IETF).  It represents the consensus of the IETF community.  It has
85    received public review and has been approved for publication by the
86    Internet Engineering Steering Group (IESG).  Further information on
87    Internet Standards is available in Section 2 of RFC 5741.
88
89
90INTRODUCTION, paragraph 8:
91OLD:
92
93    This Internet-Draft will expire on November 17, 2014.
94
95NEW:
96
97    Information about the current status of this document, any errata,
98    and how to provide feedback on it may be obtained at
99    http://www.rfc-editor.org/info/rfc7231.
100
101
102Section 11., paragraph 0:
103OLD:
104
105    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  6
106      1.1.  Conformance and Error Handling . . . . . . . . . . . . . .  6
107      1.2.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  6
108    2.  Resources  . . . . . . . . . . . . . . . . . . . . . . . . . .  7
109    3.  Representations  . . . . . . . . . . . . . . . . . . . . . . .  7
110      3.1.  Representation Metadata  . . . . . . . . . . . . . . . . .  8
111        3.1.1.  Processing Representation Data . . . . . . . . . . . .  8
112        3.1.2.  Encoding for Compression or Integrity  . . . . . . . . 11
113        3.1.3.  Audience Language  . . . . . . . . . . . . . . . . . . 13
114        3.1.4.  Identification . . . . . . . . . . . . . . . . . . . . 14
115      3.2.  Representation Data  . . . . . . . . . . . . . . . . . . . 17
116      3.3.  Payload Semantics  . . . . . . . . . . . . . . . . . . . . 17
117      3.4.  Content Negotiation  . . . . . . . . . . . . . . . . . . . 18
118        3.4.1.  Proactive Negotiation  . . . . . . . . . . . . . . . . 19
119        3.4.2.  Reactive Negotiation . . . . . . . . . . . . . . . . . 20
120 
121    4.  Request Methods  . . . . . . . . . . . . . . . . . . . . . . . 21
122      4.1.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . 21
123      4.2.  Common Method Properties . . . . . . . . . . . . . . . . . 22
124        4.2.1.  Safe Methods . . . . . . . . . . . . . . . . . . . . . 22
125        4.2.2.  Idempotent Methods . . . . . . . . . . . . . . . . . . 23
126        4.2.3.  Cacheable Methods  . . . . . . . . . . . . . . . . . . 24
127      4.3.  Method Definitions . . . . . . . . . . . . . . . . . . . . 24
128        4.3.1.  GET  . . . . . . . . . . . . . . . . . . . . . . . . . 24
129        4.3.2.  HEAD . . . . . . . . . . . . . . . . . . . . . . . . . 25
130        4.3.3.  POST . . . . . . . . . . . . . . . . . . . . . . . . . 25
131        4.3.4.  PUT  . . . . . . . . . . . . . . . . . . . . . . . . . 26
132        4.3.5.  DELETE . . . . . . . . . . . . . . . . . . . . . . . . 29
133        4.3.6.  CONNECT  . . . . . . . . . . . . . . . . . . . . . . . 30
134        4.3.7.  OPTIONS  . . . . . . . . . . . . . . . . . . . . . . . 31
135        4.3.8.  TRACE  . . . . . . . . . . . . . . . . . . . . . . . . 32
136    5.  Request Header Fields  . . . . . . . . . . . . . . . . . . . . 33
137      5.1.  Controls . . . . . . . . . . . . . . . . . . . . . . . . . 33
138        5.1.1.  Expect . . . . . . . . . . . . . . . . . . . . . . . . 34
139        5.1.2.  Max-Forwards . . . . . . . . . . . . . . . . . . . . . 36
140      5.2.  Conditionals . . . . . . . . . . . . . . . . . . . . . . . 36
141      5.3.  Content Negotiation  . . . . . . . . . . . . . . . . . . . 37
142        5.3.1.  Quality Values . . . . . . . . . . . . . . . . . . . . 37
143        5.3.2.  Accept . . . . . . . . . . . . . . . . . . . . . . . . 38
144        5.3.3.  Accept-Charset . . . . . . . . . . . . . . . . . . . . 40
145        5.3.4.  Accept-Encoding  . . . . . . . . . . . . . . . . . . . 41
146        5.3.5.  Accept-Language  . . . . . . . . . . . . . . . . . . . 42
147      5.4.  Authentication Credentials . . . . . . . . . . . . . . . . 43
148      5.5.  Request Context  . . . . . . . . . . . . . . . . . . . . . 44
149        5.5.1.  From . . . . . . . . . . . . . . . . . . . . . . . . . 44
150        5.5.2.  Referer  . . . . . . . . . . . . . . . . . . . . . . . 45
151        5.5.3.  User-Agent . . . . . . . . . . . . . . . . . . . . . . 46
152    6.  Response Status Codes  . . . . . . . . . . . . . . . . . . . . 47
153      6.1.  Overview of Status Codes . . . . . . . . . . . . . . . . . 48
154      6.2.  Informational 1xx  . . . . . . . . . . . . . . . . . . . . 50
155        6.2.1.  100 Continue . . . . . . . . . . . . . . . . . . . . . 50
156        6.2.2.  101 Switching Protocols  . . . . . . . . . . . . . . . 50
157      6.3.  Successful 2xx . . . . . . . . . . . . . . . . . . . . . . 51
158        6.3.1.  200 OK . . . . . . . . . . . . . . . . . . . . . . . . 51
159        6.3.2.  201 Created  . . . . . . . . . . . . . . . . . . . . . 51
160        6.3.3.  202 Accepted . . . . . . . . . . . . . . . . . . . . . 52
161        6.3.4.  203 Non-Authoritative Information  . . . . . . . . . . 52
162        6.3.5.  204 No Content . . . . . . . . . . . . . . . . . . . . 53
163        6.3.6.  205 Reset Content  . . . . . . . . . . . . . . . . . . 53
164      6.4.  Redirection 3xx  . . . . . . . . . . . . . . . . . . . . . 54
165        6.4.1.  300 Multiple Choices . . . . . . . . . . . . . . . . . 55
166        6.4.2.  301 Moved Permanently  . . . . . . . . . . . . . . . . 56
167        6.4.3.  302 Found  . . . . . . . . . . . . . . . . . . . . . . 56
168        6.4.4.  303 See Other  . . . . . . . . . . . . . . . . . . . . 57
169        6.4.5.  305 Use Proxy  . . . . . . . . . . . . . . . . . . . . 57
170        6.4.6.  306 (Unused) . . . . . . . . . . . . . . . . . . . . . 57
171        6.4.7.  307 Temporary Redirect . . . . . . . . . . . . . . . . 58
172      6.5.  Client Error 4xx . . . . . . . . . . . . . . . . . . . . . 58
173        6.5.1.  400 Bad Request  . . . . . . . . . . . . . . . . . . . 58
174        6.5.2.  402 Payment Required . . . . . . . . . . . . . . . . . 58
175        6.5.3.  403 Forbidden  . . . . . . . . . . . . . . . . . . . . 58
176        6.5.4.  404 Not Found  . . . . . . . . . . . . . . . . . . . . 59
177        6.5.5.  405 Method Not Allowed . . . . . . . . . . . . . . . . 59
178        6.5.6.  406 Not Acceptable . . . . . . . . . . . . . . . . . . 59
179        6.5.7.  408 Request Timeout  . . . . . . . . . . . . . . . . . 60
180        6.5.8.  409 Conflict . . . . . . . . . . . . . . . . . . . . . 60
181        6.5.9.  410 Gone . . . . . . . . . . . . . . . . . . . . . . . 60
182        6.5.10. 411 Length Required  . . . . . . . . . . . . . . . . . 61
183        6.5.11. 413 Payload Too Large  . . . . . . . . . . . . . . . . 61
184        6.5.12. 414 URI Too Long . . . . . . . . . . . . . . . . . . . 61
185        6.5.13. 415 Unsupported Media Type . . . . . . . . . . . . . . 61
186        6.5.14. 417 Expectation Failed . . . . . . . . . . . . . . . . 62
187        6.5.15. 426 Upgrade Required . . . . . . . . . . . . . . . . . 62
188      6.6.  Server Error 5xx . . . . . . . . . . . . . . . . . . . . . 62
189        6.6.1.  500 Internal Server Error  . . . . . . . . . . . . . . 62
190        6.6.2.  501 Not Implemented  . . . . . . . . . . . . . . . . . 63
191        6.6.3.  502 Bad Gateway  . . . . . . . . . . . . . . . . . . . 63
192        6.6.4.  503 Service Unavailable  . . . . . . . . . . . . . . . 63
193        6.6.5.  504 Gateway Timeout  . . . . . . . . . . . . . . . . . 63
194        6.6.6.  505 HTTP Version Not Supported . . . . . . . . . . . . 63
195    7.  Response Header Fields . . . . . . . . . . . . . . . . . . . . 64
196      7.1.  Control Data . . . . . . . . . . . . . . . . . . . . . . . 64
197        7.1.1.  Origination Date . . . . . . . . . . . . . . . . . . . 64
198        7.1.2.  Location . . . . . . . . . . . . . . . . . . . . . . . 68
199        7.1.3.  Retry-After  . . . . . . . . . . . . . . . . . . . . . 69
200        7.1.4.  Vary . . . . . . . . . . . . . . . . . . . . . . . . . 70
201      7.2.  Validator Header Fields  . . . . . . . . . . . . . . . . . 71
202      7.3.  Authentication Challenges  . . . . . . . . . . . . . . . . 72
203      7.4.  Response Context . . . . . . . . . . . . . . . . . . . . . 72
204        7.4.1.  Allow  . . . . . . . . . . . . . . . . . . . . . . . . 72
205        7.4.2.  Server . . . . . . . . . . . . . . . . . . . . . . . . 73
206    8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 73
207      8.1.  Method Registry  . . . . . . . . . . . . . . . . . . . . . 74
208        8.1.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 74
209        8.1.2.  Considerations for New Methods . . . . . . . . . . . . 74
210        8.1.3.  Registrations  . . . . . . . . . . . . . . . . . . . . 75
211      8.2.  Status Code Registry . . . . . . . . . . . . . . . . . . . 75
212        8.2.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 75
213        8.2.2.  Considerations for New Status Codes  . . . . . . . . . 76
214        8.2.3.  Registrations  . . . . . . . . . . . . . . . . . . . . 76
215      8.3.  Header Field Registry  . . . . . . . . . . . . . . . . . . 77
216        8.3.1.  Considerations for New Header Fields . . . . . . . . . 78
217        8.3.2.  Registrations  . . . . . . . . . . . . . . . . . . . . 80
218      8.4.  Content Coding Registry  . . . . . . . . . . . . . . . . . 80
219        8.4.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 81
220        8.4.2.  Registrations  . . . . . . . . . . . . . . . . . . . . 81
221    9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 81
222      9.1.  Attacks Based on File and Path Names . . . . . . . . . . . 82
223      9.2.  Attacks Based on Command, Code, or Query Injection . . . . 82
224      9.3.  Disclosure of Personal Information . . . . . . . . . . . . 83
225      9.4.  Disclosure of Sensitive Information in URIs  . . . . . . . 83
226      9.5.  Disclosure of Fragment after Redirects . . . . . . . . . . 83
227      9.6.  Disclosure of Product Information  . . . . . . . . . . . . 84
228      9.7.  Browser Fingerprinting . . . . . . . . . . . . . . . . . . 84
229    10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 85
230    11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 85
231      11.1. Normative References . . . . . . . . . . . . . . . . . . . 85
232      11.2. Informative References . . . . . . . . . . . . . . . . . . 86
233    Appendix A.  Differences between HTTP and MIME . . . . . . . . . . 88
234      A.1.  MIME-Version . . . . . . . . . . . . . . . . . . . . . . . 89
235      A.2.  Conversion to Canonical Form . . . . . . . . . . . . . . . 89
236      A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 89
237      A.4.  Conversion of Content-Encoding . . . . . . . . . . . . . . 89
238      A.5.  Conversion of Content-Transfer-Encoding  . . . . . . . . . 90
239      A.6.  MHTML and Line Length Limitations  . . . . . . . . . . . . 90
240    Appendix B.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 90
241    Appendix C.  Imported ABNF . . . . . . . . . . . . . . . . . . . . 93
242    Appendix D.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 93
243    Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
244
245NEW:
246
247    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  6
248      1.1.  Conformance and Error Handling . . . . . . . . . . . . . .  6
249      1.2.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  6
250    2.  Resources  . . . . . . . . . . . . . . . . . . . . . . . . . .  7
251    3.  Representations  . . . . . . . . . . . . . . . . . . . . . . .  7
252      3.1.  Representation Metadata  . . . . . . . . . . . . . . . . .  8
253        3.1.1.  Processing Representation Data . . . . . . . . . . . .  8
254        3.1.2.  Encoding for Compression or Integrity  . . . . . . . . 11
255        3.1.3.  Audience Language  . . . . . . . . . . . . . . . . . . 13
256        3.1.4.  Identification . . . . . . . . . . . . . . . . . . . . 14
257      3.2.  Representation Data  . . . . . . . . . . . . . . . . . . . 17
258      3.3.  Payload Semantics  . . . . . . . . . . . . . . . . . . . . 17
259      3.4.  Content Negotiation  . . . . . . . . . . . . . . . . . . . 18
260        3.4.1.  Proactive Negotiation  . . . . . . . . . . . . . . . . 19
261        3.4.2.  Reactive Negotiation . . . . . . . . . . . . . . . . . 20
262    4.  Request Methods  . . . . . . . . . . . . . . . . . . . . . . . 21
263      4.1.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . 21
264      4.2.  Common Method Properties . . . . . . . . . . . . . . . . . 22
265        4.2.1.  Safe Methods . . . . . . . . . . . . . . . . . . . . . 22
266        4.2.2.  Idempotent Methods . . . . . . . . . . . . . . . . . . 23
267        4.2.3.  Cacheable Methods  . . . . . . . . . . . . . . . . . . 24
268      4.3.  Method Definitions . . . . . . . . . . . . . . . . . . . . 24
269        4.3.1.  GET  . . . . . . . . . . . . . . . . . . . . . . . . . 24
270        4.3.2.  HEAD . . . . . . . . . . . . . . . . . . . . . . . . . 25
271        4.3.3.  POST . . . . . . . . . . . . . . . . . . . . . . . . . 25
272        4.3.4.  PUT  . . . . . . . . . . . . . . . . . . . . . . . . . 26
273        4.3.5.  DELETE . . . . . . . . . . . . . . . . . . . . . . . . 29
274        4.3.6.  CONNECT  . . . . . . . . . . . . . . . . . . . . . . . 30
275        4.3.7.  OPTIONS  . . . . . . . . . . . . . . . . . . . . . . . 31
276        4.3.8.  TRACE  . . . . . . . . . . . . . . . . . . . . . . . . 32
277    5.  Request Header Fields  . . . . . . . . . . . . . . . . . . . . 33
278      5.1.  Controls . . . . . . . . . . . . . . . . . . . . . . . . . 33
279        5.1.1.  Expect . . . . . . . . . . . . . . . . . . . . . . . . 34
280        5.1.2.  Max-Forwards . . . . . . . . . . . . . . . . . . . . . 36
281 
282      5.2.  Conditionals . . . . . . . . . . . . . . . . . . . . . . . 36
283      5.3.  Content Negotiation  . . . . . . . . . . . . . . . . . . . 37
284        5.3.1.  Quality Values . . . . . . . . . . . . . . . . . . . . 37
285        5.3.2.  Accept . . . . . . . . . . . . . . . . . . . . . . . . 38
286        5.3.3.  Accept-Charset . . . . . . . . . . . . . . . . . . . . 40
287        5.3.4.  Accept-Encoding  . . . . . . . . . . . . . . . . . . . 41
288        5.3.5.  Accept-Language  . . . . . . . . . . . . . . . . . . . 42
289      5.4.  Authentication Credentials . . . . . . . . . . . . . . . . 43
290      5.5.  Request Context  . . . . . . . . . . . . . . . . . . . . . 44
291        5.5.1.  From . . . . . . . . . . . . . . . . . . . . . . . . . 44
292        5.5.2.  Referer  . . . . . . . . . . . . . . . . . . . . . . . 45
293        5.5.3.  User-Agent . . . . . . . . . . . . . . . . . . . . . . 46
294    6.  Response Status Codes  . . . . . . . . . . . . . . . . . . . . 47
295      6.1.  Overview of Status Codes . . . . . . . . . . . . . . . . . 48
296      6.2.  Informational 1xx  . . . . . . . . . . . . . . . . . . . . 50
297        6.2.1.  100 Continue . . . . . . . . . . . . . . . . . . . . . 50
298        6.2.2.  101 Switching Protocols  . . . . . . . . . . . . . . . 50
299      6.3.  Successful 2xx . . . . . . . . . . . . . . . . . . . . . . 51
300        6.3.1.  200 OK . . . . . . . . . . . . . . . . . . . . . . . . 51
301        6.3.2.  201 Created  . . . . . . . . . . . . . . . . . . . . . 52
302        6.3.3.  202 Accepted . . . . . . . . . . . . . . . . . . . . . 52
303        6.3.4.  203 Non-Authoritative Information  . . . . . . . . . . 52
304        6.3.5.  204 No Content . . . . . . . . . . . . . . . . . . . . 53
305        6.3.6.  205 Reset Content  . . . . . . . . . . . . . . . . . . 53
306      6.4.  Redirection 3xx  . . . . . . . . . . . . . . . . . . . . . 54
307        6.4.1.  300 Multiple Choices . . . . . . . . . . . . . . . . . 55
308        6.4.2.  301 Moved Permanently  . . . . . . . . . . . . . . . . 56
309        6.4.3.  302 Found  . . . . . . . . . . . . . . . . . . . . . . 56
310        6.4.4.  303 See Other  . . . . . . . . . . . . . . . . . . . . 57
311        6.4.5.  305 Use Proxy  . . . . . . . . . . . . . . . . . . . . 57
312        6.4.6.  306 (Unused) . . . . . . . . . . . . . . . . . . . . . 57
313        6.4.7.  307 Temporary Redirect . . . . . . . . . . . . . . . . 58
314      6.5.  Client Error 4xx . . . . . . . . . . . . . . . . . . . . . 58
315        6.5.1.  400 Bad Request  . . . . . . . . . . . . . . . . . . . 58
316        6.5.2.  402 Payment Required . . . . . . . . . . . . . . . . . 58
317        6.5.3.  403 Forbidden  . . . . . . . . . . . . . . . . . . . . 58
318        6.5.4.  404 Not Found  . . . . . . . . . . . . . . . . . . . . 59
319        6.5.5.  405 Method Not Allowed . . . . . . . . . . . . . . . . 59
320        6.5.6.  406 Not Acceptable . . . . . . . . . . . . . . . . . . 59
321        6.5.7.  408 Request Timeout  . . . . . . . . . . . . . . . . . 60
322        6.5.8.  409 Conflict . . . . . . . . . . . . . . . . . . . . . 60
323        6.5.9.  410 Gone . . . . . . . . . . . . . . . . . . . . . . . 60
324        6.5.10. 411 Length Required  . . . . . . . . . . . . . . . . . 61
325        6.5.11. 413 Payload Too Large  . . . . . . . . . . . . . . . . 61
326        6.5.12. 414 URI Too Long . . . . . . . . . . . . . . . . . . . 61
327        6.5.13. 415 Unsupported Media Type . . . . . . . . . . . . . . 61
328        6.5.14. 417 Expectation Failed . . . . . . . . . . . . . . . . 62
329        6.5.15. 426 Upgrade Required . . . . . . . . . . . . . . . . . 62
330 
331      6.6.  Server Error 5xx . . . . . . . . . . . . . . . . . . . . . 62
332        6.6.1.  500 Internal Server Error  . . . . . . . . . . . . . . 62
333        6.6.2.  501 Not Implemented  . . . . . . . . . . . . . . . . . 63
334        6.6.3.  502 Bad Gateway  . . . . . . . . . . . . . . . . . . . 63
335        6.6.4.  503 Service Unavailable  . . . . . . . . . . . . . . . 63
336        6.6.5.  504 Gateway Timeout  . . . . . . . . . . . . . . . . . 63
337        6.6.6.  505 HTTP Version Not Supported . . . . . . . . . . . . 63
338    7.  Response Header Fields . . . . . . . . . . . . . . . . . . . . 64
339      7.1.  Control Data . . . . . . . . . . . . . . . . . . . . . . . 64
340        7.1.1.  Origination Date . . . . . . . . . . . . . . . . . . . 64
341        7.1.2.  Location . . . . . . . . . . . . . . . . . . . . . . . 68
342        7.1.3.  Retry-After  . . . . . . . . . . . . . . . . . . . . . 69
343        7.1.4.  Vary . . . . . . . . . . . . . . . . . . . . . . . . . 70
344      7.2.  Validator Header Fields  . . . . . . . . . . . . . . . . . 71
345      7.3.  Authentication Challenges  . . . . . . . . . . . . . . . . 72
346      7.4.  Response Context . . . . . . . . . . . . . . . . . . . . . 72
347        7.4.1.  Allow  . . . . . . . . . . . . . . . . . . . . . . . . 72
348        7.4.2.  Server . . . . . . . . . . . . . . . . . . . . . . . . 73
349    8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 73
350      8.1.  Method Registry  . . . . . . . . . . . . . . . . . . . . . 74
351        8.1.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 74
352        8.1.2.  Considerations for New Methods . . . . . . . . . . . . 74
353        8.1.3.  Registrations  . . . . . . . . . . . . . . . . . . . . 75
354      8.2.  Status Code Registry . . . . . . . . . . . . . . . . . . . 75
355        8.2.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 75
356        8.2.2.  Considerations for New Status Codes  . . . . . . . . . 76
357        8.2.3.  Registrations  . . . . . . . . . . . . . . . . . . . . 76
358      8.3.  Header Field Registry  . . . . . . . . . . . . . . . . . . 77
359        8.3.1.  Considerations for New Header Fields . . . . . . . . . 78
360        8.3.2.  Registrations  . . . . . . . . . . . . . . . . . . . . 80
361      8.4.  Content Coding Registry  . . . . . . . . . . . . . . . . . 80
362        8.4.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 81
363        8.4.2.  Registrations  . . . . . . . . . . . . . . . . . . . . 81
364    9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 81
365      9.1.  Attacks Based on File and Path Names . . . . . . . . . . . 82
366      9.2.  Attacks Based on Command, Code, or Query Injection . . . . 82
367      9.3.  Disclosure of Personal Information . . . . . . . . . . . . 83
368      9.4.  Disclosure of Sensitive Information in URIs  . . . . . . . 83
369      9.5.  Disclosure of Fragment after Redirects . . . . . . . . . . 83
370      9.6.  Disclosure of Product Information  . . . . . . . . . . . . 84
371      9.7.  Browser Fingerprinting . . . . . . . . . . . . . . . . . . 84
372    10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 85
373    11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 85
374      11.1. Normative References . . . . . . . . . . . . . . . . . . . 85
375      11.2. Informative References . . . . . . . . . . . . . . . . . . 86
376    Appendix A.  Differences between HTTP and MIME . . . . . . . . . . 88
377      A.1.  MIME-Version . . . . . . . . . . . . . . . . . . . . . . . 88
378      A.2.  Conversion to Canonical Form . . . . . . . . . . . . . . . 89
379      A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 89
380      A.4.  Conversion of Content-Encoding . . . . . . . . . . . . . . 89
381      A.5.  Conversion of Content-Transfer-Encoding  . . . . . . . . . 90
382      A.6.  MHTML and Line Length Limitations  . . . . . . . . . . . . 90
383    Appendix B.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 90
384    Appendix C.  Imported ABNF . . . . . . . . . . . . . . . . . . . . 93
385    Appendix D.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 93
386    Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
387
388
389Section 5.3.5., paragraph 2:
390OLD:
391
392      Accept-Language = 1#( language-range [ weight ] )
393      language-range  =
394                <language-range, see [RFC4647], Section 2.1>
395
396NEW:
397
398      Accept-Language = 1#( language-range [ weight ] )
399      language-range  =
400                <language-range, defined in [RFC4647], Section 2.1>
401
402
403Section 5.5.1., paragraph 3:
404OLD:
405
406      mailbox = <mailbox, see [RFC5322], Section 3.4>
407
408NEW:
409
410      mailbox = <mailbox, defined in [RFC5322], Section 3.4>
411
412
413Section 5.5.3., paragraph 5:
414OLD:
415
416    A sender SHOULD limit generated product identifiers to what is
417    necessary to identify the product; a sender MUST NOT generate
418    advertising or other nonessential information within the product
419    identifier.  A sender SHOULD NOT generate information in product-
420    version that is not a version identifier (i.e., successive versions
421    of the same product name only to differ only in the product-version
422    portion of the product identifier).
423
424NEW:
425
426    A sender SHOULD limit generated product identifiers to what is
427    necessary to identify the product; a sender MUST NOT generate
428    advertising or other nonessential information within the product
429    identifier.  A sender SHOULD NOT generate information in product-
430    version that is not a version identifier (i.e., successive versions
431    of the same product name ought only to differ in the product-version
432    portion of the product identifier).
433
434
435Section 6.1., paragraph 3:
436OLD:
437
438    +------+-------------------------------+--------------------------+
439    | Code | Reason-Phrase                 | Defined in...            |
440    +------+-------------------------------+--------------------------+
441    | 100  | Continue                      | Section 6.2.1            |
442    | 101  | Switching Protocols           | Section 6.2.2            |
443    | 200  | OK                            | Section 6.3.1            |
444    | 201  | Created                       | Section 6.3.2            |
445    | 202  | Accepted                      | Section 6.3.3            |
446    | 203  | Non-Authoritative Information | Section 6.3.4            |
447    | 204  | No Content                    | Section 6.3.5            |
448    | 205  | Reset Content                 | Section 6.3.6            |
449    | 206  | Partial Content               | Section 4.1 of [RFC7233] |
450    | 300  | Multiple Choices              | Section 6.4.1            |
451    | 301  | Moved Permanently             | Section 6.4.2            |
452    | 302  | Found                         | Section 6.4.3            |
453    | 303  | See Other                     | Section 6.4.4            |
454    | 304  | Not Modified                  | Section 4.1 of [RFC7232] |
455    | 305  | Use Proxy                     | Section 6.4.5            |
456    | 307  | Temporary Redirect            | Section 6.4.7            |
457    | 400  | Bad Request                   | Section 6.5.1            |
458    | 401  | Unauthorized                  | Section 3.1 of [RFC7235] |
459    | 402  | Payment Required              | Section 6.5.2            |
460    | 403  | Forbidden                     | Section 6.5.3            |
461    | 404  | Not Found                     | Section 6.5.4            |
462    | 405  | Method Not Allowed            | Section 6.5.5            |
463    | 406  | Not Acceptable                | Section 6.5.6            |
464    | 407  | Proxy Authentication Required | Section 3.2 of [RFC7235] |
465    | 408  | Request Time-out              | Section 6.5.7            |
466    | 409  | Conflict                      | Section 6.5.8            |
467    | 410  | Gone                          | Section 6.5.9            |
468    | 411  | Length Required               | Section 6.5.10           |
469    | 412  | Precondition Failed           | Section 4.2 of [RFC7232] |
470    | 413  | Payload Too Large             | Section 6.5.11           |
471    | 414  | URI Too Long                  | Section 6.5.12           |
472    | 415  | Unsupported Media Type        | Section 6.5.13           |
473    | 416  | Range Not Satisfiable         | Section 4.4 of [RFC7233] |
474    | 417  | Expectation Failed            | Section 6.5.14           |
475    | 426  | Upgrade Required              | Section 6.5.15           |
476    | 500  | Internal Server Error         | Section 6.6.1            |
477    | 501  | Not Implemented               | Section 6.6.2            |
478    | 502  | Bad Gateway                   | Section 6.6.3            |
479    | 503  | Service Unavailable           | Section 6.6.4            |
480    | 504  | Gateway Time-out              | Section 6.6.5            |
481    | 505  | HTTP Version Not Supported    | Section 6.6.6            |
482    +------+-------------------------------+--------------------------+
483
484NEW:
485
486    +------+-------------------------------+--------------------------+
487    | Code | Reason-Phrase                 | Defined in...            |
488    +------+-------------------------------+--------------------------+
489    | 100  | Continue                      | Section 6.2.1            |
490    | 101  | Switching Protocols           | Section 6.2.2            |
491    | 200  | OK                            | Section 6.3.1            |
492    | 201  | Created                       | Section 6.3.2            |
493    | 202  | Accepted                      | Section 6.3.3            |
494    | 203  | Non-Authoritative Information | Section 6.3.4            |
495    | 204  | No Content                    | Section 6.3.5            |
496    | 205  | Reset Content                 | Section 6.3.6            |
497    | 206  | Partial Content               | Section 4.1 of [RFC7233] |
498    | 300  | Multiple Choices              | Section 6.4.1            |
499    | 301  | Moved Permanently             | Section 6.4.2            |
500    | 302  | Found                         | Section 6.4.3            |
501    | 303  | See Other                     | Section 6.4.4            |
502    | 304  | Not Modified                  | Section 4.1 of [RFC7232] |
503    | 305  | Use Proxy                     | Section 6.4.5            |
504    | 307  | Temporary Redirect            | Section 6.4.7            |
505    | 400  | Bad Request                   | Section 6.5.1            |
506    | 401  | Unauthorized                  | Section 3.1 of [RFC7235] |
507    | 402  | Payment Required              | Section 6.5.2            |
508    | 403  | Forbidden                     | Section 6.5.3            |
509    | 404  | Not Found                     | Section 6.5.4            |
510    | 405  | Method Not Allowed            | Section 6.5.5            |
511    | 406  | Not Acceptable                | Section 6.5.6            |
512    | 407  | Proxy Authentication Required | Section 3.2 of [RFC7235] |
513    | 408  | Request Timeout               | Section 6.5.7            |
514    | 409  | Conflict                      | Section 6.5.8            |
515    | 410  | Gone                          | Section 6.5.9            |
516    | 411  | Length Required               | Section 6.5.10           |
517    | 412  | Precondition Failed           | Section 4.2 of [RFC7232] |
518    | 413  | Payload Too Large             | Section 6.5.11           |
519    | 414  | URI Too Long                  | Section 6.5.12           |
520    | 415  | Unsupported Media Type        | Section 6.5.13           |
521    | 416  | Range Not Satisfiable         | Section 4.4 of [RFC7233] |
522    | 417  | Expectation Failed            | Section 6.5.14           |
523    | 426  | Upgrade Required              | Section 6.5.15           |
524    | 500  | Internal Server Error         | Section 6.6.1            |
525    | 501  | Not Implemented               | Section 6.6.2            |
526    | 502  | Bad Gateway                   | Section 6.6.3            |
527    | 503  | Service Unavailable           | Section 6.6.4            |
528    | 504  | Gateway Timeout               | Section 6.6.5            |
529    | 505  | HTTP Version Not Supported    | Section 6.6.6            |
530    +------+-------------------------------+--------------------------+
531
532
533Section 6.2., paragraph 1:
534OLD:
535
536    The 1xx (Informational) class of status code indicates an interim
537    response for communicating connection status or request progress
538    prior to completing the requested action and sending a final
539    response. 1xx responses are terminated by the first empty line after
540    the status-line (the empty line signaling the end of the header
541    section).  Since HTTP/1.0 did not define any 1xx status codes, a
542    server MUST NOT send a 1xx response to an HTTP/1.0 client.
543
544NEW:
545
546    The 1xx (Informational) class of status code indicates an interim
547    response for communicating connection status or request progress
548    prior to completing the requested action and sending a final
549    response.  All 1xx responses consist of only the status-line and
550    optional header fields and, thus, are terminated by the empty line at
551    the end of the header section.  Since HTTP/1.0 did not define any 1xx
552    status codes, a server MUST NOT send a 1xx response to an HTTP/1.0
553    client.
554
555
556Section 7.1.1.1., paragraph 10:
557OLD:
558
559      IMF-fixdate  = day-name "," SP date1 SP time-of-day SP GMT
560      ; fixed length/zone/capitalization subset of the format
561      ; see Section 3.3 of [RFC5322]
562
563NEW:
564
565      IMF-fixdate  = day-name "," SP date1 SP time-of-day SP GMT
566      ; fixed length/zone/capitalization subset of the format
567      ; defined in Section 3.3 of [RFC5322]
568
569
570Section 9.1., paragraph 1:
571OLD:
572
573    Origin servers frequently make use of their local file system to
574    manage the mapping from effective request URI to resource
575    representations.  Most file systems are not designed to protect
576    against malicious file or path names.  Therefore, an origin server
577    needs to avoid accessing names that have a special significance to
578    the system when mapping the request target to files, folders, or
579    directories.
580
581NEW:
582
583    Origin servers frequently make use of their local file system to
584    manage the mapping from effective request URI to resource
585    representations.  Implementers need to be aware that most file
586    systems are not designed to protect against malicious file or path
587    names and, thus, depend on the origin server to avoid mapping to file
588    names, folders, or directories that have special significance to the
589    system.
590
591
592Section 11.1., paragraph 9:
593OLD:
594
595    [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
596               Protocol (HTTP/1.1): Message Syntax and Routing",
597               draft-ietf-httpbis-p1-messaging-latest (work in progress),
598               May 2014.
599
600NEW:
601
602    [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
603               Protocol (HTTP/1.1): Message Syntax and Routing",
604               RFC 7230, May 2014.
605
606
607Section 11.1., paragraph 10:
608OLD:
609
610    [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
611               Protocol (HTTP/1.1): Conditional Requests",
612               draft-ietf-httpbis-p4-conditional-latest (work in
613               progress), May 2014.
614
615NEW:
616
617    [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
618               Protocol (HTTP/1.1): Conditional Requests", RFC 7232,
619               May 2014.
620
621
622Section 11.1., paragraph 11:
623OLD:
624
625    [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
626               "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",
627               draft-ietf-httpbis-p5-range-latest (work in progress),
628               May 2014.
629
630NEW:
631
632    [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
633               "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",
634               RFC 7233, May 2014.
635
636
637Section 11.1., paragraph 12:
638OLD:
639
640    [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
641               Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
642               draft-ietf-httpbis-p6-cache-latest (work in progress),
643               May 2014.
644
645NEW:
646
647    [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
648               Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
649               RFC 7234, May 2014.
650
651
652Section 11.1., paragraph 13:
653OLD:
654
655    [RFC7235]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
656               Protocol (HTTP/1.1): Authentication",
657               draft-ietf-httpbis-p7-auth-latest (work in progress),
658               May 2014.
659
660NEW:
661
662    [RFC7235]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
663               Protocol (HTTP/1.1): Authentication", RFC 7235, May 2014.
664
665
666Section 11.2., paragraph 25:
667OLD:
668
669    [RFC7238]  Reschke, J., "The Hypertext Transfer Protocol (HTTP)
670               Status Code 308 (Permanent Redirect)",
671               draft-reschke-http-status-308-07 (work in progress),
672               March 2012.
673
674NEW:
675
676    [RFC7238]  Reschke, J., "The Hypertext Transfer Protocol (HTTP)
677               Status Code 308 (Permanent Redirect)", RFC 7238, May 2014.
678
679
680Appendix B., paragraph 2:
681OLD:
682
683    A new requirement has been added that semantics embedded in a URI be
684    disabled when those semantics are inconsistent with the request
685    method, since this is a common cause of interoperability failure.
686 
687    (Section 2)
688
689NEW:
690
691    A new requirement has been added that semantics embedded in a URI be
692    disabled when those semantics are inconsistent with the request
693    method, since this is a common cause of interoperability failure.
694    (Section 2)
695
696
697Appendix B., paragraph 26:
698OLD:
699
700    The Status Code Registry has been redefined by this specification;
701    previously, it was defined in Section 7.1 of [RFC2817].
702 
703    (Section 8.2)
704
705NEW:
706
707    The Status Code Registry has been redefined by this specification;
708    previously, it was defined in Section 7.1 of [RFC2817].
709    (Section 8.2)
710
711
712Appendix C., paragraph 3:
713OLD:
714
715      BWS           = <BWS, see [RFC7230], Section 3.2.3>
716      OWS           = <OWS, see [RFC7230], Section 3.2.3>
717      RWS           = <RWS, see [RFC7230], Section 3.2.3>
718      URI-reference = <URI-reference, see [RFC7230], Section 2.7>
719      absolute-URI  = <absolute-URI, see [RFC7230], Section 2.7>
720      comment       = <comment, see [RFC7230], Section 3.2.6>
721      field-name    = <comment, see [RFC7230], Section 3.2>
722      partial-URI   = <partial-URI, see [RFC7230], Section 2.7>
723      quoted-string = <quoted-string, see [RFC7230], Section 3.2.6>
724      token         = <token, see [RFC7230], Section 3.2.6>
725
726NEW:
727
728     BWS           = <BWS, defined in [RFC7230], Section 3.2.3>
729     OWS           = <OWS, defined in [RFC7230], Section 3.2.3>
730     RWS           = <RWS, defined in [RFC7230], Section 3.2.3>
731     URI-reference = <URI-reference, defined in [RFC7230], Section 2.7>
732     absolute-URI  = <absolute-URI, defined in [RFC7230], Section 2.7>
733     comment       = <comment, defined in [RFC7230], Section 3.2.6>
734     field-name    = <comment, defined in [RFC7230], Section 3.2>
735     partial-URI   = <partial-URI, defined in [RFC7230], Section 2.7>
736     quoted-string = <quoted-string, defined in [RFC7230], Section 3.2.6>
737     token         = <token, defined in [RFC7230], Section 3.2.6>
738
739
740Section 1.2, paragraph 1:
741OLD:
742
743    Accept = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
744     OWS ( media-range [ accept-params ] ) ] ) ]
745    Accept-Charset = *( "," OWS ) ( ( charset / "*" ) [ weight ] ) *( OWS
746     "," [ OWS ( ( charset / "*" ) [ weight ] ) ] )
747    Accept-Encoding = [ ( "," / ( codings [ weight ] ) ) *( OWS "," [ OWS
748     ( codings [ weight ] ) ] ) ]
749    Accept-Language = *( "," OWS ) ( language-range [ weight ] ) *( OWS
750     "," [ OWS ( language-range [ weight ] ) ] )
751    Allow = [ ( "," / method ) *( OWS "," [ OWS method ] ) ]
752    BWS = <BWS, see [RFC7230], Section 3.2.3>
753
754NEW:
755
756    Accept = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
757     OWS ( media-range [ accept-params ] ) ] ) ]
758    Accept-Charset = *( "," OWS ) ( ( charset / "*" ) [ weight ] ) *( OWS
759     "," [ OWS ( ( charset / "*" ) [ weight ] ) ] )
760    Accept-Encoding = [ ( "," / ( codings [ weight ] ) ) *( OWS "," [ OWS
761     ( codings [ weight ] ) ] ) ]
762    Accept-Language = *( "," OWS ) ( language-range [ weight ] ) *( OWS
763     "," [ OWS ( language-range [ weight ] ) ] )
764    Allow = [ ( "," / method ) *( OWS "," [ OWS method ] ) ]
765 
766    BWS = <BWS, defined in [RFC7230], Section 3.2.3>
767
768
769Section 1.2, paragraph 2:
770OLD:
771
772    Content-Encoding = *( "," OWS ) content-coding *( OWS "," [ OWS
773     content-coding ] )
774    Content-Language = *( "," OWS ) language-tag *( OWS "," [ OWS
775     language-tag ] )
776    Content-Location = absolute-URI / partial-URI
777    Content-Type = media-type
778 
779    Date = HTTP-date
780
781NEW:
782
783    Content-Encoding = *( "," OWS ) content-coding *( OWS "," [ OWS
784     content-coding ] )
785    Content-Language = *( "," OWS ) language-tag *( OWS "," [ OWS
786     language-tag ] )
787    Content-Location = absolute-URI / partial-URI
788    Content-Type = media-type
789    Date = HTTP-date
790
791
792Section 1.2, paragraph 10:
793OLD:
794
795    OWS = <OWS, see [RFC7230], Section 3.2.3>
796
797NEW:
798
799    OWS = <OWS, defined in [RFC7230], Section 3.2.3>
800
801
802Section 1.2, paragraph 11:
803OLD:
804
805    RWS = <RWS, see [RFC7230], Section 3.2.3>
806    Referer = absolute-URI / partial-URI
807    Retry-After = HTTP-date / delay-seconds
808
809NEW:
810
811    RWS = <RWS, defined in [RFC7230], Section 3.2.3>
812    Referer = absolute-URI / partial-URI
813    Retry-After = HTTP-date / delay-seconds
814
815
816Section 1.2, paragraph 13:
817OLD:
818
819    URI-reference = <URI-reference, see [RFC7230], Section 2.7>
820    User-Agent = product *( RWS ( product / comment ) )
821
822NEW:
823
824    URI-reference = <URI-reference, defined in [RFC7230], Section 2.7>
825    User-Agent = product *( RWS ( product / comment ) )
826
827
828Section 1.2, paragraph 15:
829OLD:
830
831    absolute-URI = <absolute-URI, see [RFC7230], Section 2.7>
832    accept-ext = OWS ";" OWS token [ "=" ( token / quoted-string ) ]
833    accept-params = weight *accept-ext
834    asctime-date = day-name SP date3 SP time-of-day SP year
835
836NEW:
837
838    absolute-URI = <absolute-URI, defined in [RFC7230], Section 2.7>
839    accept-ext = OWS ";" OWS token [ "=" ( token / quoted-string ) ]
840    accept-params = weight *accept-ext
841    asctime-date = day-name SP date3 SP time-of-day SP year
842
843
844Section 1.2, paragraph 16:
845OLD:
846
847    charset = token
848    codings = content-coding / "identity" / "*"
849    comment = <comment, see [RFC7230], Section 3.2.6>
850    content-coding = token
851    date1 = day SP month SP year
852    date2 = day "-" month "-" 2DIGIT
853    date3 = month SP ( 2DIGIT / ( SP DIGIT ) )
854    day = 2DIGIT
855    day-name = %x4D.6F.6E ; Mon
856     / %x54.75.65 ; Tue
857     / %x57.65.64 ; Wed
858     / %x54.68.75 ; Thu
859     / %x46.72.69 ; Fri
860     / %x53.61.74 ; Sat
861     / %x53.75.6E ; Sun
862    day-name-l = %x4D.6F.6E.64.61.79 ; Monday
863     / %x54.75.65.73.64.61.79 ; Tuesday
864     / %x57.65.64.6E.65.73.64.61.79 ; Wednesday
865     / %x54.68.75.72.73.64.61.79 ; Thursday
866     / %x46.72.69.64.61.79 ; Friday
867     / %x53.61.74.75.72.64.61.79 ; Saturday
868     / %x53.75.6E.64.61.79 ; Sunday
869    delay-seconds = 1*DIGIT
870
871NEW:
872
873    charset = token
874    codings = content-coding / "identity" / "*"
875    comment = <comment, defined in [RFC7230], Section 3.2.6>
876    content-coding = token
877 
878    date1 = day SP month SP year
879    date2 = day "-" month "-" 2DIGIT
880    date3 = month SP ( 2DIGIT / ( SP DIGIT ) )
881    day = 2DIGIT
882    day-name = %x4D.6F.6E ; Mon
883     / %x54.75.65 ; Tue
884     / %x57.65.64 ; Wed
885     / %x54.68.75 ; Thu
886     / %x46.72.69 ; Fri
887     / %x53.61.74 ; Sat
888     / %x53.75.6E ; Sun
889    day-name-l = %x4D.6F.6E.64.61.79 ; Monday
890     / %x54.75.65.73.64.61.79 ; Tuesday
891     / %x57.65.64.6E.65.73.64.61.79 ; Wednesday
892     / %x54.68.75.72.73.64.61.79 ; Thursday
893     / %x46.72.69.64.61.79 ; Friday
894     / %x53.61.74.75.72.64.61.79 ; Saturday
895     / %x53.75.6E.64.61.79 ; Sunday
896    delay-seconds = 1*DIGIT
897
898
899Section 1.2, paragraph 17:
900OLD:
901
902    field-name = <comment, see [RFC7230], Section 3.2>
903
904NEW:
905
906    field-name = <comment, defined in [RFC7230], Section 3.2>
907
908
909Section 1.2, paragraph 19:
910OLD:
911
912    language-range = <language-range, see [RFC4647], Section 2.1>
913    language-tag = <Language-Tag, defined in [RFC5646], Section 2.1>
914
915NEW:
916
917    language-range = <language-range, defined in [RFC4647], Section 2.1>
918    language-tag = <Language-Tag, defined in [RFC5646], Section 2.1>
919
920
921Section 1.2, paragraph 20:
922OLD:
923
924    mailbox = <mailbox, see [RFC5322], Section 3.4>
925    media-range = ( "*/*" / ( type "/*" ) / ( type "/" subtype ) ) *( OWS
926     ";" OWS parameter )
927    media-type = type "/" subtype *( OWS ";" OWS parameter )
928    method = token
929    minute = 2DIGIT
930    month = %x4A.61.6E ; Jan
931     / %x46.65.62 ; Feb
932     / %x4D.61.72 ; Mar
933     / %x41.70.72 ; Apr
934     / %x4D.61.79 ; May
935     / %x4A.75.6E ; Jun
936     / %x4A.75.6C ; Jul
937     / %x41.75.67 ; Aug
938     / %x53.65.70 ; Sep
939     / %x4F.63.74 ; Oct
940     / %x4E.6F.76 ; Nov
941     / %x44.65.63 ; Dec
942
943NEW:
944
945    mailbox = <mailbox, defined in [RFC5322], Section 3.4>
946    media-range = ( "*/*" / ( type "/*" ) / ( type "/" subtype ) ) *( OWS
947     ";" OWS parameter )
948    media-type = type "/" subtype *( OWS ";" OWS parameter )
949    method = token
950    minute = 2DIGIT
951    month = %x4A.61.6E ; Jan
952     / %x46.65.62 ; Feb
953     / %x4D.61.72 ; Mar
954     / %x41.70.72 ; Apr
955     / %x4D.61.79 ; May
956     / %x4A.75.6E ; Jun
957     / %x4A.75.6C ; Jul
958     / %x41.75.67 ; Aug
959     / %x53.65.70 ; Sep
960     / %x4F.63.74 ; Oct
961     / %x4E.6F.76 ; Nov
962     / %x44.65.63 ; Dec
963
964
965Section 1.2, paragraph 21:
966OLD:
967
968    obs-date = rfc850-date / asctime-date
969    parameter = token "=" ( token / quoted-string )
970    partial-URI = <partial-URI, see [RFC7230], Section 2.7>
971    product = token [ "/" product-version ]
972    product-version = token
973 
974    quoted-string = <quoted-string, see [RFC7230], Section 3.2.6>
975    qvalue = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
976
977NEW:
978
979    obs-date = rfc850-date / asctime-date
980 
981    parameter = token "=" ( token / quoted-string )
982    partial-URI = <partial-URI, defined in [RFC7230], Section 2.7>
983    product = token [ "/" product-version ]
984    product-version = token
985    quoted-string = <quoted-string, defined in [RFC7230], Section 3.2.6>
986    qvalue = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
987
988
989Section 1.2, paragraph 24:
990OLD:
991
992    time-of-day = hour ":" minute ":" second
993    token = <token, see [RFC7230], Section 3.2.6>
994    type = token
995
996NEW:
997
998    time-of-day = hour ":" minute ":" second
999    token = <token, defined in [RFC7230], Section 3.2.6>
1000    type = token
1001
1002
1003Section 1.2, paragraph 34:
1004OLD:
1005
1006    2
1007       200 OK (status code)  51
1008       201 Created (status code)  51
1009       202 Accepted (status code)  52
1010       203 Non-Authoritative Information (status code)  52
1011       204 No Content (status code)  53
1012       205 Reset Content (status code)  53
1013
1014NEW:
1015
1016    2
1017       200 OK (status code)  51
1018       201 Created (status code)  52
1019       202 Accepted (status code)  52
1020       203 Non-Authoritative Information (status code)  52
1021       204 No Content (status code)  53
1022       205 Reset Content (status code)  53
1023
1024
1025Section 1.2, paragraph 47:
1026OLD:
1027
1028    M
1029       Max-Forwards header field  36
1030       MIME-Version header field  89
1031
1032NEW:
1033
1034    M
1035       Max-Forwards header field  36
1036       MIME-Version header field  88
1037
1038
1039Section 345, paragraph 1:
1040OLD:
1041
1042    EMail: fielding@gbiv.com
1043    URI:   http://roy.gbiv.com/
1044    Julian F. Reschke (editor)
1045    greenbytes GmbH
1046    Hafenweg 16
1047    Muenster, NW  48155
1048    Germany
1049
1050NEW:
1051
1052    EMail: fielding@gbiv.com
1053    URI:   http://roy.gbiv.com/
1054 
1055    Julian F. Reschke (editor)
1056    greenbytes GmbH
1057    Hafenweg 16
1058    Muenster, NW  48155
1059    Germany
1060
Note: See TracBrowser for help on using the repository browser.