Changeset 2651
- Timestamp:
- 06/05/14 17:07:58 (7 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 17 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/auth48/p1-messaging.unpg.txt
r2650 r2651 1011 1011 scheme have no shared identity with the "http" scheme even if their 1012 1012 resource identifiers indicate the same authority (the same host 1013 listening to the same TCP port). They are distinct name 1013 listening to the same TCP port). They are distinct namespaces and 1014 1014 are considered to be distinct origin servers. However, an extension 1015 1015 to HTTP that is defined to apply to entire host domains, such as the … … 3573 3573 8.4. Transfer Coding Registry 3574 3574 3575 The HTTP Transfer Coding Registry defines the name 3575 The HTTP Transfer Coding Registry defines the namespace for transfer 3576 3576 coding names. It is maintained at 3577 3577 <http://www.iana.org/assignments/http-parameters>. … … 3602 3602 codings defined in Section 4.2. 3603 3603 3604 Values to be added to this name space require IETF Review (see3605 Section 4.1 of [RFC5226]), and MUST conform to the purpose of3606 transfer codingdefined in this specification.3604 Values to be added to this namespace require IETF Review (see Section 3605 4.1 of [RFC5226]), and MUST conform to the purpose of transfer coding 3606 defined in this specification. 3607 3607 3608 3608 Use of program names for the identification of encoding formats is … … 3664 3664 8.6. Upgrade Token Registry 3665 3665 3666 The HTTP Upgrade Token Registry defines the name 3666 The HTTP Upgrade Token Registry defines the namespace for protocol- 3667 3667 name tokens used to identify protocols in the Upgrade header field. 3668 3668 The registry is maintained at -
draft-ietf-httpbis/latest/auth48/p2-semantics.unpg.txt
r2647 r2651 4165 4165 8.1. Method Registry 4166 4166 4167 The HTTP Method Registry defines the name space for the request4168 methodtoken (Section 4). The method registry will be created and4167 The HTTP Method Registry defines the namespace for the request method 4168 token (Section 4). The method registry will be created and 4169 4169 maintained at (the suggested URI) 4170 4170 <http://www.iana.org/assignments/http-methods>. … … 4182 4182 o Pointer to specification text 4183 4183 4184 Values to be added to this name 4184 Values to be added to this namespace require IETF Review (see 4185 4185 [RFC5226], Section 4.1). 4186 4186 … … 4248 4248 8.2. Status Code Registry 4249 4249 4250 The HTTP Status Code Registry defines the name 4250 The HTTP Status Code Registry defines the namespace for the response 4251 4251 status-code token (Section 6). The status code registry is 4252 4252 maintained at <http://www.iana.org/assignments/http-status-codes>. … … 4265 4265 o Pointer to specification text 4266 4266 4267 Values to be added to the HTTP status code name 4267 Values to be added to the HTTP status code namespace require IETF 4268 4268 Review (see [RFC5226], Section 4.1). 4269 4269 … … 4548 4548 8.4. Content Coding Registry 4549 4549 4550 The HTTP Content Coding Registry defines the name 4550 The HTTP Content Coding Registry defines the namespace for content 4551 4551 coding names (Section 4.2 of [RFC7230]). The content coding registry 4552 4552 is maintained at <http://www.iana.org/assignments/http-parameters>. … … 4577 4577 Section 4.2 of [RFC7230]). 4578 4578 4579 Values to be added to this name space require IETF Review (see4580 Section 4.1 of [RFC5226]), and MUST conform to the purpose of content4581 codingdefined in this section.4579 Values to be added to this namespace require IETF Review (see Section 4580 4.1 of [RFC5226]), and MUST conform to the purpose of content coding 4581 defined in this section. 4582 4582 4583 4583 8.4.2. Registrations -
draft-ietf-httpbis/latest/auth48/rfc7230.abdiff.txt
r2650 r2651 1139 1139 OLD: 1140 1140 1141 The HTTP Transfer Coding Registry defines the name 1141 The HTTP Transfer Coding Registry defines the namespace for transfer 1142 1142 coding names. It is maintained at 1143 1143 <http://www.iana.org/assignments/http-parameters>. … … 1150 1150 1151 1151 1152 Section 8.4.1., paragraph 5:1153 OLD:1154 1155 Values to be added to this name space require IETF Review (see1156 Section 4.1 of [RFC5226]), and MUST conform to the purpose of1157 transfer coding defined in this specification.1158 1159 NEW:1160 1161 Values to be added to this namespace require IETF Review (see Section1162 4.1 of [RFC5226]), and MUST conform to the purpose of transfer coding1163 defined in this specification.1164 1165 1166 1152 Section 8.4.2., paragraph 1: 1167 1153 OLD: … … 1203 1189 OLD: 1204 1190 1205 The HTTP Upgrade Token Registry defines the name 1191 The HTTP Upgrade Token Registry defines the namespace for protocol- 1206 1192 name tokens used to identify protocols in the Upgrade header field. 1207 1193 The registry is maintained at -
draft-ietf-httpbis/latest/auth48/rfc7230.diff.html
r2650 r2651 380 380 <tr><td class="lineno" valign="top"></td><td class="left"> target resource within that origin server's name space. The optional</td><td> </td><td class="right"> target resource within that origin server's name space. The optional</td><td class="lineno" valign="top"></td></tr> 381 381 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 382 <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 18, line 44</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 18, line 44</em></th><td></td></tr> 383 <tr><td class="lineno" valign="top"></td><td class="left"> through the use of strong encryption, end-to-end, prior to sending</td><td> </td><td class="right"> through the use of strong encryption, end-to-end, prior to sending</td><td class="lineno" valign="top"></td></tr> 384 <tr><td class="lineno" valign="top"></td><td class="left"> the first HTTP request.</td><td> </td><td class="right"> the first HTTP request.</td><td class="lineno" valign="top"></td></tr> 385 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 386 <tr><td class="lineno" valign="top"></td><td class="left"> https-URI = "https:" "//" authority path-abempty [ "?" query ]</td><td> </td><td class="right"> https-URI = "https:" "//" authority path-abempty [ "?" query ]</td><td class="lineno" valign="top"></td></tr> 387 <tr><td class="lineno" valign="top"></td><td class="left"> [ "#" fragment ]</td><td> </td><td class="right"> [ "#" fragment ]</td><td class="lineno" valign="top"></td></tr> 388 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 389 <tr><td class="lineno" valign="top"></td><td class="left"> Note that the "https" URI scheme depends on both TLS and TCP for</td><td> </td><td class="right"> Note that the "https" URI scheme depends on both TLS and TCP for</td><td class="lineno" valign="top"></td></tr> 390 <tr><td class="lineno" valign="top"></td><td class="left"> establishing authority. Resources made available via the "https"</td><td> </td><td class="right"> establishing authority. Resources made available via the "https"</td><td class="lineno" valign="top"></td></tr> 391 <tr><td class="lineno" valign="top"></td><td class="left"> scheme have no shared identity with the "http" scheme even if their</td><td> </td><td class="right"> scheme have no shared identity with the "http" scheme even if their</td><td class="lineno" valign="top"></td></tr> 392 <tr><td class="lineno" valign="top"></td><td class="left"> resource identifiers indicate the same authority (the same host</td><td> </td><td class="right"> resource identifiers indicate the same authority (the same host</td><td class="lineno" valign="top"></td></tr> 393 <tr><td><a name="diff0021" /></td></tr> 394 <tr><td class="lineno" valign="top"></td><td class="lblock"> listening to the same TCP port). They are distinct name<span class="delete"> </span>spaces and</td><td> </td><td class="rblock"> listening to the same TCP port). They are distinct namespaces and</td><td class="lineno" valign="top"></td></tr> 395 <tr><td class="lineno" valign="top"></td><td class="left"> are considered to be distinct origin servers. However, an extension</td><td> </td><td class="right"> are considered to be distinct origin servers. However, an extension</td><td class="lineno" valign="top"></td></tr> 396 <tr><td class="lineno" valign="top"></td><td class="left"> to HTTP that is defined to apply to entire host domains, such as the</td><td> </td><td class="right"> to HTTP that is defined to apply to entire host domains, such as the</td><td class="lineno" valign="top"></td></tr> 397 <tr><td class="lineno" valign="top"></td><td class="left"> Cookie protocol [RFC6265], can allow information set by one service</td><td> </td><td class="right"> Cookie protocol [RFC6265], can allow information set by one service</td><td class="lineno" valign="top"></td></tr> 398 <tr><td class="lineno" valign="top"></td><td class="left"> to impact communication with other services within a matching group</td><td> </td><td class="right"> to impact communication with other services within a matching group</td><td class="lineno" valign="top"></td></tr> 399 <tr><td class="lineno" valign="top"></td><td class="left"> of host domains.</td><td> </td><td class="right"> of host domains.</td><td class="lineno" valign="top"></td></tr> 400 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 401 <tr><td class="lineno" valign="top"></td><td class="left"> The process for authoritative access to an "https" identified</td><td> </td><td class="right"> The process for authoritative access to an "https" identified</td><td class="lineno" valign="top"></td></tr> 402 <tr><td class="lineno" valign="top"></td><td class="left"> resource is defined in [RFC2818].</td><td> </td><td class="right"> resource is defined in [RFC2818].</td><td class="lineno" valign="top"></td></tr> 403 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 404 <tr><td class="lineno" valign="top"></td><td class="left">2.7.3. http and https URI Normalization and Comparison</td><td> </td><td class="right">2.7.3. http and https URI Normalization and Comparison</td><td class="lineno" valign="top"></td></tr> 405 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 406 <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 19, line 18</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 19, line 18</em></th><td></td></tr> 382 <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 19, line 18</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 19, line 18</em></th><td></td></tr> 407 383 <tr><td class="lineno" valign="top"></td><td class="left"> Since the "http" and "https" schemes conform to the URI generic</td><td> </td><td class="right"> Since the "http" and "https" schemes conform to the URI generic</td><td class="lineno" valign="top"></td></tr> 408 384 <tr><td class="lineno" valign="top"></td><td class="left"> syntax, such URIs are normalized and compared according to the</td><td> </td><td class="right"> syntax, such URIs are normalized and compared according to the</td><td class="lineno" valign="top"></td></tr> … … 415 391 <tr><td class="lineno" valign="top"></td><td class="left"> path component is equivalent to an absolute path of "/", so the</td><td> </td><td class="right"> path component is equivalent to an absolute path of "/", so the</td><td class="lineno" valign="top"></td></tr> 416 392 <tr><td class="lineno" valign="top"></td><td class="left"> normal form is to provide a path of "/" instead. The scheme and host</td><td> </td><td class="right"> normal form is to provide a path of "/" instead. The scheme and host</td><td class="lineno" valign="top"></td></tr> 417 <tr><td><a name="diff002 2" /></td></tr>393 <tr><td><a name="diff0021" /></td></tr> 418 394 <tr><td class="lineno" valign="top"></td><td class="lblock"> are case<span class="delete">-</span>insensitive and normally provided in lowercase; all other</td><td> </td><td class="rblock"> are case<span class="insert"> </span>insensitive and normally provided in lowercase; all other</td><td class="lineno" valign="top"></td></tr> 419 395 <tr><td class="lineno" valign="top"></td><td class="left"> components are compared in a case-sensitive manner. Characters other</td><td> </td><td class="right"> components are compared in a case-sensitive manner. Characters other</td><td class="lineno" valign="top"></td></tr> … … 428 404 <tr><td class="lineno" valign="top"></td><td class="left"> http://EXAMPLE.com:/%7esmith/home.html</td><td> </td><td class="right"> http://EXAMPLE.com:/%7esmith/home.html</td><td class="lineno" valign="top"></td></tr> 429 405 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 430 <tr bgcolor="gray" ><td></td><th><a name="part-l1 4" /><small>skipping to change at</small><em> page 20, line 45</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 20, line 45</em></th><td></td></tr>406 <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 20, line 45</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 20, line 45</em></th><td></td></tr> 431 407 <tr><td class="lineno" valign="top"></td><td class="left">3.1. Start Line</td><td> </td><td class="right">3.1. Start Line</td><td class="lineno" valign="top"></td></tr> 432 408 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 439 415 <tr><td class="lineno" valign="top"></td><td class="left"> In theory, a client could receive requests and a server could receive</td><td> </td><td class="right"> In theory, a client could receive requests and a server could receive</td><td class="lineno" valign="top"></td></tr> 440 416 <tr><td class="lineno" valign="top"></td><td class="left"> responses, distinguishing them by their different start-line formats,</td><td> </td><td class="right"> responses, distinguishing them by their different start-line formats,</td><td class="lineno" valign="top"></td></tr> 441 <tr><td><a name="diff002 3" /></td></tr>417 <tr><td><a name="diff0022" /></td></tr> 442 418 <tr><td class="lineno" valign="top"></td><td class="lblock"> but, in practice, servers are implemented <span class="delete">to only</span> expect a request (a</td><td> </td><td class="rblock"> but, in practice, servers are implemented <span class="insert">only to</span> expect a request (a</td><td class="lineno" valign="top"></td></tr> 443 419 <tr><td class="lineno" valign="top"></td><td class="left"> response is interpreted as an unknown or invalid request method) and</td><td> </td><td class="right"> response is interpreted as an unknown or invalid request method) and</td><td class="lineno" valign="top"></td></tr> … … 448 424 <tr><td class="lineno" valign="top"></td><td class="left">3.1.1. Request Line</td><td> </td><td class="right">3.1.1. Request Line</td><td class="lineno" valign="top"></td></tr> 449 425 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 450 <tr><td><a name="diff002 4" /></td></tr>426 <tr><td><a name="diff0023" /></td></tr> 451 427 <tr><td class="lineno" valign="top"></td><td class="lblock"> A request-line begins with a method <span class="delete">token,</span> followed by a single space</td><td> </td><td class="rblock"> A request-line begins with a method <span class="insert">token and is</span> followed by a single</td><td class="lineno" valign="top"></td></tr> 452 428 <tr><td class="lineno" valign="top"></td><td class="lblock"> (SP), the request-target, another single space (SP), the protocol</td><td> </td><td class="rblock"> space (SP), the request-target, another single space (SP), the</td><td class="lineno" valign="top"></td></tr> … … 456 432 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 457 433 <tr><td class="lineno" valign="top"></td><td class="left"> The method token indicates the request method to be performed on the</td><td> </td><td class="right"> The method token indicates the request method to be performed on the</td><td class="lineno" valign="top"></td></tr> 458 <tr><td><a name="diff002 5" /></td></tr>434 <tr><td><a name="diff0024" /></td></tr> 459 435 <tr><td class="lineno" valign="top"></td><td class="lblock"> target resource. The request method is case<span class="delete">-</span>sensitive.</td><td> </td><td class="rblock"> target resource. The request method is case<span class="insert"> </span>sensitive.</td><td class="lineno" valign="top"></td></tr> 460 436 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 469 445 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 470 446 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 471 <tr bgcolor="gray" ><td></td><th><a name="part-l1 5" /><small>skipping to change at</small><em> page 22, line 8</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 22, line 8</em></th><td></td></tr>447 <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 22, line 8</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 22, line 8</em></th><td></td></tr> 472 448 <tr><td class="lineno" valign="top"></td><td class="left"> longer than any URI it wishes to parse MUST respond with a 414 (URI</td><td> </td><td class="right"> longer than any URI it wishes to parse MUST respond with a 414 (URI</td><td class="lineno" valign="top"></td></tr> 473 449 <tr><td class="lineno" valign="top"></td><td class="left"> Too Long) status code (see Section 6.5.12 of [RFC7231]).</td><td> </td><td class="right"> Too Long) status code (see Section 6.5.12 of [RFC7231]).</td><td class="lineno" valign="top"></td></tr> … … 480 456 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 481 457 <tr><td class="lineno" valign="top"></td><td class="left"> The first line of a response message is the status-line, consisting</td><td> </td><td class="right"> The first line of a response message is the status-line, consisting</td><td class="lineno" valign="top"></td></tr> 482 <tr><td><a name="diff002 6" /></td></tr>458 <tr><td><a name="diff0025" /></td></tr> 483 459 <tr><td class="lineno" valign="top"></td><td class="lblock"> of the protocol version, a space (SP), the status code, another</td><td> </td><td class="rblock"> of the protocol version, a space (SP), the status code, another <span class="insert">space</span></td><td class="lineno" valign="top"></td></tr> 484 460 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">space,</span> a possibly empty textual phrase describing the status code,</td><td> </td><td class="rblock"><span class="insert"> (SP),</span> a possibly empty textual phrase describing the status code,</td><td class="lineno" valign="top"></td></tr> … … 495 471 <tr><td class="lineno" valign="top"></td><td class="left"> first digit), the status codes defined by this specification,</td><td> </td><td class="right"> first digit), the status codes defined by this specification,</td><td class="lineno" valign="top"></td></tr> 496 472 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 497 <tr bgcolor="gray" ><td></td><th><a name="part-l1 6" /><small>skipping to change at</small><em> page 23, line 29</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 23, line 29</em></th><td></td></tr>473 <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 23, line 29</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 23, line 29</em></th><td></td></tr> 498 474 <tr><td class="lineno" valign="top"></td><td class="left"> evaluation, or refine the meaning of responses.</td><td> </td><td class="right"> evaluation, or refine the meaning of responses.</td><td class="lineno" valign="top"></td></tr> 499 475 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 506 482 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 507 483 <tr><td class="lineno" valign="top"></td><td class="left"> All defined header fields ought to be registered with IANA in the</td><td> </td><td class="right"> All defined header fields ought to be registered with IANA in the</td><td class="lineno" valign="top"></td></tr> 508 <tr><td><a name="diff002 7" /></td></tr>484 <tr><td><a name="diff0026" /></td></tr> 509 485 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">Message Header Field R</span>egistry, as described in Section 8.3 of</td><td> </td><td class="rblock"> <span class="insert">"Message Headers" field r</span>egistry, as described in Section 8.3 of</td><td class="lineno" valign="top"></td></tr> 510 486 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7231].</td><td> </td><td class="right"> [RFC7231].</td><td class="lineno" valign="top"></td></tr> … … 519 495 <tr><td class="lineno" valign="top"></td><td class="left"> apply a request to the target resource until the entire request</td><td> </td><td class="right"> apply a request to the target resource until the entire request</td><td class="lineno" valign="top"></td></tr> 520 496 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 521 <tr bgcolor="gray" ><td></td><th><a name="part-l1 7" /><small>skipping to change at</small><em> page 24, line 14</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 24, line 14</em></th><td></td></tr>497 <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 24, line 14</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 24, line 14</em></th><td></td></tr> 522 498 <tr><td class="lineno" valign="top"></td><td class="left"> the combined field value in order, separated by a comma. The order</td><td> </td><td class="right"> the combined field value in order, separated by a comma. The order</td><td class="lineno" valign="top"></td></tr> 523 499 <tr><td class="lineno" valign="top"></td><td class="left"> in which header fields with the same field name are received is</td><td> </td><td class="right"> in which header fields with the same field name are received is</td><td class="lineno" valign="top"></td></tr> … … 530 506 <tr><td class="lineno" valign="top"></td><td class="left"> list syntax, violating the above requirements on multiple header</td><td> </td><td class="right"> list syntax, violating the above requirements on multiple header</td><td class="lineno" valign="top"></td></tr> 531 507 <tr><td class="lineno" valign="top"></td><td class="left"> fields with the same name. Since it cannot be combined into a</td><td> </td><td class="right"> fields with the same name. Since it cannot be combined into a</td><td class="lineno" valign="top"></td></tr> 532 <tr><td><a name="diff002 8" /></td></tr>508 <tr><td><a name="diff0027" /></td></tr> 533 509 <tr><td class="lineno" valign="top"></td><td class="lblock"> single field-value, recipients ought to handle <span class="delete">"Set-Cookie"</span> as a</td><td> </td><td class="rblock"> single field-value, recipients ought to handle <span class="insert">Set-Cookie</span> as a</td><td class="lineno" valign="top"></td></tr> 534 510 <tr><td class="lineno" valign="top"></td><td class="left"> special case while processing header fields. (See Appendix A.2.3</td><td> </td><td class="right"> special case while processing header fields. (See Appendix A.2.3</td><td class="lineno" valign="top"></td></tr> … … 545 521 <tr><td class="lineno" valign="top"></td><td class="left"> preferred to improve readability, a sender SHOULD generate the</td><td> </td><td class="right"> preferred to improve readability, a sender SHOULD generate the</td><td class="lineno" valign="top"></td></tr> 546 522 <tr><td class="lineno" valign="top"></td><td class="left"> optional whitespace as a single SP; otherwise, a sender SHOULD NOT</td><td> </td><td class="right"> optional whitespace as a single SP; otherwise, a sender SHOULD NOT</td><td class="lineno" valign="top"></td></tr> 547 <tr><td><a name="diff002 9" /></td></tr>523 <tr><td><a name="diff0028" /></td></tr> 548 524 <tr><td class="lineno" valign="top"></td><td class="lblock"> generate optional whitespace except as needed to white<span class="delete">-</span>out invalid or</td><td> </td><td class="rblock"> generate optional whitespace except as needed to white<span class="insert"> </span>out invalid or</td><td class="lineno" valign="top"></td></tr> 549 525 <tr><td class="lineno" valign="top"></td><td class="left"> unwanted protocol elements during in-place message filtering.</td><td> </td><td class="right"> unwanted protocol elements during in-place message filtering.</td><td class="lineno" valign="top"></td></tr> … … 558 534 <tr><td class="lineno" valign="top"></td><td class="left"> it before interpreting the protocol element.</td><td> </td><td class="right"> it before interpreting the protocol element.</td><td class="lineno" valign="top"></td></tr> 559 535 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 560 <tr bgcolor="gray" ><td></td><th><a name="part-l1 8" /><small>skipping to change at</small><em> page 25, line 12</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 25, line 12</em></th><td></td></tr>536 <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 25, line 12</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 25, line 12</em></th><td></td></tr> 561 537 <tr><td class="lineno" valign="top"></td><td class="left"> BWS = OWS</td><td> </td><td class="right"> BWS = OWS</td><td class="lineno" valign="top"></td></tr> 562 538 <tr><td class="lineno" valign="top"></td><td class="left"> ; "bad" whitespace</td><td> </td><td class="right"> ; "bad" whitespace</td><td class="lineno" valign="top"></td></tr> … … 569 545 <tr><td class="lineno" valign="top"></td><td class="left"> (usually after the message's entire header section has been</td><td> </td><td class="right"> (usually after the message's entire header section has been</td><td class="lineno" valign="top"></td></tr> 570 546 <tr><td class="lineno" valign="top"></td><td class="left"> processed). Consequently, this specification does not use ABNF rules</td><td> </td><td class="right"> processed). Consequently, this specification does not use ABNF rules</td><td class="lineno" valign="top"></td></tr> 571 <tr><td><a name="diff00 30" /></td></tr>547 <tr><td><a name="diff0029" /></td></tr> 572 548 <tr><td class="lineno" valign="top"></td><td class="lblock"> to define each "<span class="delete">Field-Name: Field V</span>alue" pair, as was done in</td><td> </td><td class="rblock"> to define each "<span class="insert">field-name: field-v</span>alue" pair, as was done in</td><td class="lineno" valign="top"></td></tr> 573 549 <tr><td class="lineno" valign="top"></td><td class="left"> previous editions. Instead, this specification uses ABNF rules that</td><td> </td><td class="right"> previous editions. Instead, this specification uses ABNF rules that</td><td class="lineno" valign="top"></td></tr> … … 582 558 <tr><td class="lineno" valign="top"></td><td class="left"> server MUST reject any received request message that contains</td><td> </td><td class="right"> server MUST reject any received request message that contains</td><td class="lineno" valign="top"></td></tr> 583 559 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 584 <tr bgcolor="gray" ><td></td><th><a name="part-l1 9" /><small>skipping to change at</small><em> page 26, line 16</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 26, line 16</em></th><td></td></tr>560 <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 26, line 16</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 26, line 16</em></th><td></td></tr> 585 561 <tr><td class="lineno" valign="top"></td><td class="left"> received, or replace each received obs-fold with one or more SP</td><td> </td><td class="right"> received, or replace each received obs-fold with one or more SP</td><td class="lineno" valign="top"></td></tr> 586 562 <tr><td class="lineno" valign="top"></td><td class="left"> octets prior to interpreting the field value or forwarding the</td><td> </td><td class="right"> octets prior to interpreting the field value or forwarding the</td><td class="lineno" valign="top"></td></tr> … … 593 569 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 594 570 <tr><td class="lineno" valign="top"></td><td class="left"> Historically, HTTP has allowed field content with text in the</td><td> </td><td class="right"> Historically, HTTP has allowed field content with text in the</td><td class="lineno" valign="top"></td></tr> 595 <tr><td><a name="diff003 1" /></td></tr>571 <tr><td><a name="diff0030" /></td></tr> 596 572 <tr><td class="lineno" valign="top"></td><td class="lblock"> ISO-8859-1 <span class="delete">charset [ISO-8859-1]</span>, supporting other charsets only</td><td> </td><td class="rblock"> ISO-8859-1 <span class="insert">[ISO-8859-1] charset</span>, supporting other charsets only</td><td class="lineno" valign="top"></td></tr> 597 573 <tr><td class="lineno" valign="top"></td><td class="left"> through use of [RFC2047] encoding. In practice, most HTTP header</td><td> </td><td class="right"> through use of [RFC2047] encoding. In practice, most HTTP header</td><td class="lineno" valign="top"></td></tr> … … 606 582 <tr><td class="lineno" valign="top"></td><td class="left"> field or on the length of the header section as a whole, as described</td><td> </td><td class="right"> field or on the length of the header section as a whole, as described</td><td class="lineno" valign="top"></td></tr> 607 583 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 608 <tr bgcolor="gray" ><td></td><th><a name="part-l 20" /><small>skipping to change at</small><em> page 33, line 6</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 33, line 6</em></th><td></td></tr>584 <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 33, line 6</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 33, line 6</em></th><td></td></tr> 609 585 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 610 586 <tr><td class="lineno" valign="top"></td><td class="left"> 6. If this is a request message and none of the above are true, then</td><td> </td><td class="right"> 6. If this is a request message and none of the above are true, then</td><td class="lineno" valign="top"></td></tr> … … 617 593 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 618 594 <tr><td class="lineno" valign="top"></td><td class="left"> Since there is no way to distinguish a successfully completed, close-</td><td> </td><td class="right"> Since there is no way to distinguish a successfully completed, close-</td><td class="lineno" valign="top"></td></tr> 619 <tr><td><a name="diff003 2" /></td></tr>595 <tr><td><a name="diff0031" /></td></tr> 620 596 <tr><td class="lineno" valign="top"></td><td class="lblock"> delimited message from a partially<span class="delete">-</span>received message interrupted by</td><td> </td><td class="rblock"> delimited message from a partially<span class="insert"> </span>received message interrupted by</td><td class="lineno" valign="top"></td></tr> 621 597 <tr><td class="lineno" valign="top"></td><td class="left"> network failure, a server SHOULD generate encoding or length-</td><td> </td><td class="right"> network failure, a server SHOULD generate encoding or length-</td><td class="lineno" valign="top"></td></tr> … … 630 606 <tr><td class="lineno" valign="top"></td><td class="left"> valid Content-Length header field if the message body length is known</td><td> </td><td class="right"> valid Content-Length header field if the message body length is known</td><td class="lineno" valign="top"></td></tr> 631 607 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 632 <tr bgcolor="gray" ><td></td><th><a name="part-l2 1" /><small>skipping to change at</small><em> page 35, line 26</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 35, line 26</em></th><td></td></tr>608 <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><small>skipping to change at</small><em> page 35, line 26</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 35, line 26</em></th><td></td></tr> 633 609 <tr><td class="lineno" valign="top"></td><td class="left"> / "compress" ; Section 4.2.1</td><td> </td><td class="right"> / "compress" ; Section 4.2.1</td><td class="lineno" valign="top"></td></tr> 634 610 <tr><td class="lineno" valign="top"></td><td class="left"> / "deflate" ; Section 4.2.2</td><td> </td><td class="right"> / "deflate" ; Section 4.2.2</td><td class="lineno" valign="top"></td></tr> … … 641 617 <tr><td class="lineno" valign="top"></td><td class="left"> transfer-parameter = token BWS "=" BWS ( token / quoted-string )</td><td> </td><td class="right"> transfer-parameter = token BWS "=" BWS ( token / quoted-string )</td><td class="lineno" valign="top"></td></tr> 642 618 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 643 <tr><td><a name="diff003 3" /></td></tr>619 <tr><td><a name="diff0032" /></td></tr> 644 620 <tr><td class="lineno" valign="top"></td><td class="lblock"> All transfer-coding names are <span class="delete">case-insensitive</span> and ought to be</td><td> </td><td class="rblock"> All transfer-coding names are <span class="insert">case insensitive</span> and ought to be</td><td class="lineno" valign="top"></td></tr> 645 621 <tr><td class="lineno" valign="top"></td><td class="lblock"> registered within the <span class="delete">HTTP</span> Transfer <span class="delete">Coding</span> registry, as defined in</td><td> </td><td class="rblock"> registered within the <span class="insert">"HTTP</span> Transfer <span class="insert">Coding"</span> registry, as defined in</td><td class="lineno" valign="top"></td></tr> … … 655 631 <tr><td class="lineno" valign="top"></td><td class="left"> sequence of length-delimited buffers, which enables the sender to</td><td> </td><td class="right"> sequence of length-delimited buffers, which enables the sender to</td><td class="lineno" valign="top"></td></tr> 656 632 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 657 <tr bgcolor="gray" ><td></td><th><a name="part-l2 2" /><small>skipping to change at</small><em> page 49, line 29</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 49, line 29</em></th><td></td></tr>633 <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><small>skipping to change at</small><em> page 49, line 29</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 49, line 29</em></th><td></td></tr> 658 634 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 659 635 <tr><td class="lineno" valign="top"></td><td class="left"> A proxy MUST NOT modify the "absolute-path" and "query" parts of the</td><td> </td><td class="right"> A proxy MUST NOT modify the "absolute-path" and "query" parts of the</td><td class="lineno" valign="top"></td></tr> … … 666 642 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 667 643 <tr><td class="lineno" valign="top"></td><td class="left"> A proxy MUST NOT transform the payload (Section 3.3 of [RFC7231]) of</td><td> </td><td class="right"> A proxy MUST NOT transform the payload (Section 3.3 of [RFC7231]) of</td><td class="lineno" valign="top"></td></tr> 668 <tr><td><a name="diff003 4" /></td></tr>644 <tr><td><a name="diff0033" /></td></tr> 669 645 <tr><td class="lineno" valign="top"></td><td class="lblock"> a message that contains a no-transform <span class="delete">cache-c</span>ontrol directive</td><td> </td><td class="rblock"> a message that contains a no-transform <span class="insert">Cache-C</span>ontrol directive</td><td class="lineno" valign="top"></td></tr> 670 646 <tr><td class="lineno" valign="top"></td><td class="left"> (Section 5.2 of [RFC7234]).</td><td> </td><td class="right"> (Section 5.2 of [RFC7234]).</td><td class="lineno" valign="top"></td></tr> 671 647 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 672 648 <tr><td class="lineno" valign="top"></td><td class="left"> A proxy MAY transform the payload of a message that does not contain</td><td> </td><td class="right"> A proxy MAY transform the payload of a message that does not contain</td><td class="lineno" valign="top"></td></tr> 673 <tr><td><a name="diff003 5" /></td></tr>649 <tr><td><a name="diff0034" /></td></tr> 674 650 <tr><td class="lineno" valign="top"></td><td class="lblock"> a no-transform <span class="delete">cache-c</span>ontrol directive. A proxy that transforms a</td><td> </td><td class="rblock"> a no-transform <span class="insert">Cache-C</span>ontrol directive. A proxy that transforms a</td><td class="lineno" valign="top"></td></tr> 675 651 <tr><td class="lineno" valign="top"></td><td class="left"> payload MUST add a Warning header field with the warn-code of 214</td><td> </td><td class="right"> payload MUST add a Warning header field with the warn-code of 214</td><td class="lineno" valign="top"></td></tr> … … 681 657 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 682 658 <tr><td class="lineno" valign="top"></td><td class="left"> A proxy SHOULD NOT modify header fields that provide information</td><td> </td><td class="right"> A proxy SHOULD NOT modify header fields that provide information</td><td class="lineno" valign="top"></td></tr> 683 <tr><td><a name="diff003 6" /></td></tr>659 <tr><td><a name="diff0035" /></td></tr> 684 660 <tr><td class="lineno" valign="top"></td><td class="lblock"> about the end<span class="delete"> </span>points of the communication chain, the resource state,</td><td> </td><td class="rblock"> about the endpoints of the communication chain, the resource state,</td><td class="lineno" valign="top"></td></tr> 685 661 <tr><td class="lineno" valign="top"></td><td class="left"> or the selected representation (other than the payload) unless the</td><td> </td><td class="right"> or the selected representation (other than the payload) unless the</td><td class="lineno" valign="top"></td></tr> … … 689 665 <tr><td class="lineno" valign="top"></td><td class="left">6. Connection Management</td><td> </td><td class="right">6. Connection Management</td><td class="lineno" valign="top"></td></tr> 690 666 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 691 <tr><td><a name="diff003 7" /></td></tr>667 <tr><td><a name="diff0036" /></td></tr> 692 668 <tr><td class="lineno" valign="top"></td><td class="lblock"> HTTP messaging is independent of the underlying <span class="delete">transport</span> or <span class="delete">session-</span></td><td> </td><td class="rblock"> HTTP messaging is independent of the underlying <span class="insert">transport-</span> or</td><td class="lineno" valign="top"></td></tr> 693 669 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> layer</span> connection protocol(s). HTTP only presumes a reliable</td><td> </td><td class="rblock"> <span class="insert">session-layer</span> connection protocol(s). HTTP only presumes a reliable</td><td class="lineno" valign="top"></td></tr> … … 703 679 <tr><td class="lineno" valign="top"></td><td class="left"> default TCP port of 80, but the client might be configured to use a</td><td> </td><td class="right"> default TCP port of 80, but the client might be configured to use a</td><td class="lineno" valign="top"></td></tr> 704 680 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 705 <tr bgcolor="gray" ><td></td><th><a name="part-l2 3" /><small>skipping to change at</small><em> page 51, line 8</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 51, line 8</em></th><td></td></tr>681 <tr bgcolor="gray" ><td></td><th><a name="part-l22" /><small>skipping to change at</small><em> page 51, line 8</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 51, line 8</em></th><td></td></tr> 706 682 <tr><td class="lineno" valign="top"></td><td class="left"> recipients on the chain ("end-to-end"), enabling the message to be</td><td> </td><td class="right"> recipients on the chain ("end-to-end"), enabling the message to be</td><td class="lineno" valign="top"></td></tr> 707 683 <tr><td class="lineno" valign="top"></td><td class="left"> self-descriptive and allowing future connection-specific extensions</td><td> </td><td class="right"> self-descriptive and allowing future connection-specific extensions</td><td class="lineno" valign="top"></td></tr> … … 714 690 <tr><td class="lineno" valign="top"></td><td class="left"> connection-option = token</td><td> </td><td class="right"> connection-option = token</td><td class="lineno" valign="top"></td></tr> 715 691 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 716 <tr><td><a name="diff003 8" /></td></tr>692 <tr><td><a name="diff0037" /></td></tr> 717 693 <tr><td class="lineno" valign="top"></td><td class="lblock"> Connection options are case<span class="delete">-</span>insensitive.</td><td> </td><td class="rblock"> Connection options are case<span class="insert"> </span>insensitive.</td><td class="lineno" valign="top"></td></tr> 718 694 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 727 703 <tr><td class="lineno" valign="top"></td><td class="left"> connection option. In contrast, a connection-specific header field</td><td> </td><td class="right"> connection option. In contrast, a connection-specific header field</td><td class="lineno" valign="top"></td></tr> 728 704 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 729 <tr bgcolor="gray" ><td></td><th><a name="part-l2 4" /><small>skipping to change at</small><em> page 51, line 51</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 51, line 51</em></th><td></td></tr>705 <tr bgcolor="gray" ><td></td><th><a name="part-l23" /><small>skipping to change at</small><em> page 51, line 51</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 51, line 51</em></th><td></td></tr> 730 706 <tr><td class="lineno" valign="top"></td><td class="left"> A client that does not support persistent connections MUST send the</td><td> </td><td class="right"> A client that does not support persistent connections MUST send the</td><td class="lineno" valign="top"></td></tr> 731 707 <tr><td class="lineno" valign="top"></td><td class="left"> "close" connection option in every request message.</td><td> </td><td class="right"> "close" connection option in every request message.</td><td class="lineno" valign="top"></td></tr> … … 738 714 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 739 715 <tr><td class="lineno" valign="top"></td><td class="left"> It is beyond the scope of this specification to describe how</td><td> </td><td class="right"> It is beyond the scope of this specification to describe how</td><td class="lineno" valign="top"></td></tr> 740 <tr><td><a name="diff003 9" /></td></tr>716 <tr><td><a name="diff0038" /></td></tr> 741 717 <tr><td class="lineno" valign="top"></td><td class="lblock"> connections are established via various transport or session-layer</td><td> </td><td class="rblock"> connections are established via various transport<span class="insert">-</span> or session-layer</td><td class="lineno" valign="top"></td></tr> 742 718 <tr><td class="lineno" valign="top"></td><td class="left"> protocols. Each connection applies to only one transport link.</td><td> </td><td class="right"> protocols. Each connection applies to only one transport link.</td><td class="lineno" valign="top"></td></tr> … … 746 722 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP/1.1 defaults to the use of "persistent connections", allowing</td><td> </td><td class="right"> HTTP/1.1 defaults to the use of "persistent connections", allowing</td><td class="lineno" valign="top"></td></tr> 747 723 <tr><td class="lineno" valign="top"></td><td class="left"> multiple requests and responses to be carried over a single</td><td> </td><td class="right"> multiple requests and responses to be carried over a single</td><td class="lineno" valign="top"></td></tr> 748 <tr><td><a name="diff00 40" /></td></tr>724 <tr><td><a name="diff0039" /></td></tr> 749 725 <tr><td class="lineno" valign="top"></td><td class="lblock"> connection. The "close" connection<span class="delete">-</span>option is used to signal that a</td><td> </td><td class="rblock"> connection. The "close" connection<span class="insert"> </span>option is used to signal that a</td><td class="lineno" valign="top"></td></tr> 750 726 <tr><td class="lineno" valign="top"></td><td class="left"> connection will not persist after the current request/response. HTTP</td><td> </td><td class="right"> connection will not persist after the current request/response. HTTP</td><td class="lineno" valign="top"></td></tr> … … 755 731 <tr><td class="lineno" valign="top"></td><td class="left"> Connection header field (if any):</td><td> </td><td class="right"> Connection header field (if any):</td><td class="lineno" valign="top"></td></tr> 756 732 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 757 <tr><td><a name="diff004 1" /></td></tr>733 <tr><td><a name="diff0040" /></td></tr> 758 734 <tr><td class="lineno" valign="top"></td><td class="lblock"> o If the <span class="delete">close</span> connection option is present, the connection will not</td><td> </td><td class="rblock"> o If the <span class="insert">"close"</span> connection option is present, the connection will</td><td class="lineno" valign="top"></td></tr> 759 735 <tr><td class="lineno" valign="top"></td><td class="lblock"> persist after the current response; else,</td><td> </td><td class="rblock"> not persist after the current response; else,</td><td class="lineno" valign="top"></td></tr> … … 770 746 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 771 747 <tr><td class="lineno" valign="top"></td><td class="left"> A client MAY send additional requests on a persistent connection</td><td> </td><td class="right"> A client MAY send additional requests on a persistent connection</td><td class="lineno" valign="top"></td></tr> 772 <tr><td><a name="diff004 2" /></td></tr>748 <tr><td><a name="diff0041" /></td></tr> 773 749 <tr><td class="lineno" valign="top"></td><td class="lblock"> until it sends or receives a <span class="delete">close</span> connection option or receives an</td><td> </td><td class="rblock"> until it sends or receives a <span class="insert">"close"</span> connection option or receives an</td><td class="lineno" valign="top"></td></tr> 774 750 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP/1.0 response without a "keep-alive" connection option.</td><td> </td><td class="right"> HTTP/1.0 response without a "keep-alive" connection option.</td><td class="lineno" valign="top"></td></tr> … … 783 759 <tr><td class="lineno" valign="top"></td><td class="left"> reuse the same connection for a subsequent request.</td><td> </td><td class="right"> reuse the same connection for a subsequent request.</td><td class="lineno" valign="top"></td></tr> 784 760 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 785 <tr bgcolor="gray" ><td></td><th><a name="part-l2 5" /><small>skipping to change at</small><em> page 55, line 19</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 55, line 19</em></th><td></td></tr>761 <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 55, line 19</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 55, line 19</em></th><td></td></tr> 786 762 <tr><td class="lineno" valign="top"></td><td class="left"> enables allocated system resources to be reclaimed.</td><td> </td><td class="right"> enables allocated system resources to be reclaimed.</td><td class="lineno" valign="top"></td></tr> 787 763 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 794 770 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 795 771 <tr><td class="lineno" valign="top"></td><td class="left"> A server SHOULD sustain persistent connections, when possible, and</td><td> </td><td class="right"> A server SHOULD sustain persistent connections, when possible, and</td><td class="lineno" valign="top"></td></tr> 796 <tr><td><a name="diff004 3" /></td></tr>772 <tr><td><a name="diff0042" /></td></tr> 797 773 <tr><td class="lineno" valign="top"></td><td class="lblock"> allow the underlying transport's flow<span class="delete"> </span>control mechanisms to resolve</td><td> </td><td class="rblock"> allow the underlying transport's flow<span class="insert">-</span>control mechanisms to resolve</td><td class="lineno" valign="top"></td></tr> 798 774 <tr><td class="lineno" valign="top"></td><td class="left"> temporary overloads, rather than terminate connections with the</td><td> </td><td class="right"> temporary overloads, rather than terminate connections with the</td><td class="lineno" valign="top"></td></tr> … … 807 783 <tr><td class="lineno" valign="top"></td><td class="left"> the connection.</td><td> </td><td class="right"> the connection.</td><td class="lineno" valign="top"></td></tr> 808 784 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 809 <tr><td><a name="diff004 4" /></td></tr>785 <tr><td><a name="diff0043" /></td></tr> 810 786 <tr><td class="lineno" valign="top"></td><td class="lblock">6.6. Tear<span class="delete">-</span>down</td><td> </td><td class="rblock">6.6. Teardown</td><td class="lineno" valign="top"></td></tr> 811 787 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 814 790 <tr><td class="lineno" valign="top"></td><td class="left"> the connection after the current request/response pair.</td><td> </td><td class="right"> the connection after the current request/response pair.</td><td class="lineno" valign="top"></td></tr> 815 791 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 816 <tr><td><a name="diff004 5" /></td></tr>792 <tr><td><a name="diff0044" /></td></tr> 817 793 <tr><td class="lineno" valign="top"></td><td class="lblock"> A client that sends a <span class="delete">close</span> connection option MUST NOT send further</td><td> </td><td class="rblock"> A client that sends a <span class="insert">"close"</span> connection option MUST NOT send further</td><td class="lineno" valign="top"></td></tr> 818 794 <tr><td class="lineno" valign="top"></td><td class="left"> requests on that connection (after the one containing close) and MUST</td><td> </td><td class="right"> requests on that connection (after the one containing close) and MUST</td><td class="lineno" valign="top"></td></tr> … … 820 796 <tr><td class="lineno" valign="top"></td><td class="left"> corresponding to this request.</td><td> </td><td class="right"> corresponding to this request.</td><td class="lineno" valign="top"></td></tr> 821 797 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 822 <tr><td><a name="diff004 6" /></td></tr>798 <tr><td><a name="diff0045" /></td></tr> 823 799 <tr><td class="lineno" valign="top"></td><td class="lblock"> A server that receives a <span class="delete">close</span> connection option MUST initiate a</td><td> </td><td class="rblock"> A server that receives a <span class="insert">"close"</span> connection option MUST initiate a</td><td class="lineno" valign="top"></td></tr> 824 800 <tr><td class="lineno" valign="top"></td><td class="left"> close of the connection (see below) after it sends the final response</td><td> </td><td class="right"> close of the connection (see below) after it sends the final response</td><td class="lineno" valign="top"></td></tr> … … 828 804 <tr><td class="lineno" valign="top"></td><td class="left"> connection.</td><td> </td><td class="right"> connection.</td><td class="lineno" valign="top"></td></tr> 829 805 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 830 <tr><td><a name="diff004 7" /></td></tr>806 <tr><td><a name="diff0046" /></td></tr> 831 807 <tr><td class="lineno" valign="top"></td><td class="lblock"> A server that sends a <span class="delete">close</span> connection option MUST initiate a close</td><td> </td><td class="rblock"> A server that sends a <span class="insert">"close"</span> connection option MUST initiate a close</td><td class="lineno" valign="top"></td></tr> 832 808 <tr><td class="lineno" valign="top"></td><td class="left"> of the connection (see below) after it sends the response containing</td><td> </td><td class="right"> of the connection (see below) after it sends the response containing</td><td class="lineno" valign="top"></td></tr> … … 834 810 <tr><td class="lineno" valign="top"></td><td class="left"> that connection.</td><td> </td><td class="right"> that connection.</td><td class="lineno" valign="top"></td></tr> 835 811 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 836 <tr><td><a name="diff004 8" /></td></tr>812 <tr><td><a name="diff0047" /></td></tr> 837 813 <tr><td class="lineno" valign="top"></td><td class="lblock"> A client that receives a <span class="delete">close</span> connection option MUST cease sending</td><td> </td><td class="rblock"> A client that receives a <span class="insert">"close"</span> connection option MUST cease sending</td><td class="lineno" valign="top"></td></tr> 838 814 <tr><td class="lineno" valign="top"></td><td class="left"> requests on that connection and close the connection after reading</td><td> </td><td class="right"> requests on that connection and close the connection after reading</td><td class="lineno" valign="top"></td></tr> … … 844 820 <tr><td class="lineno" valign="top"></td><td class="left"> a significant risk that the client will not be able to read the last</td><td> </td><td class="right"> a significant risk that the client will not be able to read the last</td><td class="lineno" valign="top"></td></tr> 845 821 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP response. If the server receives additional data from the</td><td> </td><td class="right"> HTTP response. If the server receives additional data from the</td><td class="lineno" valign="top"></td></tr> 846 <tr><td><a name="diff004 9" /></td></tr>822 <tr><td><a name="diff0048" /></td></tr> 847 823 <tr><td class="lineno" valign="top"></td><td class="lblock"> client on a fully<span class="delete">-</span>closed connection, such as another request that was</td><td> </td><td class="rblock"> client on a fully<span class="insert"> </span>closed connection, such as another request that was</td><td class="lineno" valign="top"></td></tr> 848 824 <tr><td class="lineno" valign="top"></td><td class="left"> sent by the client before receiving the server's response, the</td><td> </td><td class="right"> sent by the client before receiving the server's response, the</td><td class="lineno" valign="top"></td></tr> … … 857 833 <tr><td class="lineno" valign="top"></td><td class="left"> continues to read from the connection until it receives a</td><td> </td><td class="right"> continues to read from the connection until it receives a</td><td class="lineno" valign="top"></td></tr> 858 834 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 859 <tr bgcolor="gray" ><td></td><th><a name="part-l2 6" /><small>skipping to change at</small><em> page 57, line 31</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 57, line 31</em></th><td></td></tr>835 <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 57, line 31</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 57, line 31</em></th><td></td></tr> 860 836 <tr><td class="lineno" valign="top"></td><td class="left"> The following is a hypothetical example sent by a client:</td><td> </td><td class="right"> The following is a hypothetical example sent by a client:</td><td class="lineno" valign="top"></td></tr> 861 837 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 868 844 <tr><td class="lineno" valign="top"></td><td class="left"> after the protocol change is entirely dependent upon the new</td><td> </td><td class="right"> after the protocol change is entirely dependent upon the new</td><td class="lineno" valign="top"></td></tr> 869 845 <tr><td class="lineno" valign="top"></td><td class="left"> protocol(s) chosen. However, immediately after sending the 101</td><td> </td><td class="right"> protocol(s) chosen. However, immediately after sending the 101</td><td class="lineno" valign="top"></td></tr> 870 <tr><td><a name="diff00 50" /></td></tr>846 <tr><td><a name="diff0049" /></td></tr> 871 847 <tr><td class="lineno" valign="top"></td><td class="lblock"> response, the server is expected to continue responding to the</td><td> </td><td class="rblock"> <span class="insert">(Switching Protocols)</span> response, the server is expected to continue</td><td class="lineno" valign="top"></td></tr> 872 848 <tr><td class="lineno" valign="top"></td><td class="lblock"> original request as if it had received its equivalent within the new</td><td> </td><td class="rblock"> responding to the original request as if it had received its</td><td class="lineno" valign="top"></td></tr> … … 886 862 <tr><td class="lineno" valign="top"></td><td class="left"> protocol; an OPTIONS request can be honored by any protocol.</td><td> </td><td class="right"> protocol; an OPTIONS request can be honored by any protocol.</td><td class="lineno" valign="top"></td></tr> 887 863 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 888 <tr bgcolor="gray" ><td></td><th><a name="part-l2 7" /><small>skipping to change at</small><em> page 59, line 35</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 59, line 35</em></th><td></td></tr>864 <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 59, line 35</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 59, line 35</em></th><td></td></tr> 889 865 <tr><td class="lineno" valign="top"></td><td class="left"> #element => [ ( "," / element ) *( OWS "," [ OWS element ] ) ]</td><td> </td><td class="right"> #element => [ ( "," / element ) *( OWS "," [ OWS element ] ) ]</td><td class="lineno" valign="top"></td></tr> 890 866 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 897 873 <tr><td class="lineno" valign="top"></td><td class="left"> example-list-elmt = token ; see Section 3.2.6</td><td> </td><td class="right"> example-list-elmt = token ; see Section 3.2.6</td><td class="lineno" valign="top"></td></tr> 898 874 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 899 <tr><td><a name="diff005 1" /></td></tr>875 <tr><td><a name="diff0050" /></td></tr> 900 876 <tr><td class="lineno" valign="top"></td><td class="lblock"> Then the following are valid values for example-list (not including</td><td> </td><td class="rblock"> Then<span class="insert">,</span> the following are valid values for example-list (not including</td><td class="lineno" valign="top"></td></tr> 901 877 <tr><td class="lineno" valign="top"></td><td class="left"> the double quotes, which are present for delimitation only):</td><td> </td><td class="right"> the double quotes, which are present for delimitation only):</td><td class="lineno" valign="top"></td></tr> … … 919 895 <tr><td class="lineno" valign="top"></td><td class="left">8.1. Header Field Registration</td><td> </td><td class="right">8.1. Header Field Registration</td><td class="lineno" valign="top"></td></tr> 920 896 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 921 <tr><td><a name="diff005 2" /></td></tr>897 <tr><td><a name="diff0051" /></td></tr> 922 898 <tr><td class="lineno" valign="top"></td><td class="lblock"> HTTP header fields are registered within the <span class="delete">Message Header Field</span></td><td> </td><td class="rblock"> HTTP header fields are registered within the <span class="insert">"Message Header" field</span></td><td class="lineno" valign="top"></td></tr> 923 899 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> Registry</span> maintained at</td><td> </td><td class="rblock"><span class="insert"> registry</span> maintained at</td><td class="lineno" valign="top"></td></tr> 924 900 <tr><td class="lineno" valign="top"></td><td class="left"> <http://www.iana.org/assignments/message-headers/>.</td><td> </td><td class="right"> <http://www.iana.org/assignments/message-headers/>.</td><td class="lineno" valign="top"></td></tr> 925 901 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 926 <tr><td><a name="diff005 3" /></td></tr>902 <tr><td><a name="diff0052" /></td></tr> 927 903 <tr><td class="lineno" valign="top"></td><td class="lblock"> This document defines the following HTTP header fields, so <span class="delete">their</span></td><td> </td><td class="rblock"> This document defines the following HTTP header fields, so <span class="insert">the</span></td><td class="lineno" valign="top"></td></tr> 928 904 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> associated</span> registry <span class="delete">entries shall be</span> updated <span class="delete">according to the</span></td><td> </td><td class="rblock"><span class="insert"> "Permanent Message Header Field Names"</span> registry <span class="insert">has been</span> updated</td><td class="lineno" valign="top"></td></tr> … … 942 918 <tr><td class="lineno" valign="top"></td><td class="left"> +-------------------+----------+----------+---------------+</td><td> </td><td class="right"> +-------------------+----------+----------+---------------+</td><td class="lineno" valign="top"></td></tr> 943 919 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 944 <tr><td><a name="diff005 4" /></td></tr>920 <tr><td><a name="diff0053" /></td></tr> 945 921 <tr><td class="lineno" valign="top"></td><td class="lblock"> Furthermore, the header field-name "Close" <span class="delete">shall be</span> registered as</td><td> </td><td class="rblock"> Furthermore, the header field-name "Close" <span class="insert">has been</span> registered as</td><td class="lineno" valign="top"></td></tr> 946 922 <tr><td class="lineno" valign="top"></td><td class="left"> "reserved", since using that name as an HTTP header field might</td><td> </td><td class="right"> "reserved", since using that name as an HTTP header field might</td><td class="lineno" valign="top"></td></tr> … … 962 938 <tr><td class="lineno" valign="top"></td><td class="left"> <http://www.iana.org/assignments/uri-schemes/>.</td><td> </td><td class="right"> <http://www.iana.org/assignments/uri-schemes/>.</td><td class="lineno" valign="top"></td></tr> 963 939 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 964 <tr><td><a name="diff005 5" /></td></tr>940 <tr><td><a name="diff0054" /></td></tr> 965 941 <tr><td class="lineno" valign="top"></td><td class="lblock"> This document defines the following URI schemes, so <span class="delete">their associated</span></td><td> </td><td class="rblock"> This document defines the following URI schemes, so <span class="insert">the "Permanent</span></td><td class="lineno" valign="top"></td></tr> 966 942 <tr><td class="lineno" valign="top"></td><td class="lblock"> registry <span class="delete">entries shall be</span> updated <span class="delete">according to the permanent</span></td><td> </td><td class="rblock"><span class="insert"> URI Schemes"</span> registry <span class="insert">has been</span> updated <span class="insert">accordingly.</span></td><td class="lineno" valign="top"></td></tr> … … 980 956 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 981 957 <tr><td class="lineno" valign="top"></td><td class="left"> This document serves as the specification for the Internet media</td><td> </td><td class="right"> This document serves as the specification for the Internet media</td><td class="lineno" valign="top"></td></tr> 982 <tr><td><a name="diff005 6" /></td></tr>958 <tr><td><a name="diff0055" /></td></tr> 983 959 <tr><td class="lineno" valign="top"></td><td class="lblock"> types "message/http" and "application/http". The following <span class="delete">is to be</span></td><td> </td><td class="rblock"> types "message/http" and "application/http". The following <span class="insert">has been</span></td><td class="lineno" valign="top"></td></tr> 984 960 <tr><td class="lineno" valign="top"></td><td class="left"> registered with IANA.</td><td> </td><td class="right"> registered with IANA.</td><td class="lineno" valign="top"></td></tr> … … 993 969 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 994 970 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 995 <tr bgcolor="gray" ><td></td><th><a name="part-l2 8" /><small>skipping to change at</small><em> page 62, line 20</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 62, line 20</em></th><td></td></tr>971 <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 62, line 20</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 62, line 20</em></th><td></td></tr> 996 972 <tr><td class="lineno" valign="top"></td><td class="left"> Additional information:</td><td> </td><td class="right"> Additional information:</td><td class="lineno" valign="top"></td></tr> 997 973 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1004 980 <tr><td class="lineno" valign="top"></td><td class="left"> Macintosh file type code(s): N/A</td><td> </td><td class="right"> Macintosh file type code(s): N/A</td><td class="lineno" valign="top"></td></tr> 1005 981 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1006 <tr><td><a name="diff005 7" /></td></tr>982 <tr><td><a name="diff0056" /></td></tr> 1007 983 <tr><td class="lineno" valign="top"></td><td class="lblock"> Person and email address to contact for further information: See</td><td> </td><td class="rblock"> Person and email address to contact for further information:</td><td class="lineno" valign="top"></td></tr> 1008 984 <tr><td class="lineno" valign="top"></td><td class="lblock"> Authors' Addresses Section.</td><td> </td><td class="rblock"> See Authors' Addresses Section.</td><td class="lineno" valign="top"></td></tr> … … 1018 994 <tr><td class="lineno" valign="top"></td><td class="left">8.3.2. Internet Media Type application/http</td><td> </td><td class="right">8.3.2. Internet Media Type application/http</td><td class="lineno" valign="top"></td></tr> 1019 995 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1020 <tr bgcolor="gray" ><td></td><th><a name="part-l2 9" /><small>skipping to change at</small><em> page 63, line 7</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 63, line 7</em></th><td></td></tr>996 <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 63, line 7</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 63, line 7</em></th><td></td></tr> 1021 997 <tr><td class="lineno" valign="top"></td><td class="left"> version: The HTTP-version number of the enclosed messages (e.g.,</td><td> </td><td class="right"> version: The HTTP-version number of the enclosed messages (e.g.,</td><td class="lineno" valign="top"></td></tr> 1022 998 <tr><td class="lineno" valign="top"></td><td class="left"> "1.1"). If not present, the version can be determined from the</td><td> </td><td class="right"> "1.1"). If not present, the version can be determined from the</td><td class="lineno" valign="top"></td></tr> … … 1029 1005 <tr><td class="lineno" valign="top"></td><td class="left"> Encoding considerations: HTTP messages enclosed by this type are in</td><td> </td><td class="right"> Encoding considerations: HTTP messages enclosed by this type are in</td><td class="lineno" valign="top"></td></tr> 1030 1006 <tr><td class="lineno" valign="top"></td><td class="left"> "binary" format; use of an appropriate Content-Transfer-Encoding</td><td> </td><td class="right"> "binary" format; use of an appropriate Content-Transfer-Encoding</td><td class="lineno" valign="top"></td></tr> 1007 <tr><td><a name="diff0057" /></td></tr> 1008 <tr><td class="lineno" valign="top"></td><td class="lblock"> is required when transmitted via <span class="delete">E-</span>mail.</td><td> </td><td class="rblock"> is required when transmitted via <span class="insert">e</span>mail.</td><td class="lineno" valign="top"></td></tr> 1009 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1010 <tr><td class="lineno" valign="top"></td><td class="left"> Security considerations: see Section 9</td><td> </td><td class="right"> Security considerations: see Section 9</td><td class="lineno" valign="top"></td></tr> 1011 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1012 <tr><td class="lineno" valign="top"></td><td class="left"> Interoperability considerations: N/A</td><td> </td><td class="right"> Interoperability considerations: N/A</td><td class="lineno" valign="top"></td></tr> 1013 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1014 <tr><td class="lineno" valign="top"></td><td class="left"> Published specification: This specification (see Section 8.3.2).</td><td> </td><td class="right"> Published specification: This specification (see Section 8.3.2).</td><td class="lineno" valign="top"></td></tr> 1015 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1016 <tr><td class="lineno" valign="top"></td><td class="left"> Applications that use this media type: N/A</td><td> </td><td class="right"> Applications that use this media type: N/A</td><td class="lineno" valign="top"></td></tr> 1017 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1018 <tr><td class="lineno" valign="top"></td><td class="left"> Fragment identifier considerations: N/A</td><td> </td><td class="right"> Fragment identifier considerations: N/A</td><td class="lineno" valign="top"></td></tr> 1019 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1020 <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 63, line 29</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 63, line 29</em></th><td></td></tr> 1021 <tr><td class="lineno" valign="top"></td><td class="left"> Additional information:</td><td> </td><td class="right"> Additional information:</td><td class="lineno" valign="top"></td></tr> 1022 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1023 <tr><td class="lineno" valign="top"></td><td class="left"> Deprecated alias names for this type: N/A</td><td> </td><td class="right"> Deprecated alias names for this type: N/A</td><td class="lineno" valign="top"></td></tr> 1024 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1025 <tr><td class="lineno" valign="top"></td><td class="left"> Magic number(s): N/A</td><td> </td><td class="right"> Magic number(s): N/A</td><td class="lineno" valign="top"></td></tr> 1026 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1027 <tr><td class="lineno" valign="top"></td><td class="left"> File extension(s): N/A</td><td> </td><td class="right"> File extension(s): N/A</td><td class="lineno" valign="top"></td></tr> 1028 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1029 <tr><td class="lineno" valign="top"></td><td class="left"> Macintosh file type code(s): N/A</td><td> </td><td class="right"> Macintosh file type code(s): N/A</td><td class="lineno" valign="top"></td></tr> 1030 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1031 1031 <tr><td><a name="diff0058" /></td></tr> 1032 <tr><td class="lineno" valign="top"></td><td class="lblock"> is required when transmitted via <span class="delete">E-</span>mail.</td><td> </td><td class="rblock"> is required when transmitted via <span class="insert">e</span>mail.</td><td class="lineno" valign="top"></td></tr>1033 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1034 <tr><td class="lineno" valign="top"></td><td class="left"> Security considerations: see Section 9</td><td> </td><td class="right"> Security considerations: see Section 9</td><td class="lineno" valign="top"></td></tr>1035 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1036 <tr><td class="lineno" valign="top"></td><td class="left"> Interoperability considerations: N/A</td><td> </td><td class="right"> Interoperability considerations: N/A</td><td class="lineno" valign="top"></td></tr>1037 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1038 <tr><td class="lineno" valign="top"></td><td class="left"> Published specification: This specification (see Section 8.3.2).</td><td> </td><td class="right"> Published specification: This specification (see Section 8.3.2).</td><td class="lineno" valign="top"></td></tr>1039 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1040 <tr><td class="lineno" valign="top"></td><td class="left"> Applications that use this media type: N/A</td><td> </td><td class="right"> Applications that use this media type: N/A</td><td class="lineno" valign="top"></td></tr>1041 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1042 <tr><td class="lineno" valign="top"></td><td class="left"> Fragment identifier considerations: N/A</td><td> </td><td class="right"> Fragment identifier considerations: N/A</td><td class="lineno" valign="top"></td></tr>1043 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>1044 <tr bgcolor="gray" ><td></td><th><a name="part-l30" /><small>skipping to change at</small><em> page 63, line 29</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 63, line 29</em></th><td></td></tr>1045 <tr><td class="lineno" valign="top"></td><td class="left"> Additional information:</td><td> </td><td class="right"> Additional information:</td><td class="lineno" valign="top"></td></tr>1046 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1047 <tr><td class="lineno" valign="top"></td><td class="left"> Deprecated alias names for this type: N/A</td><td> </td><td class="right"> Deprecated alias names for this type: N/A</td><td class="lineno" valign="top"></td></tr>1048 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1049 <tr><td class="lineno" valign="top"></td><td class="left"> Magic number(s): N/A</td><td> </td><td class="right"> Magic number(s): N/A</td><td class="lineno" valign="top"></td></tr>1050 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1051 <tr><td class="lineno" valign="top"></td><td class="left"> File extension(s): N/A</td><td> </td><td class="right"> File extension(s): N/A</td><td class="lineno" valign="top"></td></tr>1052 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1053 <tr><td class="lineno" valign="top"></td><td class="left"> Macintosh file type code(s): N/A</td><td> </td><td class="right"> Macintosh file type code(s): N/A</td><td class="lineno" valign="top"></td></tr>1054 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1055 <tr><td><a name="diff0059" /></td></tr>1056 1032 <tr><td class="lineno" valign="top"></td><td class="lblock"> Person and email address to contact for further information: See</td><td> </td><td class="rblock"> Person and email address to contact for further information:</td><td class="lineno" valign="top"></td></tr> 1057 1033 <tr><td class="lineno" valign="top"></td><td class="lblock"> Authors' Addresses Section.</td><td> </td><td class="rblock"> See Authors' Addresses Section.</td><td class="lineno" valign="top"></td></tr> … … 1067 1043 <tr><td class="lineno" valign="top"></td><td class="left">8.4. Transfer Coding Registry</td><td> </td><td class="right">8.4. Transfer Coding Registry</td><td class="lineno" valign="top"></td></tr> 1068 1044 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1069 <tr><td><a name="diff00 60" /></td></tr>1070 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Transfer <span class="delete">Coding Registry</span> defines the <span class="delete">name space</span> for transfer</td><td> </td><td class="rblock"> The <span class="insert">"HTTP</span> Transfer <span class="insert">Coding" registry</span> defines the <span class="insert">namespace</span>for</td><td class="lineno" valign="top"></td></tr>1045 <tr><td><a name="diff0059" /></td></tr> 1046 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Transfer <span class="delete">Coding Registry</span> defines the namespace for transfer</td><td> </td><td class="rblock"> The <span class="insert">"HTTP</span> Transfer <span class="insert">Coding" registry</span> defines the namespace for</td><td class="lineno" valign="top"></td></tr> 1071 1047 <tr><td class="lineno" valign="top"></td><td class="lblock"> coding names. It is maintained at</td><td> </td><td class="rblock"> transfer coding names. It is maintained at</td><td class="lineno" valign="top"></td></tr> 1072 1048 <tr><td class="lineno" valign="top"></td><td class="left"> <http://www.iana.org/assignments/http-parameters>.</td><td> </td><td class="right"> <http://www.iana.org/assignments/http-parameters>.</td><td class="lineno" valign="top"></td></tr> … … 1080 1056 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1081 1057 <tr><td class="lineno" valign="top"></td><td class="left"> o Pointer to specification text</td><td> </td><td class="right"> o Pointer to specification text</td><td class="lineno" valign="top"></td></tr> 1082 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1083 <tr><td class="lineno" valign="top"></td><td class="left"> Names of transfer codings MUST NOT overlap with names of content</td><td> </td><td class="right"> Names of transfer codings MUST NOT overlap with names of content</td><td class="lineno" valign="top"></td></tr> 1084 <tr><td class="lineno" valign="top"></td><td class="left"> codings (Section 3.1.2.1 of [RFC7231]) unless the encoding</td><td> </td><td class="right"> codings (Section 3.1.2.1 of [RFC7231]) unless the encoding</td><td class="lineno" valign="top"></td></tr> 1085 <tr><td class="lineno" valign="top"></td><td class="left"> transformation is identical, as is the case for the compression</td><td> </td><td class="right"> transformation is identical, as is the case for the compression</td><td class="lineno" valign="top"></td></tr> 1086 <tr><td class="lineno" valign="top"></td><td class="left"> codings defined in Section 4.2.</td><td> </td><td class="right"> codings defined in Section 4.2.</td><td class="lineno" valign="top"></td></tr> 1087 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1088 <tr><td><a name="diff0061" /></td></tr> 1089 <tr><td class="lineno" valign="top"></td><td class="lblock"> Values to be added to this <span class="delete">name space</span> require IETF Review (see</td><td> </td><td class="rblock"> Values to be added to this <span class="insert">namespace</span> require IETF Review (see Section</td><td class="lineno" valign="top"></td></tr> 1090 <tr><td class="lineno" valign="top"></td><td class="lblock"> Section 4.1 of [RFC5226]), and MUST conform to the purpose of</td><td> </td><td class="rblock"> 4.1 of [RFC5226]), and MUST conform to the purpose of transfer coding</td><td class="lineno" valign="top"></td></tr> 1091 <tr><td class="lineno" valign="top"></td><td class="lblock"> transfer coding defined in this specification.</td><td> </td><td class="rblock"> defined in this specification.</td><td class="lineno" valign="top"></td></tr> 1058 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1059 <tr bgcolor="gray" ><td></td><th><a name="part-l30" /><small>skipping to change at</small><em> page 64, line 22</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 64, line 22</em></th><td></td></tr> 1060 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1061 <tr><td class="lineno" valign="top"></td><td class="left"> Values to be added to this namespace require IETF Review (see Section</td><td> </td><td class="right"> Values to be added to this namespace require IETF Review (see Section</td><td class="lineno" valign="top"></td></tr> 1062 <tr><td class="lineno" valign="top"></td><td class="left"> 4.1 of [RFC5226]), and MUST conform to the purpose of transfer coding</td><td> </td><td class="right"> 4.1 of [RFC5226]), and MUST conform to the purpose of transfer coding</td><td class="lineno" valign="top"></td></tr> 1063 <tr><td class="lineno" valign="top"></td><td class="left"> defined in this specification.</td><td> </td><td class="right"> defined in this specification.</td><td class="lineno" valign="top"></td></tr> 1092 1064 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1093 1065 <tr><td class="lineno" valign="top"></td><td class="left"> Use of program names for the identification of encoding formats is</td><td> </td><td class="right"> Use of program names for the identification of encoding formats is</td><td class="lineno" valign="top"></td></tr> … … 1096 1068 <tr><td class="lineno" valign="top"></td><td class="left">8.4.2. Registration</td><td> </td><td class="right">8.4.2. Registration</td><td class="lineno" valign="top"></td></tr> 1097 1069 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1098 <tr><td><a name="diff006 2" /></td></tr>1070 <tr><td><a name="diff0060" /></td></tr> 1099 1071 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP Transfer Coding Registry shall be</span> updated with the</td><td> </td><td class="rblock"> The <span class="insert">"HTTP Transfer Coding Registry" has been</span> updated with the</td><td class="lineno" valign="top"></td></tr> 1100 1072 <tr><td class="lineno" valign="top"></td><td class="left"> registrations below:</td><td> </td><td class="right"> registrations below:</td><td class="lineno" valign="top"></td></tr> … … 1115 1087 <tr><td class="lineno" valign="top"></td><td class="left">8.5. Content Coding Registration</td><td> </td><td class="right">8.5. Content Coding Registration</td><td class="lineno" valign="top"></td></tr> 1116 1088 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1117 <tr><td><a name="diff006 3" /></td></tr>1089 <tr><td><a name="diff0061" /></td></tr> 1118 1090 <tr><td class="lineno" valign="top"></td><td class="lblock"> IANA maintains the <span class="delete">registry of HTTP Content Codings</span> at</td><td> </td><td class="rblock"> IANA maintains the <span class="insert">"HTTP Content Coding Registry"</span> at</td><td class="lineno" valign="top"></td></tr> 1119 1091 <tr><td class="lineno" valign="top"></td><td class="left"> <http://www.iana.org/assignments/http-parameters>.</td><td> </td><td class="right"> <http://www.iana.org/assignments/http-parameters>.</td><td class="lineno" valign="top"></td></tr> 1120 1092 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1121 <tr><td><a name="diff006 4" /></td></tr>1093 <tr><td><a name="diff0062" /></td></tr> 1122 1094 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP Content Codings Registry shall be</span> updated with the</td><td> </td><td class="rblock"> The <span class="insert">"HTTP Content Codings Registry" has been</span> updated with the</td><td class="lineno" valign="top"></td></tr> 1123 1095 <tr><td class="lineno" valign="top"></td><td class="left"> registrations below:</td><td> </td><td class="right"> registrations below:</td><td class="lineno" valign="top"></td></tr> … … 1137 1109 <tr><td class="lineno" valign="top"></td><td class="left">8.6. Upgrade Token Registry</td><td> </td><td class="right">8.6. Upgrade Token Registry</td><td class="lineno" valign="top"></td></tr> 1138 1110 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1139 <tr><td><a name="diff006 5" /></td></tr>1140 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Upgrade Token <span class="delete">Registry</span> defines the <span class="delete">name space</span>for <span class="delete">protocol-</span></td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Upgrade Token <span class="insert">Registry"</span></td><td class="lineno" valign="top"></td></tr>1141 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> name</span> tokens used to identify protocols in the Upgrade header field.</td><td> </td><td class="rblock"> defines the <span class="insert">namespace</span>for <span class="insert">protocol-name</span> tokens used to identify</td><td class="lineno" valign="top"></td></tr>1111 <tr><td><a name="diff0063" /></td></tr> 1112 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Upgrade Token <span class="delete">Registry</span> defines the namespace for <span class="delete">protocol-</span></td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Upgrade Token <span class="insert">Registry"</span></td><td class="lineno" valign="top"></td></tr> 1113 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> name</span> tokens used to identify protocols in the Upgrade header field.</td><td> </td><td class="rblock"> defines the namespace for <span class="insert">protocol-name</span> tokens used to identify</td><td class="lineno" valign="top"></td></tr> 1142 1114 <tr><td class="lineno" valign="top"></td><td class="lblock"> The registry is maintained at</td><td> </td><td class="rblock"> protocols in the Upgrade header field. The registry is maintained at</td><td class="lineno" valign="top"></td></tr> 1143 1115 <tr><td class="lineno" valign="top"></td><td class="left"> <http://www.iana.org/assignments/http-upgrade-tokens>.</td><td> </td><td class="right"> <http://www.iana.org/assignments/http-upgrade-tokens>.</td><td class="lineno" valign="top"></td></tr> … … 1163 1135 <tr><td class="lineno" valign="top"></td><td class="left">8.6.2. Upgrade Token Registration</td><td> </td><td class="right">8.6.2. Upgrade Token Registration</td><td class="lineno" valign="top"></td></tr> 1164 1136 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1165 <tr><td><a name="diff006 6" /></td></tr>1137 <tr><td><a name="diff0064" /></td></tr> 1166 1138 <tr><td class="lineno" valign="top"></td><td class="lblock"> The "HTTP" entry in the <span class="delete">HTTP</span> Upgrade <span class="delete">Token Registry</span> shall be updated</td><td> </td><td class="rblock"> The "HTTP" entry in the <span class="insert">"HTTP</span> Upgrade <span class="insert">Token" registry</span> shall be</td><td class="lineno" valign="top"></td></tr> 1167 1139 <tr><td class="lineno" valign="top"></td><td class="lblock"> with the registration below:</td><td> </td><td class="rblock"> updated with the registration below:</td><td class="lineno" valign="top"></td></tr> … … 1188 1160 <tr><td class="lineno" valign="top"></td><td class="left"> Domain Name Service (DNS), and the hierarchy of servers from which it</td><td> </td><td class="right"> Domain Name Service (DNS), and the hierarchy of servers from which it</td><td class="lineno" valign="top"></td></tr> 1189 1161 <tr><td class="lineno" valign="top"></td><td class="left"> obtains resolution results, could impact the authenticity of address</td><td> </td><td class="right"> obtains resolution results, could impact the authenticity of address</td><td class="lineno" valign="top"></td></tr> 1190 <tr><td><a name="diff006 7" /></td></tr>1162 <tr><td><a name="diff0065" /></td></tr> 1191 1163 <tr><td class="lineno" valign="top"></td><td class="lblock"> mappings; DNS Security Extensions (DNSSEC<span class="delete">, [RFC4033]) are</span> one way to</td><td> </td><td class="rblock"> mappings; DNS Security Extensions (DNSSEC<span class="insert">) ([RFC4033]) is</span> one way to</td><td class="lineno" valign="top"></td></tr> 1192 1164 <tr><td class="lineno" valign="top"></td><td class="left"> improve authenticity.</td><td> </td><td class="right"> improve authenticity.</td><td class="lineno" valign="top"></td></tr> … … 1206 1178 <tr><td class="lineno" valign="top"></td><td class="left">9.2. Risks of Intermediaries</td><td> </td><td class="right">9.2. Risks of Intermediaries</td><td class="lineno" valign="top"></td></tr> 1207 1179 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1208 <tr><td><a name="diff006 8" /></td></tr>1180 <tr><td><a name="diff0066" /></td></tr> 1209 1181 <tr><td class="lineno" valign="top"></td><td class="lblock"> By their very nature, HTTP intermediaries are <span class="delete">men-in-the-middle, and</span></td><td> </td><td class="rblock"> By their very nature, HTTP intermediaries are <span class="insert">men in the middle and,</span></td><td class="lineno" valign="top"></td></tr> 1210 1182 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> thus</span> represent an opportunity for man-in-the-middle attacks.</td><td> </td><td class="rblock"><span class="insert"> thus,</span> represent an opportunity for man-in-the-middle attacks.</td><td class="lineno" valign="top"></td></tr> … … 1231 1203 <tr><td class="lineno" valign="top"></td><td class="left"> such information is detected by the protocol to be incomplete,</td><td> </td><td class="right"> such information is detected by the protocol to be incomplete,</td><td class="lineno" valign="top"></td></tr> 1232 1204 <tr><td class="lineno" valign="top"></td><td class="left"> expired, or corrupted during transfer. Such mechanisms might be</td><td> </td><td class="right"> expired, or corrupted during transfer. Such mechanisms might be</td><td class="lineno" valign="top"></td></tr> 1233 <tr><td><a name="diff006 9" /></td></tr>1205 <tr><td><a name="diff0067" /></td></tr> 1234 1206 <tr><td class="lineno" valign="top"></td><td class="lblock"> selectively enabled via user<span class="delete"> </span>agent extensions or the presence of</td><td> </td><td class="rblock"> selectively enabled via user<span class="insert">-</span>agent extensions or the presence of</td><td class="lineno" valign="top"></td></tr> 1235 1207 <tr><td class="lineno" valign="top"></td><td class="left"> message integrity metadata in a response. At a minimum, user agents</td><td> </td><td class="right"> message integrity metadata in a response. At a minimum, user agents</td><td class="lineno" valign="top"></td></tr> … … 1255 1227 <tr><td class="lineno" valign="top"></td><td class="left">11.1. Normative References</td><td> </td><td class="right">11.1. Normative References</td><td class="lineno" valign="top"></td></tr> 1256 1228 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1257 <tr><td><a name="diff00 70" /></td></tr>1229 <tr><td><a name="diff0068" /></td></tr> 1258 1230 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">[RFC0793] Postel, J., "Transmission Control Protocol", STD 7,</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> 1259 1231 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> RFC 793, September 1981.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> … … 1281 1253 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td> </td><td class="right"> [RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td class="lineno" valign="top"></td></tr> 1282 1254 <tr><td class="lineno" valign="top"></td><td class="left"> Transfer Protocol (HTTP/1.1): Semantics and Content",</td><td> </td><td class="right"> Transfer Protocol (HTTP/1.1): Semantics and Content",</td><td class="lineno" valign="top"></td></tr> 1283 <tr><td><a name="diff00 71" /></td></tr>1255 <tr><td><a name="diff0069" /></td></tr> 1284 1256 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p2-semantics-latest (work in</span></td><td> </td><td class="rblock"> <span class="insert">RFC 7231,</span> May 2014.</td><td class="lineno" valign="top"></td></tr> 1285 1257 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> progress),</span> May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> … … 1287 1259 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7232] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td> </td><td class="right"> [RFC7232] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td class="lineno" valign="top"></td></tr> 1288 1260 <tr><td class="lineno" valign="top"></td><td class="left"> Transfer Protocol (HTTP/1.1): Conditional Requests",</td><td> </td><td class="right"> Transfer Protocol (HTTP/1.1): Conditional Requests",</td><td class="lineno" valign="top"></td></tr> 1289 <tr><td><a name="diff007 2" /></td></tr>1261 <tr><td><a name="diff0070" /></td></tr> 1290 1262 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p4-conditional-latest (work in</span></td><td> </td><td class="rblock"> <span class="insert">RFC 7232,</span> May 2014.</td><td class="lineno" valign="top"></td></tr> 1291 1263 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> progress),</span> May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> … … 1293 1265 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7233] Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td> </td><td class="right"> [RFC7233] Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td class="lineno" valign="top"></td></tr> 1294 1266 <tr><td class="lineno" valign="top"></td><td class="left"> "Hypertext Transfer Protocol (HTTP/1.1): Range</td><td> </td><td class="right"> "Hypertext Transfer Protocol (HTTP/1.1): Range</td><td class="lineno" valign="top"></td></tr> 1295 <tr><td><a name="diff007 3" /></td></tr>1267 <tr><td><a name="diff0071" /></td></tr> 1296 1268 <tr><td class="lineno" valign="top"></td><td class="lblock"> Requests", <span class="delete">draft-ietf-httpbis-p5-range-latest (work in</span></td><td> </td><td class="rblock"> Requests", <span class="insert">RFC 7233,</span> May 2014.</td><td class="lineno" valign="top"></td></tr> 1297 1269 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> progress),</span> May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> … … 1299 1271 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7234] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td> </td><td class="right"> [RFC7234] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td class="lineno" valign="top"></td></tr> 1300 1272 <tr><td class="lineno" valign="top"></td><td class="left"> Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td> </td><td class="right"> Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td class="lineno" valign="top"></td></tr> 1301 <tr><td><a name="diff007 4" /></td></tr>1273 <tr><td><a name="diff0072" /></td></tr> 1302 1274 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p6-cache-latest (work in progress),</span></td><td> </td><td class="rblock"> <span class="insert">RFC 7234,</span> May 2014.</td><td class="lineno" valign="top"></td></tr> 1303 1275 <tr><td class="lineno" valign="top"></td><td class="lblock"> May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> … … 1305 1277 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7235] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td> </td><td class="right"> [RFC7235] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td class="lineno" valign="top"></td></tr> 1306 1278 <tr><td class="lineno" valign="top"></td><td class="left"> Transfer Protocol (HTTP/1.1): Authentication",</td><td> </td><td class="right"> Transfer Protocol (HTTP/1.1): Authentication",</td><td class="lineno" valign="top"></td></tr> 1307 <tr><td><a name="diff007 5" /></td></tr>1279 <tr><td><a name="diff0073" /></td></tr> 1308 1280 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p7-auth-latest (work in progress),</span></td><td> </td><td class="rblock"> <span class="insert">RFC 7235,</span> May 2014.</td><td class="lineno" valign="top"></td></tr> 1309 1281 <tr><td class="lineno" valign="top"></td><td class="lblock"> May 2014.</td><td> </td><td class="rblock"> </td><td class="lineno" valign="top"></td></tr> … … 1332 1304 <tr><td class="lineno" valign="top"></td><td class="left"> effects of hierarchical proxies, caching, the need for persistent</td><td> </td><td class="right"> effects of hierarchical proxies, caching, the need for persistent</td><td class="lineno" valign="top"></td></tr> 1333 1305 <tr><td class="lineno" valign="top"></td><td class="left"> connections, or name-based virtual hosts. The proliferation of</td><td> </td><td class="right"> connections, or name-based virtual hosts. The proliferation of</td><td class="lineno" valign="top"></td></tr> 1334 <tr><td><a name="diff007 6" /></td></tr>1306 <tr><td><a name="diff0074" /></td></tr> 1335 1307 <tr><td class="lineno" valign="top"></td><td class="lblock"> incompletely<span class="delete">-</span>implemented applications calling themselves "HTTP/1.0"</td><td> </td><td class="rblock"> incompletely<span class="insert"> </span>implemented applications calling themselves "HTTP/1.0"</td><td class="lineno" valign="top"></td></tr> 1336 1308 <tr><td class="lineno" valign="top"></td><td class="left"> further necessitated a protocol version change in order for two</td><td> </td><td class="right"> further necessitated a protocol version change in order for two</td><td class="lineno" valign="top"></td></tr> … … 1356 1328 <tr><td class="lineno" valign="top"></td><td class="left"> and HTTP/1.1.</td><td> </td><td class="right"> and HTTP/1.1.</td><td class="lineno" valign="top"></td></tr> 1357 1329 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1358 <tr><td><a name="diff007 7" /></td></tr>1330 <tr><td><a name="diff0075" /></td></tr> 1359 1331 <tr><td class="lineno" valign="top"></td><td class="lblock">A.1.1. Multi<span class="delete">-</span>homed Web Servers</td><td> </td><td class="rblock">A.1.1. Multihomed Web Servers</td><td class="lineno" valign="top"></td></tr> 1360 1332 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1380 1352 <tr><td class="lineno" valign="top"></td><td class="left">A.2. Changes from RFC 2616</td><td> </td><td class="right">A.2. Changes from RFC 2616</td><td class="lineno" valign="top"></td></tr> 1381 1353 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1382 <tr><td><a name="diff007 8" /></td></tr>1354 <tr><td><a name="diff0076" /></td></tr> 1383 1355 <tr><td class="lineno" valign="top"></td><td class="lblock"> HTTP's approach to error handling has been explained<span class="delete">. (Section 2.5)</span></td><td> </td><td class="rblock"> HTTP's approach to error handling has been explained<span class="insert"> (Section 2.5).</span></td><td class="lineno" valign="top"></td></tr> 1384 1356 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1385 <tr><td><a name="diff007 9" /></td></tr>1357 <tr><td><a name="diff0077" /></td></tr> 1386 1358 <tr><td class="lineno" valign="top"></td><td class="lblock"> The HTTP-version ABNF production has been clarified to be case<span class="delete">-</span></td><td> </td><td class="rblock"> The HTTP-version ABNF production has been clarified to be case</td><td class="lineno" valign="top"></td></tr> 1387 1359 <tr><td class="lineno" valign="top"></td><td class="left"> sensitive. Additionally, version numbers have been restricted to</td><td> </td><td class="right"> sensitive. Additionally, version numbers have been restricted to</td><td class="lineno" valign="top"></td></tr> 1388 1360 <tr><td class="lineno" valign="top"></td><td class="left"> single digits, due to the fact that implementations are known to</td><td> </td><td class="right"> single digits, due to the fact that implementations are known to</td><td class="lineno" valign="top"></td></tr> 1389 <tr><td><a name="diff00 80" /></td></tr>1361 <tr><td><a name="diff0078" /></td></tr> 1390 1362 <tr><td class="lineno" valign="top"></td><td class="lblock"> handle multi-digit version numbers incorrectly<span class="delete">. (Section 2.6)</span></td><td> </td><td class="rblock"> handle multi-digit version numbers incorrectly<span class="insert"> (Section 2.6).</span></td><td class="lineno" valign="top"></td></tr> 1391 1363 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1392 1364 <tr><td class="lineno" valign="top"></td><td class="left"> Userinfo (i.e., username and password) are now disallowed in HTTP and</td><td> </td><td class="right"> Userinfo (i.e., username and password) are now disallowed in HTTP and</td><td class="lineno" valign="top"></td></tr> 1393 1365 <tr><td class="lineno" valign="top"></td><td class="left"> HTTPS URIs, because of security issues related to their transmission</td><td> </td><td class="right"> HTTPS URIs, because of security issues related to their transmission</td><td class="lineno" valign="top"></td></tr> 1394 <tr><td><a name="diff00 81" /></td></tr>1366 <tr><td><a name="diff0079" /></td></tr> 1395 1367 <tr><td class="lineno" valign="top"></td><td class="lblock"> on the wire<span class="delete">. (Section 2.7.1)</span></td><td> </td><td class="rblock"> on the wire<span class="insert"> (Section 2.7.1).</span></td><td class="lineno" valign="top"></td></tr> 1396 1368 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1397 1369 <tr><td class="lineno" valign="top"></td><td class="left"> The HTTPS URI scheme is now defined by this specification;</td><td> </td><td class="right"> The HTTPS URI scheme is now defined by this specification;</td><td class="lineno" valign="top"></td></tr> 1398 <tr><td><a name="diff008 2" /></td></tr>1370 <tr><td><a name="diff0080" /></td></tr> 1399 1371 <tr><td class="lineno" valign="top"></td><td class="lblock"> previously, it was <span class="delete">done</span> in Section 2.4 of [RFC2818]. Furthermore, it</td><td> </td><td class="rblock"> previously, it was <span class="insert">defined</span> in Section 2.4 of [RFC2818]. Furthermore,</td><td class="lineno" valign="top"></td></tr> 1400 1372 <tr><td class="lineno" valign="top"></td><td class="lblock"> implies end-to-end <span class="delete">security.</span> (Section <span class="delete">2.7.2)</span></td><td> </td><td class="rblock"> it implies end-to-end <span class="insert">security</span> (Section <span class="insert">2.7.2).</span></td><td class="lineno" valign="top"></td></tr> … … 1404 1376 <tr><td class="lineno" valign="top"></td><td class="left"> fundamentally a message-oriented protocol. Minimum supported sizes</td><td> </td><td class="right"> fundamentally a message-oriented protocol. Minimum supported sizes</td><td class="lineno" valign="top"></td></tr> 1405 1377 <tr><td class="lineno" valign="top"></td><td class="left"> for various protocol elements have been suggested, to improve</td><td> </td><td class="right"> for various protocol elements have been suggested, to improve</td><td class="lineno" valign="top"></td></tr> 1406 <tr><td><a name="diff008 3" /></td></tr>1378 <tr><td><a name="diff0081" /></td></tr> 1407 1379 <tr><td class="lineno" valign="top"></td><td class="lblock"> interoperability<span class="delete">. (Section 3)</span></td><td> </td><td class="rblock"> interoperability<span class="insert"> (Section 3).</span></td><td class="lineno" valign="top"></td></tr> 1408 1380 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1409 1381 <tr><td class="lineno" valign="top"></td><td class="left"> Invalid whitespace around field-names is now required to be rejected,</td><td> </td><td class="right"> Invalid whitespace around field-names is now required to be rejected,</td><td class="lineno" valign="top"></td></tr> 1410 1382 <tr><td class="lineno" valign="top"></td><td class="left"> because accepting it represents a security vulnerability. The ABNF</td><td> </td><td class="right"> because accepting it represents a security vulnerability. The ABNF</td><td class="lineno" valign="top"></td></tr> 1411 <tr><td><a name="diff008 4" /></td></tr>1383 <tr><td><a name="diff0082" /></td></tr> 1412 1384 <tr><td class="lineno" valign="top"></td><td class="lblock"> productions defining header fields now only list the field <span class="delete">value.</span></td><td> </td><td class="rblock"> productions defining header fields now only list the field <span class="insert">value</span></td><td class="lineno" valign="top"></td></tr> 1413 1385 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">3.2)</span></td><td> </td><td class="rblock"> (Section <span class="insert">3.2).</span></td><td class="lineno" valign="top"></td></tr> … … 1415 1387 <tr><td class="lineno" valign="top"></td><td class="left"> Rules about implicit linear whitespace between certain grammar</td><td> </td><td class="right"> Rules about implicit linear whitespace between certain grammar</td><td class="lineno" valign="top"></td></tr> 1416 1388 <tr><td class="lineno" valign="top"></td><td class="left"> productions have been removed; now whitespace is only allowed where</td><td> </td><td class="right"> productions have been removed; now whitespace is only allowed where</td><td class="lineno" valign="top"></td></tr> 1417 <tr><td><a name="diff008 5" /></td></tr>1389 <tr><td><a name="diff0083" /></td></tr> 1418 1390 <tr><td class="lineno" valign="top"></td><td class="lblock"> specifically defined in the ABNF<span class="delete">. (Section 3.2.3)</span></td><td> </td><td class="rblock"> specifically defined in the ABNF<span class="insert"> (Section 3.2.3).</span></td><td class="lineno" valign="top"></td></tr> 1419 1391 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1420 1392 <tr><td class="lineno" valign="top"></td><td class="left"> Header fields that span multiple lines ("line folding") are</td><td> </td><td class="right"> Header fields that span multiple lines ("line folding") are</td><td class="lineno" valign="top"></td></tr> 1421 <tr><td><a name="diff008 6" /></td></tr>1393 <tr><td><a name="diff0084" /></td></tr> 1422 1394 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">deprecated.</span> (Section <span class="delete">3.2.4)</span></td><td> </td><td class="rblock"> <span class="insert">deprecated</span> (Section <span class="insert">3.2.4).</span></td><td class="lineno" valign="top"></td></tr> 1423 1395 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"> </td><td class="lineno" valign="top"></td></tr> … … 1425 1397 <tr><td class="lineno" valign="top"></td><td class="left"> and handling of backslash-escaping in them has been clarified. The</td><td> </td><td class="right"> and handling of backslash-escaping in them has been clarified. The</td><td class="lineno" valign="top"></td></tr> 1426 1398 <tr><td class="lineno" valign="top"></td><td class="left"> quoted-pair rule no longer allows escaping control characters other</td><td> </td><td class="right"> quoted-pair rule no longer allows escaping control characters other</td><td class="lineno" valign="top"></td></tr> 1427 <tr><td><a name="diff008 7" /></td></tr>1399 <tr><td><a name="diff0085" /></td></tr> 1428 1400 <tr><td class="lineno" valign="top"></td><td class="lblock"> than HTAB. <span class="delete">Non-ASCII</span> content in header fields and the reason phrase</td><td> </td><td class="rblock"> than HTAB. <span class="insert">Non-US-ASCII</span> content in header fields and the reason</td><td class="lineno" valign="top"></td></tr> 1429 1401 <tr><td class="lineno" valign="top"></td><td class="lblock"> has been obsoleted and made opaque (the TEXT rule was <span class="delete">removed).</span></td><td> </td><td class="rblock"> phrase has been obsoleted and made opaque (the TEXT rule was <span class="insert">removed)</span></td><td class="lineno" valign="top"></td></tr> … … 1431 1403 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1432 1404 <tr><td class="lineno" valign="top"></td><td class="left"> Bogus "Content-Length" header fields are now required to be handled</td><td> </td><td class="right"> Bogus "Content-Length" header fields are now required to be handled</td><td class="lineno" valign="top"></td></tr> 1433 <tr><td><a name="diff008 8" /></td></tr>1405 <tr><td><a name="diff0086" /></td></tr> 1434 1406 <tr><td class="lineno" valign="top"></td><td class="lblock"> as errors by recipients<span class="delete">. (Section 3.3.2)</span></td><td> </td><td class="rblock"> as errors by recipients<span class="insert"> (Section 3.3.2).</span></td><td class="lineno" valign="top"></td></tr> 1435 1407 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1439 1411 <tr><td class="lineno" valign="top"></td><td class="left"> elements cannot define such special cases. CONNECT is a new, special</td><td> </td><td class="right"> elements cannot define such special cases. CONNECT is a new, special</td><td class="lineno" valign="top"></td></tr> 1440 1412 <tr><td class="lineno" valign="top"></td><td class="left"> case in determining message body length. "multipart/byteranges" is no</td><td> </td><td class="right"> case in determining message body length. "multipart/byteranges" is no</td><td class="lineno" valign="top"></td></tr> 1441 <tr><td><a name="diff008 9" /></td></tr>1413 <tr><td><a name="diff0087" /></td></tr> 1442 1414 <tr><td class="lineno" valign="top"></td><td class="lblock"> longer a way of determining message body length <span class="delete">detection.</span></td><td> </td><td class="rblock"> longer a way of determining message body length <span class="insert">detection</span></td><td class="lineno" valign="top"></td></tr> 1443 1415 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">3.3.3)</span></td><td> </td><td class="rblock"> (Section <span class="insert">3.3.3).</span></td><td class="lineno" valign="top"></td></tr> 1444 1416 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1445 <tr><td><a name="diff00 90" /></td></tr>1417 <tr><td><a name="diff0088" /></td></tr> 1446 1418 <tr><td class="lineno" valign="top"></td><td class="lblock"> The "identity" transfer coding token has been <span class="delete">removed.</span> (Sections 3.3</td><td> </td><td class="rblock"> The "identity" transfer coding token has been <span class="insert">removed</span> (Sections 3.3</td><td class="lineno" valign="top"></td></tr> 1447 1419 <tr><td class="lineno" valign="top"></td><td class="lblock"> and <span class="delete">4)</span></td><td> </td><td class="rblock"> and <span class="insert">4).</span></td><td class="lineno" valign="top"></td></tr> 1448 1420 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1449 1421 <tr><td class="lineno" valign="top"></td><td class="left"> Chunk length does not include the count of the octets in the chunk</td><td> </td><td class="right"> Chunk length does not include the count of the octets in the chunk</td><td class="lineno" valign="top"></td></tr> 1450 <tr><td><a name="diff00 91" /></td></tr>1422 <tr><td><a name="diff0089" /></td></tr> 1451 1423 <tr><td class="lineno" valign="top"></td><td class="lblock"> header and trailer. Line folding in chunk extensions is <span class="delete">disallowed.</span></td><td> </td><td class="rblock"> header and trailer. Line folding in chunk extensions is <span class="insert">disallowed</span></td><td class="lineno" valign="top"></td></tr> 1452 1424 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">4.1)</span></td><td> </td><td class="rblock"> (Section <span class="insert">4.1).</span></td><td class="lineno" valign="top"></td></tr> 1453 1425 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1454 <tr><td><a name="diff009 2" /></td></tr>1426 <tr><td><a name="diff0090" /></td></tr> 1455 1427 <tr><td class="lineno" valign="top"></td><td class="lblock"> The meaning of the "deflate" content coding has been <span class="delete">clarified.</span></td><td> </td><td class="rblock"> The meaning of the "deflate" content coding has been <span class="insert">clarified</span></td><td class="lineno" valign="top"></td></tr> 1456 1428 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">4.2.2)</span></td><td> </td><td class="rblock"> (Section <span class="insert">4.2.2).</span></td><td class="lineno" valign="top"></td></tr> … … 1458 1430 <tr><td class="lineno" valign="top"></td><td class="left"> The segment + query components of RFC 3986 have been used to define</td><td> </td><td class="right"> The segment + query components of RFC 3986 have been used to define</td><td class="lineno" valign="top"></td></tr> 1459 1431 <tr><td class="lineno" valign="top"></td><td class="left"> the request-target, instead of abs_path from RFC 1808. The asterisk-</td><td> </td><td class="right"> the request-target, instead of abs_path from RFC 1808. The asterisk-</td><td class="lineno" valign="top"></td></tr> 1460 <tr><td><a name="diff009 3" /></td></tr>1432 <tr><td><a name="diff0091" /></td></tr> 1461 1433 <tr><td class="lineno" valign="top"></td><td class="lblock"> form of the request-target is only allowed with the OPTIONS <span class="delete">method.</span></td><td> </td><td class="rblock"> form of the request-target is only allowed with the OPTIONS <span class="insert">method</span></td><td class="lineno" valign="top"></td></tr> 1462 1434 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">5.3)</span></td><td> </td><td class="rblock"> (Section <span class="insert">5.3).</span></td><td class="lineno" valign="top"></td></tr> 1463 1435 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1464 <tr><td><a name="diff009 4" /></td></tr>1436 <tr><td><a name="diff0092" /></td></tr> 1465 1437 <tr><td class="lineno" valign="top"></td><td class="lblock"> The term "Effective Request URI" has been introduced<span class="delete">. (Section 5.5)</span></td><td> </td><td class="rblock"> The term "Effective Request URI" has been introduced<span class="insert"> (Section 5.5).</span></td><td class="lineno" valign="top"></td></tr> 1466 1438 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1467 <tr><td><a name="diff009 5" /></td></tr>1439 <tr><td><a name="diff0093" /></td></tr> 1468 1440 <tr><td class="lineno" valign="top"></td><td class="lblock"> Gateways do not need to generate Via header fields <span class="delete">anymore.</span></td><td> </td><td class="rblock"> Gateways do not need to generate Via header fields <span class="insert">anymore</span></td><td class="lineno" valign="top"></td></tr> 1469 1441 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">5.7.1)</span></td><td> </td><td class="rblock"> (Section <span class="insert">5.7.1).</span></td><td class="lineno" valign="top"></td></tr> … … 1472 1444 <tr><td class="lineno" valign="top"></td><td class="left"> clarified. Also, "hop-by-hop" header fields are required to appear</td><td> </td><td class="right"> clarified. Also, "hop-by-hop" header fields are required to appear</td><td class="lineno" valign="top"></td></tr> 1473 1445 <tr><td class="lineno" valign="top"></td><td class="left"> in the Connection header field; just because they're defined as hop-</td><td> </td><td class="right"> in the Connection header field; just because they're defined as hop-</td><td class="lineno" valign="top"></td></tr> 1474 <tr><td><a name="diff009 6" /></td></tr>1446 <tr><td><a name="diff0094" /></td></tr> 1475 1447 <tr><td class="lineno" valign="top"></td><td class="lblock"> by-hop in this specification doesn't exempt them<span class="delete">. (Section 6.1)</span></td><td> </td><td class="rblock"> by-hop in this specification doesn't exempt them<span class="insert"> (Section 6.1).</span></td><td class="lineno" valign="top"></td></tr> 1476 1448 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1480 1452 <tr><td class="lineno" valign="top"></td><td class="left"> the server prematurely closes the connection has been removed. Also,</td><td> </td><td class="right"> the server prematurely closes the connection has been removed. Also,</td><td class="lineno" valign="top"></td></tr> 1481 1453 <tr><td class="lineno" valign="top"></td><td class="left"> some extraneous requirements about when servers are allowed to close</td><td> </td><td class="right"> some extraneous requirements about when servers are allowed to close</td><td class="lineno" valign="top"></td></tr> 1482 <tr><td><a name="diff009 7" /></td></tr>1454 <tr><td><a name="diff0095" /></td></tr> 1483 1455 <tr><td class="lineno" valign="top"></td><td class="lblock"> connections prematurely have been removed<span class="delete">. (Section 6.3)</span></td><td> </td><td class="rblock"> connections prematurely have been removed<span class="insert"> (Section 6.3).</span></td><td class="lineno" valign="top"></td></tr> 1484 1456 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1485 1457 <tr><td class="lineno" valign="top"></td><td class="left"> The semantics of the Upgrade header field is now defined in responses</td><td> </td><td class="right"> The semantics of the Upgrade header field is now defined in responses</td><td class="lineno" valign="top"></td></tr> 1486 1458 <tr><td class="lineno" valign="top"></td><td class="left"> other than 101 (this was incorporated from [RFC2817]). Furthermore,</td><td> </td><td class="right"> other than 101 (this was incorporated from [RFC2817]). Furthermore,</td><td class="lineno" valign="top"></td></tr> 1459 <tr><td><a name="diff0096" /></td></tr> 1460 <tr><td class="lineno" valign="top"></td><td class="lblock"> the ordering in the field value is now significant<span class="delete">. (Section 6.7)</span></td><td> </td><td class="rblock"> the ordering in the field value is now significant<span class="insert"> (Section 6.7).</span></td><td class="lineno" valign="top"></td></tr> 1461 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1462 <tr><td class="lineno" valign="top"></td><td class="left"> Empty list elements in list productions (e.g., a list header field</td><td> </td><td class="right"> Empty list elements in list productions (e.g., a list header field</td><td class="lineno" valign="top"></td></tr> 1463 <tr><td><a name="diff0097" /></td></tr> 1464 <tr><td class="lineno" valign="top"></td><td class="lblock"> containing ", ,") have been deprecated<span class="delete">. (Section 7)</span></td><td> </td><td class="rblock"> containing ", ,") have been deprecated<span class="insert"> (Section 7).</span></td><td class="lineno" valign="top"></td></tr> 1465 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1466 <tr><td class="lineno" valign="top"></td><td class="left"> Registration of Transfer Codings now requires IETF Review</td><td> </td><td class="right"> Registration of Transfer Codings now requires IETF Review</td><td class="lineno" valign="top"></td></tr> 1487 1467 <tr><td><a name="diff0098" /></td></tr> 1488 <tr><td class="lineno" valign="top"></td><td class="lblock"> the ordering in the field value is now significant<span class="delete">. (Section 6.7)</span></td><td> </td><td class="rblock"> the ordering in the field value is now significant<span class="insert"> (Section 6.7).</span></td><td class="lineno" valign="top"></td></tr> 1489 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1490 <tr><td class="lineno" valign="top"></td><td class="left"> Empty list elements in list productions (e.g., a list header field</td><td> </td><td class="right"> Empty list elements in list productions (e.g., a list header field</td><td class="lineno" valign="top"></td></tr> 1468 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section 8.4)</td><td> </td><td class="rblock"> (Section 8.4)<span class="insert">.</span></td><td class="lineno" valign="top"></td></tr> 1469 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1491 1470 <tr><td><a name="diff0099" /></td></tr> 1492 <tr><td class="lineno" valign="top"></td><td class="lblock"> containing ", ,") have been deprecated<span class="delete">. (Section 7)</span></td><td> </td><td class="rblock"> containing ", ,") have been deprecated<span class="insert"> (Section 7).</span></td><td class="lineno" valign="top"></td></tr>1493 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1494 <tr><td class="lineno" valign="top"></td><td class="left"> Registration of Transfer Codings now requires IETF Review</td><td> </td><td class="right"> Registration of Transfer Codings now requires IETF Review</td><td class="lineno" valign="top"></td></tr>1495 <tr><td><a name="diff0100" /></td></tr>1496 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section 8.4)</td><td> </td><td class="rblock"> (Section 8.4)<span class="insert">.</span></td><td class="lineno" valign="top"></td></tr>1497 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1498 <tr><td><a name="diff0101" /></td></tr>1499 1471 <tr><td class="lineno" valign="top"></td><td class="lblock"> This specification now defines the Upgrade <span class="delete">Token Registry,</span> previously</td><td> </td><td class="rblock"> This specification now defines the <span class="insert">"HTTP</span> Upgrade <span class="insert">Tokens" registry,</span></td><td class="lineno" valign="top"></td></tr> 1500 1472 <tr><td class="lineno" valign="top"></td><td class="lblock"> defined in Section 7.2 of <span class="delete">[RFC2817].</span> (Section <span class="delete">8.6)</span></td><td> </td><td class="rblock"> previously defined in Section 7.2 of <span class="insert">[RFC2817]</span> (Section <span class="insert">8.6).</span></td><td class="lineno" valign="top"></td></tr> 1501 1473 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1502 <tr><td><a name="diff010 2" /></td></tr>1474 <tr><td><a name="diff0100" /></td></tr> 1503 1475 <tr><td class="lineno" valign="top"></td><td class="lblock"> The expectation to support HTTP/0.9 requests has been <span class="delete">removed.</span></td><td> </td><td class="rblock"> The expectation to support HTTP/0.9 requests has been <span class="insert">removed</span></td><td class="lineno" valign="top"></td></tr> 1504 1476 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Appendix <span class="delete">A)</span></td><td> </td><td class="rblock"> (Appendix <span class="insert">A).</span></td><td class="lineno" valign="top"></td></tr> … … 1506 1478 <tr><td class="lineno" valign="top"></td><td class="left"> Issues with the Keep-Alive and Proxy-Connection header fields in</td><td> </td><td class="right"> Issues with the Keep-Alive and Proxy-Connection header fields in</td><td class="lineno" valign="top"></td></tr> 1507 1479 <tr><td class="lineno" valign="top"></td><td class="left"> requests are pointed out, with use of the latter being discouraged</td><td> </td><td class="right"> requests are pointed out, with use of the latter being discouraged</td><td class="lineno" valign="top"></td></tr> 1508 <tr><td><a name="diff010 3" /></td></tr>1480 <tr><td><a name="diff0101" /></td></tr> 1509 1481 <tr><td class="lineno" valign="top"></td><td class="lblock"> altogether<span class="delete">. (Appendix A.1.2)</span></td><td> </td><td class="rblock"> altogether<span class="insert"> (Appendix A.1.2).</span></td><td class="lineno" valign="top"></td></tr> 1510 1482 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1530 1502 <tr><td class="lineno" valign="top"></td><td class="left"> deflate (Coding Format) 38</td><td> </td><td class="right"> deflate (Coding Format) 38</td><td class="lineno" valign="top"></td></tr> 1531 1503 <tr><td class="lineno" valign="top"></td><td class="left"> Delimiters 26</td><td> </td><td class="right"> Delimiters 26</td><td class="lineno" valign="top"></td></tr> 1532 <tr><td><a name="diff010 4" /></td></tr>1504 <tr><td><a name="diff0102" /></td></tr> 1533 1505 <tr><td class="lineno" valign="top"></td><td class="lblock"> downstream <span class="delete">9</span></td><td> </td><td class="rblock"> downstream <span class="insert">10</span></td><td class="lineno" valign="top"></td></tr> 1534 1506 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1554 1526 <tr><td class="lineno" valign="top"></td><td class="left"> HTAB 6</td><td> </td><td class="right"> HTAB 6</td><td class="lineno" valign="top"></td></tr> 1555 1527 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP-message 19</td><td> </td><td class="right"> HTTP-message 19</td><td class="lineno" valign="top"></td></tr> 1556 <tr><td><a name="diff010 5" /></td></tr>1528 <tr><td><a name="diff0103" /></td></tr> 1557 1529 <tr><td class="lineno" valign="top"></td><td class="lblock"> HTTP-name 1<span class="delete">3</span></td><td> </td><td class="rblock"> HTTP-name 1<span class="insert">4</span></td><td class="lineno" valign="top"></td></tr> 1558 1530 <tr><td class="lineno" valign="top"></td><td class="left"> http-URI 16</td><td> </td><td class="right"> http-URI 16</td><td class="lineno" valign="top"></td></tr> 1559 <tr><td><a name="diff010 6" /></td></tr>1531 <tr><td><a name="diff0104" /></td></tr> 1560 1532 <tr><td class="lineno" valign="top"></td><td class="lblock"> HTTP-version 1<span class="delete">3</span></td><td> </td><td class="rblock"> HTTP-version 1<span class="insert">4</span></td><td class="lineno" valign="top"></td></tr> 1561 1533 <tr><td class="lineno" valign="top"></td><td class="left"> https-URI 18</td><td> </td><td class="right"> https-URI 18</td><td class="lineno" valign="top"></td></tr> … … 1581 1553 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1582 1554 <tr><td class="lineno" valign="top"></td><td class="left"> I</td><td> </td><td class="right"> I</td><td class="lineno" valign="top"></td></tr> 1583 <tr><td><a name="diff010 7" /></td></tr>1555 <tr><td><a name="diff0105" /></td></tr> 1584 1556 <tr><td class="lineno" valign="top"></td><td class="lblock"> inbound <span class="delete">9</span></td><td> </td><td class="rblock"> inbound <span class="insert">10</span></td><td class="lineno" valign="top"></td></tr> 1585 1557 <tr><td class="lineno" valign="top"></td><td class="left"> interception proxy 11</td><td> </td><td class="right"> interception proxy 11</td><td class="lineno" valign="top"></td></tr> … … 1600 1572 <tr><td class="lineno" valign="top"></td><td class="left"> origin server 7</td><td> </td><td class="right"> origin server 7</td><td class="lineno" valign="top"></td></tr> 1601 1573 <tr><td class="lineno" valign="top"></td><td class="left"> origin-form (of request-target) 41</td><td> </td><td class="right"> origin-form (of request-target) 41</td><td class="lineno" valign="top"></td></tr> 1602 <tr><td><a name="diff010 8" /></td></tr>1574 <tr><td><a name="diff0106" /></td></tr> 1603 1575 <tr><td class="lineno" valign="top"></td><td class="lblock"> outbound <span class="delete">9</span></td><td> </td><td class="rblock"> outbound <span class="insert">10</span></td><td class="lineno" valign="top"></td></tr> 1604 1576 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1624 1596 <tr><td class="lineno" valign="top"></td><td class="left"> U</td><td> </td><td class="right"> U</td><td class="lineno" valign="top"></td></tr> 1625 1597 <tr><td class="lineno" valign="top"></td><td class="left"> Upgrade header field 56</td><td> </td><td class="right"> Upgrade header field 56</td><td class="lineno" valign="top"></td></tr> 1626 <tr><td><a name="diff010 9" /></td></tr>1598 <tr><td><a name="diff0107" /></td></tr> 1627 1599 <tr><td class="lineno" valign="top"></td><td class="lblock"> upstream <span class="delete">9</span></td><td> </td><td class="rblock"> upstream <span class="insert">10</span></td><td class="lineno" valign="top"></td></tr> 1628 1600 <tr><td class="lineno" valign="top"></td><td class="left"> URI scheme</td><td> </td><td class="right"> URI scheme</td><td class="lineno" valign="top"></td></tr> … … 1638 1610 1639 1611 <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr> 1640 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 10 9change blocks. </a></th></tr>1641 <tr class="stats"><td></td><th><i>18 4 lines changed or deleted</i></th><th><i> </i></th><th><i>161lines changed or added</i></th><td></td></tr>1612 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 107 change blocks. </a></th></tr> 1613 <tr class="stats"><td></td><th><i>180 lines changed or deleted</i></th><th><i> </i></th><th><i>157 lines changed or added</i></th><td></td></tr> 1642 1614 <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.38. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr> 1643 1615 </table> -
draft-ietf-httpbis/latest/auth48/rfc7231.abdiff.txt
r2647 r2651 1254 1254 OLD: 1255 1255 1256 The HTTP Method Registry defines the name space for the request1257 methodtoken (Section 4). The method registry will be created and1256 The HTTP Method Registry defines the namespace for the request method 1257 token (Section 4). The method registry will be created and 1258 1258 maintained at (the suggested URI) 1259 1259 <http://www.iana.org/assignments/http-methods>. … … 1314 1314 OLD: 1315 1315 1316 The HTTP Status Code Registry defines the name 1316 The HTTP Status Code Registry defines the namespace for the response 1317 1317 status-code token (Section 6). The status code registry is 1318 1318 maintained at <http://www.iana.org/assignments/http-status-codes>. … … 1385 1385 OLD: 1386 1386 1387 The HTTP Content Coding Registry defines the name 1387 The HTTP Content Coding Registry defines the namespace for content 1388 1388 coding names (Section 4.2 of [RFC7230]). The content coding registry 1389 1389 is maintained at <http://www.iana.org/assignments/http-parameters>. … … 1410 1410 OLD: 1411 1411 1412 Values to be added to this name space require IETF Review (see1413 Section 4.1 of [RFC5226]), and MUST conform to the purpose of content1414 codingdefined in this section.1412 Values to be added to this namespace require IETF Review (see Section 1413 4.1 of [RFC5226]), and MUST conform to the purpose of content coding 1414 defined in this section. 1415 1415 1416 1416 NEW: -
draft-ietf-httpbis/latest/auth48/rfc7231.diff.html
r2647 r2651 1063 1063 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1064 1064 <tr><td><a name="diff0051" /></td></tr> 1065 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Method <span class="delete">Registry</span> defines the <span class="delete">name space</span> for the request</td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Method <span class="insert">Registry"</span> defines the</td><td class="lineno" valign="top"></td></tr>1066 <tr><td class="lineno" valign="top"></td><td class="lblock"> method token (Section 4). The <span class="delete">method registry will be</span> created and</td><td> </td><td class="rblock"> <span class="insert">namespace</span>for the request method token (Section 4). The <span class="insert">"HTTP Method</span></td><td class="lineno" valign="top"></td></tr>1065 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Method <span class="delete">Registry</span> defines the namespace for the request method</td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Method <span class="insert">Registry"</span> defines the</td><td class="lineno" valign="top"></td></tr> 1066 <tr><td class="lineno" valign="top"></td><td class="lblock"> token (Section 4). The <span class="delete">method registry will be</span> created and</td><td> </td><td class="rblock"> namespace for the request method token (Section 4). The <span class="insert">"HTTP Method</span></td><td class="lineno" valign="top"></td></tr> 1067 1067 <tr><td class="lineno" valign="top"></td><td class="lblock"> maintained at <span class="delete">(the suggested URI)</span></td><td> </td><td class="rblock"><span class="insert"> Registry" has been</span> created and <span class="insert">is now</span> maintained at</td><td class="lineno" valign="top"></td></tr> 1068 1068 <tr><td class="lineno" valign="top"></td><td class="left"> <http://www.iana.org/assignments/http-methods>.</td><td> </td><td class="right"> <http://www.iana.org/assignments/http-methods>.</td><td class="lineno" valign="top"></td></tr> … … 1076 1076 <tr><td class="lineno" valign="top"></td><td class="left"> o Safe ("yes" or "no", see Section 4.2.1)</td><td> </td><td class="right"> o Safe ("yes" or "no", see Section 4.2.1)</td><td class="lineno" valign="top"></td></tr> 1077 1077 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1078 <tr><td class="lineno" valign="top"></td><td class="left"> o Idempotent ("yes" or "no", see Section 4.2.2)</td><td> </td><td class="right"> o Idempotent ("yes" or "no", see Section 4.2.2)</td><td class="lineno" valign="top"></td></tr> 1079 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1080 <tr><td class="lineno" valign="top"></td><td class="left"> o Pointer to specification text</td><td> </td><td class="right"> o Pointer to specification text</td><td class="lineno" valign="top"></td></tr> 1081 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1082 <tr><td><a name="diff0052" /></td></tr> 1083 <tr><td class="lineno" valign="top"></td><td class="lblock"> Values to be added to this name<span class="delete"> </span>space require IETF Review (see</td><td> </td><td class="rblock"> Values to be added to this namespace require IETF Review (see</td><td class="lineno" valign="top"></td></tr> 1084 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC5226], Section 4.1).</td><td> </td><td class="right"> [RFC5226], Section 4.1).</td><td class="lineno" valign="top"></td></tr> 1085 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1086 <tr><td class="lineno" valign="top"></td><td class="left">8.1.2. Considerations for New Methods</td><td> </td><td class="right">8.1.2. Considerations for New Methods</td><td class="lineno" valign="top"></td></tr> 1087 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1088 <tr><td class="lineno" valign="top"></td><td class="left"> Standardized methods are generic; that is, they are potentially</td><td> </td><td class="right"> Standardized methods are generic; that is, they are potentially</td><td class="lineno" valign="top"></td></tr> 1089 <tr><td class="lineno" valign="top"></td><td class="left"> applicable to any resource, not just one particular media type, kind</td><td> </td><td class="right"> applicable to any resource, not just one particular media type, kind</td><td class="lineno" valign="top"></td></tr> 1090 <tr><td class="lineno" valign="top"></td><td class="left"> of resource, or application. As such, it is preferred that new</td><td> </td><td class="right"> of resource, or application. As such, it is preferred that new</td><td class="lineno" valign="top"></td></tr> 1091 <tr><td class="lineno" valign="top"></td><td class="left"> methods be registered in a document that isn't specific to a single</td><td> </td><td class="right"> methods be registered in a document that isn't specific to a single</td><td class="lineno" valign="top"></td></tr> 1092 <tr><td class="lineno" valign="top"></td><td class="left"> application or data format, since orthogonal technologies deserve</td><td> </td><td class="right"> application or data format, since orthogonal technologies deserve</td><td class="lineno" valign="top"></td></tr> 1093 <tr><td class="lineno" valign="top"></td><td class="left"> orthogonal specification.</td><td> </td><td class="right"> orthogonal specification.</td><td class="lineno" valign="top"></td></tr> 1078 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1079 <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 74, line 44</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 74, line 44</em></th><td></td></tr> 1094 1080 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1095 1081 <tr><td class="lineno" valign="top"></td><td class="left"> Since message parsing (Section 3.3 of [RFC7230]) needs to be</td><td> </td><td class="right"> Since message parsing (Section 3.3 of [RFC7230]) needs to be</td><td class="lineno" valign="top"></td></tr> … … 1102 1088 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1103 1089 <tr><td class="lineno" valign="top"></td><td class="left"> A new method definition needs to indicate whether it is safe</td><td> </td><td class="right"> A new method definition needs to indicate whether it is safe</td><td class="lineno" valign="top"></td></tr> 1104 <tr><td><a name="diff005 3" /></td></tr>1090 <tr><td><a name="diff0052" /></td></tr> 1105 1091 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section 4.2.1), idempotent (Section 4.2.2), cacheable</td><td> </td><td class="rblock"> (Section 4.2.1), idempotent (Section 4.2.2), <span class="insert">or</span> cacheable</td><td class="lineno" valign="top"></td></tr> 1106 1092 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">4.2.3),</span> what semantics are to be associated with the payload</td><td> </td><td class="rblock"> (Section <span class="insert">4.2.3). It needs to indicate</span> what semantics are to be</td><td class="lineno" valign="top"></td></tr> … … 1121 1107 <tr><td class="lineno" valign="top"></td><td class="left">8.1.3. Registrations</td><td> </td><td class="right">8.1.3. Registrations</td><td class="lineno" valign="top"></td></tr> 1122 1108 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1123 <tr><td><a name="diff005 4" /></td></tr>1109 <tr><td><a name="diff0053" /></td></tr> 1124 1110 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Method <span class="delete">Registry shall be</span> populated with the registrations</td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Method <span class="insert">Registry" has been</span></td><td class="lineno" valign="top"></td></tr> 1125 1111 <tr><td class="lineno" valign="top"></td><td class="lblock"> below:</td><td> </td><td class="rblock"> populated with the registrations below:</td><td class="lineno" valign="top"></td></tr> … … 1140 1126 <tr><td class="lineno" valign="top"></td><td class="left">8.2. Status Code Registry</td><td> </td><td class="right">8.2. Status Code Registry</td><td class="lineno" valign="top"></td></tr> 1141 1127 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1142 <tr><td><a name="diff005 5" /></td></tr>1143 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Status Code <span class="delete">Registry</span> defines the <span class="delete">name space</span>for the response</td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Status Code <span class="insert">Registry"</span> defines</td><td class="lineno" valign="top"></td></tr>1144 <tr><td class="lineno" valign="top"></td><td class="lblock"> status-code token (Section 6). The <span class="delete">status code</span> registry is</td><td> </td><td class="rblock"> the <span class="insert">namespace</span>for the response status-code token (Section 6). The</td><td class="lineno" valign="top"></td></tr>1128 <tr><td><a name="diff0054" /></td></tr> 1129 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Status Code <span class="delete">Registry</span> defines the namespace for the response</td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Status Code <span class="insert">Registry"</span> defines</td><td class="lineno" valign="top"></td></tr> 1130 <tr><td class="lineno" valign="top"></td><td class="lblock"> status-code token (Section 6). The <span class="delete">status code</span> registry is</td><td> </td><td class="rblock"> the namespace for the response status-code token (Section 6). The</td><td class="lineno" valign="top"></td></tr> 1145 1131 <tr><td class="lineno" valign="top"></td><td class="lblock"> maintained at <http://www.iana.org/assignments/http-status-codes>.</td><td> </td><td class="rblock"> <span class="insert">"HTTP Status Codes"</span> registry is maintained at</td><td class="lineno" valign="top"></td></tr> 1146 1132 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"> <http://www.iana.org/assignments/http-status-codes>.</td><td class="lineno" valign="top"></td></tr> … … 1155 1141 <tr><td class="lineno" valign="top"></td><td class="left"> o Status Code (3 digits)</td><td> </td><td class="right"> o Status Code (3 digits)</td><td class="lineno" valign="top"></td></tr> 1156 1142 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1157 <tr><td class="lineno" valign="top"></td><td class="left"> o Short Description</td><td> </td><td class="right"> o Short Description</td><td class="lineno" valign="top"></td></tr> 1158 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1159 <tr><td class="lineno" valign="top"></td><td class="left"> o Pointer to specification text</td><td> </td><td class="right"> o Pointer to specification text</td><td class="lineno" valign="top"></td></tr> 1160 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1161 <tr><td><a name="diff0056" /></td></tr> 1162 <tr><td class="lineno" valign="top"></td><td class="lblock"> Values to be added to the HTTP status code name<span class="delete"> </span>space require IETF</td><td> </td><td class="rblock"> Values to be added to the HTTP status code namespace require IETF</td><td class="lineno" valign="top"></td></tr> 1163 <tr><td class="lineno" valign="top"></td><td class="left"> Review (see [RFC5226], Section 4.1).</td><td> </td><td class="right"> Review (see [RFC5226], Section 4.1).</td><td class="lineno" valign="top"></td></tr> 1164 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1165 <tr><td class="lineno" valign="top"></td><td class="left">8.2.2. Considerations for New Status Codes</td><td> </td><td class="right">8.2.2. Considerations for New Status Codes</td><td class="lineno" valign="top"></td></tr> 1166 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1167 <tr><td class="lineno" valign="top"></td><td class="left"> When it is necessary to express semantics for a response that are not</td><td> </td><td class="right"> When it is necessary to express semantics for a response that are not</td><td class="lineno" valign="top"></td></tr> 1168 <tr><td class="lineno" valign="top"></td><td class="left"> defined by current status codes, a new status code can be registered.</td><td> </td><td class="right"> defined by current status codes, a new status code can be registered.</td><td class="lineno" valign="top"></td></tr> 1169 <tr><td class="lineno" valign="top"></td><td class="left"> Status codes are generic; they are potentially applicable to any</td><td> </td><td class="right"> Status codes are generic; they are potentially applicable to any</td><td class="lineno" valign="top"></td></tr> 1170 <tr><td class="lineno" valign="top"></td><td class="left"> resource, not just one particular media type, kind of resource, or</td><td> </td><td class="right"> resource, not just one particular media type, kind of resource, or</td><td class="lineno" valign="top"></td></tr> 1171 <tr><td class="lineno" valign="top"></td><td class="left"> application of HTTP. As such, it is preferred that new status codes</td><td> </td><td class="right"> application of HTTP. As such, it is preferred that new status codes</td><td class="lineno" valign="top"></td></tr> 1172 <tr><td class="lineno" valign="top"></td><td class="left"> be registered in a document that isn't specific to a single</td><td> </td><td class="right"> be registered in a document that isn't specific to a single</td><td class="lineno" valign="top"></td></tr> 1173 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1174 <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 76, line 49</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 76, line 49</em></th><td></td></tr> 1143 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1144 <tr bgcolor="gray" ><td></td><th><a name="part-l33" /><small>skipping to change at</small><em> page 76, line 49</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 76, line 49</em></th><td></td></tr> 1175 1145 <tr><td class="lineno" valign="top"></td><td class="left"> cached without explicit freshness information. Likewise, the</td><td> </td><td class="right"> cached without explicit freshness information. Likewise, the</td><td class="lineno" valign="top"></td></tr> 1176 1146 <tr><td class="lineno" valign="top"></td><td class="left"> definition of a status code can place constraints upon cache</td><td> </td><td class="right"> definition of a status code can place constraints upon cache</td><td class="lineno" valign="top"></td></tr> … … 1183 1153 <tr><td class="lineno" valign="top"></td><td class="left">8.2.3. Registrations</td><td> </td><td class="right">8.2.3. Registrations</td><td class="lineno" valign="top"></td></tr> 1184 1154 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1185 <tr><td><a name="diff005 7" /></td></tr>1155 <tr><td><a name="diff0055" /></td></tr> 1186 1156 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Status <span class="delete">Code Registry shall be</span> updated with the registrations</td><td> </td><td class="rblock"> The <span class="insert">"HTTP</span> Status <span class="insert">Codes" registry has been</span> updated with the</td><td class="lineno" valign="top"></td></tr> 1187 1157 <tr><td class="lineno" valign="top"></td><td class="lblock"> below:</td><td> </td><td class="rblock"> registrations below:</td><td class="lineno" valign="top"></td></tr> … … 1197 1167 <tr><td class="lineno" valign="top"></td><td class="left"> | 203 | Non-Authoritative Information | Section 6.3.4 |</td><td> </td><td class="right"> | 203 | Non-Authoritative Information | Section 6.3.4 |</td><td class="lineno" valign="top"></td></tr> 1198 1168 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1199 <tr bgcolor="gray" ><td></td><th><a name="part-l3 3" /><small>skipping to change at</small><em> page 77, line 48</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 77, line 48</em></th><td></td></tr>1169 <tr bgcolor="gray" ><td></td><th><a name="part-l34" /><small>skipping to change at</small><em> page 77, line 48</em></th><th> </th><th><a name="part-r34" /><small>skipping to change at</small><em> page 77, line 48</em></th><td></td></tr> 1200 1170 <tr><td class="lineno" valign="top"></td><td class="left"> | 500 | Internal Server Error | Section 6.6.1 |</td><td> </td><td class="right"> | 500 | Internal Server Error | Section 6.6.1 |</td><td class="lineno" valign="top"></td></tr> 1201 1171 <tr><td class="lineno" valign="top"></td><td class="left"> | 501 | Not Implemented | Section 6.6.2 |</td><td> </td><td class="right"> | 501 | Not Implemented | Section 6.6.2 |</td><td class="lineno" valign="top"></td></tr> … … 1208 1178 <tr><td class="lineno" valign="top"></td><td class="left">8.3. Header Field Registry</td><td> </td><td class="right">8.3. Header Field Registry</td><td class="lineno" valign="top"></td></tr> 1209 1179 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1210 <tr><td><a name="diff005 8" /></td></tr>1180 <tr><td><a name="diff0056" /></td></tr> 1211 1181 <tr><td class="lineno" valign="top"></td><td class="lblock"> HTTP header fields are registered within the <span class="delete">Message Header Field</span></td><td> </td><td class="rblock"> HTTP header fields are registered within the <span class="insert">"Message Headers"</span></td><td class="lineno" valign="top"></td></tr> 1212 1182 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> Registry</span> located at <span class="delete"><http://www.iana.org/assignments/message-headers/</span></td><td> </td><td class="rblock"><span class="insert"> registry</span> located at <span class="insert"><http://www.iana.org/assignments/message-headers></span></td><td class="lineno" valign="top"></td></tr> … … 1232 1202 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1233 1203 <tr><td class="lineno" valign="top"></td><td class="left"> New header field values typically have their syntax defined using</td><td> </td><td class="right"> New header field values typically have their syntax defined using</td><td class="lineno" valign="top"></td></tr> 1234 <tr><td><a name="diff005 9" /></td></tr>1204 <tr><td><a name="diff0057" /></td></tr> 1235 1205 <tr><td class="lineno" valign="top"></td><td class="lblock"> ABNF <span class="delete">([RFC5234]), using</span> the extension defined in Section 7 of</td><td> </td><td class="rblock"> ABNF <span class="insert">([RFC5234]) (implementing</span> the extension defined in Section 7 of</td><td class="lineno" valign="top"></td></tr> 1236 1206 <tr><td class="lineno" valign="top"></td><td class="lblock"> [RFC7230] as <span class="delete">necessary,</span> and are usually constrained to the range of</td><td> </td><td class="rblock"> [RFC7230] as <span class="insert">necessary),</span> and <span class="insert">they</span> are usually constrained to the</td><td class="lineno" valign="top"></td></tr> … … 1247 1217 <tr><td class="lineno" valign="top"></td><td class="left"> values, they need to be treated with care if they are allowed in the</td><td> </td><td class="right"> values, they need to be treated with care if they are allowed in the</td><td class="lineno" valign="top"></td></tr> 1248 1218 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1249 <tr bgcolor="gray" ><td></td><th><a name="part-l3 4" /><small>skipping to change at</small><em> page 80, line 15</em></th><th> </th><th><a name="part-r34" /><small>skipping to change at</small><em> page 80, line 15</em></th><td></td></tr>1219 <tr bgcolor="gray" ><td></td><th><a name="part-l35" /><small>skipping to change at</small><em> page 80, line 15</em></th><th> </th><th><a name="part-r35" /><small>skipping to change at</small><em> page 80, line 15</em></th><td></td></tr> 1250 1220 <tr><td class="lineno" valign="top"></td><td class="left"> o Whether the header field is useful or allowable in trailers (see</td><td> </td><td class="right"> o Whether the header field is useful or allowable in trailers (see</td><td class="lineno" valign="top"></td></tr> 1251 1221 <tr><td class="lineno" valign="top"></td><td class="left"> Section 4.1 of [RFC7230]).</td><td> </td><td class="right"> Section 4.1 of [RFC7230]).</td><td class="lineno" valign="top"></td></tr> … … 1258 1228 <tr><td class="lineno" valign="top"></td><td class="left">8.3.2. Registrations</td><td> </td><td class="right">8.3.2. Registrations</td><td class="lineno" valign="top"></td></tr> 1259 1229 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1260 <tr><td><a name="diff00 60" /></td></tr>1230 <tr><td><a name="diff0058" /></td></tr> 1261 1231 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">Message Header Field Registry shall be</span> updated with the following</td><td> </td><td class="rblock"> The <span class="insert">"Message Headers" registry has been</span> updated with the following</td><td class="lineno" valign="top"></td></tr> 1262 1232 <tr><td class="lineno" valign="top"></td><td class="left"> permanent registrations:</td><td> </td><td class="right"> permanent registrations:</td><td class="lineno" valign="top"></td></tr> … … 1271 1241 <tr><td class="lineno" valign="top"></td><td class="left"> | Allow | http | standard | Section 7.4.1 |</td><td> </td><td class="right"> | Allow | http | standard | Section 7.4.1 |</td><td class="lineno" valign="top"></td></tr> 1272 1242 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1273 <tr bgcolor="gray" ><td></td><th><a name="part-l3 5" /><small>skipping to change at</small><em> page 80, line 48</em></th><th> </th><th><a name="part-r35" /><small>skipping to change at</small><em> page 80, line 48</em></th><td></td></tr>1243 <tr bgcolor="gray" ><td></td><th><a name="part-l36" /><small>skipping to change at</small><em> page 80, line 48</em></th><th> </th><th><a name="part-r36" /><small>skipping to change at</small><em> page 80, line 48</em></th><td></td></tr> 1274 1244 <tr><td class="lineno" valign="top"></td><td class="left"> | Server | http | standard | Section 7.4.2 |</td><td> </td><td class="right"> | Server | http | standard | Section 7.4.2 |</td><td class="lineno" valign="top"></td></tr> 1275 1245 <tr><td class="lineno" valign="top"></td><td class="left"> | User-Agent | http | standard | Section 5.5.3 |</td><td> </td><td class="right"> | User-Agent | http | standard | Section 5.5.3 |</td><td class="lineno" valign="top"></td></tr> … … 1282 1252 <tr><td class="lineno" valign="top"></td><td class="left">8.4. Content Coding Registry</td><td> </td><td class="right">8.4. Content Coding Registry</td><td class="lineno" valign="top"></td></tr> 1283 1253 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1284 <tr><td><a name="diff00 61" /></td></tr>1285 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Content Coding <span class="delete">Registry</span> defines the <span class="delete">name space</span> for content</td><td> </td><td class="rblock"> The <span class="insert">"HTTP</span> Content Coding <span class="insert">Registry"</span> defines the <span class="insert">namespace</span>for content</td><td class="lineno" valign="top"></td></tr>1254 <tr><td><a name="diff0059" /></td></tr> 1255 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Content Coding <span class="delete">Registry</span> defines the namespace for content</td><td> </td><td class="rblock"> The <span class="insert">"HTTP</span> Content Coding <span class="insert">Registry"</span> defines the namespace for content</td><td class="lineno" valign="top"></td></tr> 1286 1256 <tr><td class="lineno" valign="top"></td><td class="lblock"> coding names (Section 4.2 of [RFC7230]). The <span class="delete">content coding registry</span></td><td> </td><td class="rblock"> coding names (Section 4.2 of [RFC7230]). The <span class="insert">"HTTP Content Coding</span></td><td class="lineno" valign="top"></td></tr> 1287 1257 <tr><td class="lineno" valign="top"></td><td class="lblock"> is maintained at <http://www.iana.org/assignments/http-parameters>.</td><td> </td><td class="rblock"><span class="insert"> Registry"</span> is maintained at</td><td class="lineno" valign="top"></td></tr> … … 1290 1260 <tr><td class="lineno" valign="top"></td><td class="left">8.4.1. Procedure</td><td> </td><td class="right">8.4.1. Procedure</td><td class="lineno" valign="top"></td></tr> 1291 1261 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1292 <tr><td><a name="diff006 2" /></td></tr>1262 <tr><td><a name="diff0060" /></td></tr> 1293 1263 <tr><td class="lineno" valign="top"></td><td class="lblock"> Content <span class="delete">C</span>oding registrations MUST include the following fields:</td><td> </td><td class="rblock"> Content <span class="insert">c</span>oding registrations MUST include the following fields:</td><td class="lineno" valign="top"></td></tr> 1294 1264 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1304 1274 <tr><td class="lineno" valign="top"></td><td class="left"> Section 4.2 of [RFC7230]).</td><td> </td><td class="right"> Section 4.2 of [RFC7230]).</td><td class="lineno" valign="top"></td></tr> 1305 1275 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1306 <tr><td ><a name="diff0063" /></td></tr>1307 <tr><td class="lineno" valign="top"></td><td class="lblock"> Values to be added to this <span class="delete">name space</span> require IETF Review (see</td><td> </td><td class="rblock"> Values to be added to this <span class="insert">namespace</span> require IETF Review (see Section</td><td class="lineno" valign="top"></td></tr>1308 <tr><td class="lineno" valign="top"></td><td class="lblock"> Section 4.1 of <span class="delete">[RFC5226]),</span> and MUST conform to the purpose of content</td><td> </td><td class="rblock"> 4.1 of <span class="insert">[RFC5226])</span>and MUST conform to the purpose of content coding</td><td class="lineno" valign="top"></td></tr>1309 <tr><td class="lineno" valign="top"></td><td class="l block"> coding defined in this section.</td><td> </td><td class="rblock"> defined in this section.</td><td class="lineno" valign="top"></td></tr>1276 <tr><td class="lineno" valign="top"></td><td class="left"> Values to be added to this namespace require IETF Review (see Section</td><td> </td><td class="right"> Values to be added to this namespace require IETF Review (see Section</td><td class="lineno" valign="top"></td></tr> 1277 <tr><td><a name="diff0061" /></td></tr> 1278 <tr><td class="lineno" valign="top"></td><td class="lblock"> 4.1 of [RFC5226])<span class="delete">,</span> and MUST conform to the purpose of content coding</td><td> </td><td class="rblock"> 4.1 of [RFC5226]) and MUST conform to the purpose of content coding</td><td class="lineno" valign="top"></td></tr> 1279 <tr><td class="lineno" valign="top"></td><td class="left"> defined in this section.</td><td> </td><td class="right"> defined in this section.</td><td class="lineno" valign="top"></td></tr> 1310 1280 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1311 1281 <tr><td class="lineno" valign="top"></td><td class="left">8.4.2. Registrations</td><td> </td><td class="right">8.4.2. Registrations</td><td class="lineno" valign="top"></td></tr> 1312 1282 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1313 <tr><td><a name="diff006 4" /></td></tr>1283 <tr><td><a name="diff0062" /></td></tr> 1314 1284 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP Content Codings Registry shall be</span> updated with the</td><td> </td><td class="rblock"> The <span class="insert">"HTTP Content Codings Registry" has been</span> updated with the</td><td class="lineno" valign="top"></td></tr> 1315 1285 <tr><td class="lineno" valign="top"></td><td class="left"> registrations below:</td><td> </td><td class="right"> registrations below:</td><td class="lineno" valign="top"></td></tr> … … 1332 1302 <tr><td class="lineno" valign="top"></td><td class="left"> The list of considerations below is not exhaustive. Most security</td><td> </td><td class="right"> The list of considerations below is not exhaustive. Most security</td><td class="lineno" valign="top"></td></tr> 1333 1303 <tr><td class="lineno" valign="top"></td><td class="left"> concerns related to HTTP semantics are about securing server-side</td><td> </td><td class="right"> concerns related to HTTP semantics are about securing server-side</td><td class="lineno" valign="top"></td></tr> 1334 <tr><td><a name="diff006 5" /></td></tr>1304 <tr><td><a name="diff0063" /></td></tr> 1335 1305 <tr><td class="lineno" valign="top"></td><td class="lblock"> applications (code behind the HTTP <span class="delete">interface),</span> securing <span class="delete">user agent</span></td><td> </td><td class="rblock"> applications (code behind the HTTP <span class="insert">interface) or</span> securing <span class="insert">user-agent</span></td><td class="lineno" valign="top"></td></tr> 1336 1306 <tr><td class="lineno" valign="top"></td><td class="lblock"> processing of payloads received via <span class="delete">HTTP, or secure</span> use of the</td><td> </td><td class="rblock"> processing of payloads received via <span class="insert">HTTP. Secure</span> use of the Internet</td><td class="lineno" valign="top"></td></tr> … … 1350 1320 <tr><td class="lineno" valign="top"></td><td class="left"> system.</td><td> </td><td class="right"> system.</td><td class="lineno" valign="top"></td></tr> 1351 1321 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1352 <tr bgcolor="gray" ><td></td><th><a name="part-l3 6" /><small>skipping to change at</small><em> page 82, line 25</em></th><th> </th><th><a name="part-r36" /><small>skipping to change at</small><em> page 82, line 25</em></th><td></td></tr>1322 <tr bgcolor="gray" ><td></td><th><a name="part-l37" /><small>skipping to change at</small><em> page 82, line 25</em></th><th> </th><th><a name="part-r37" /><small>skipping to change at</small><em> page 82, line 25</em></th><td></td></tr> 1353 1323 <tr><td class="lineno" valign="top"></td><td class="left"> For example, UNIX, Microsoft Windows, and other operating systems use</td><td> </td><td class="right"> For example, UNIX, Microsoft Windows, and other operating systems use</td><td class="lineno" valign="top"></td></tr> 1354 1324 <tr><td class="lineno" valign="top"></td><td class="left"> ".." as a path component to indicate a directory level above the</td><td> </td><td class="right"> ".." as a path component to indicate a directory level above the</td><td class="lineno" valign="top"></td></tr> … … 1361 1331 <tr><td class="lineno" valign="top"></td><td class="left"> case-insensitive names.</td><td> </td><td class="right"> case-insensitive names.</td><td class="lineno" valign="top"></td></tr> 1362 1332 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1363 <tr><td><a name="diff006 6" /></td></tr>1333 <tr><td><a name="diff0064" /></td></tr> 1364 1334 <tr><td class="lineno" valign="top"></td><td class="lblock"> Attacks based on such special names tend to focus on either <span class="delete">denial-</span></td><td> </td><td class="rblock"> Attacks based on such special names tend to focus on either <span class="insert">denial of</span></td><td class="lineno" valign="top"></td></tr> 1365 1335 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> of-service</span> (e.g., telling the server to read from a COM port) or</td><td> </td><td class="rblock"><span class="insert"> service</span> (e.g., telling the server to read from a COM port) or</td><td class="lineno" valign="top"></td></tr> … … 1375 1345 <tr><td class="lineno" valign="top"></td><td class="left"> elements (method, request-target, header fields, or body) to contain</td><td> </td><td class="right"> elements (method, request-target, header fields, or body) to contain</td><td class="lineno" valign="top"></td></tr> 1376 1346 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1377 <tr bgcolor="gray" ><td></td><th><a name="part-l3 7" /><small>skipping to change at</small><em> page 83, line 41</em></th><th> </th><th><a name="part-r37" /><small>skipping to change at</small><em> page 83, line 41</em></th><td></td></tr>1347 <tr bgcolor="gray" ><td></td><th><a name="part-l38" /><small>skipping to change at</small><em> page 83, line 41</em></th><th> </th><th><a name="part-r38" /><small>skipping to change at</small><em> page 83, line 41</em></th><td></td></tr> 1378 1348 <tr><td class="lineno" valign="top"></td><td class="left"> of sensitive data because that data will be placed in the request-</td><td> </td><td class="right"> of sensitive data because that data will be placed in the request-</td><td class="lineno" valign="top"></td></tr> 1379 1349 <tr><td class="lineno" valign="top"></td><td class="left"> target. Many existing servers, proxies, and user agents log or</td><td> </td><td class="right"> target. Many existing servers, proxies, and user agents log or</td><td class="lineno" valign="top"></td></tr> … … 1386 1356 <tr><td class="lineno" valign="top"></td><td class="left"> information about the user's immediate browsing history and any</td><td> </td><td class="right"> information about the user's immediate browsing history and any</td><td class="lineno" valign="top"></td></tr> 1387 1357 <tr><td class="lineno" valign="top"></td><td class="left"> personal information that might be found in the referring resource's</td><td> </td><td class="right"> personal information that might be found in the referring resource's</td><td class="lineno" valign="top"></td></tr> 1388 <tr><td><a name="diff006 7" /></td></tr>1358 <tr><td><a name="diff0065" /></td></tr> 1389 1359 <tr><td class="lineno" valign="top"></td><td class="lblock"> URI. Limitations on Referer are described in Section 5.5.2 to</td><td> </td><td class="rblock"> URI. Limitations on <span class="insert">the</span> Referer <span class="insert">header field</span> are described in</td><td class="lineno" valign="top"></td></tr> 1390 1360 <tr><td class="lineno" valign="top"></td><td class="lblock"> address some of its security considerations.</td><td> </td><td class="rblock"> Section 5.5.2 to address some of its security considerations.</td><td class="lineno" valign="top"></td></tr> … … 1400 1370 <tr><td class="lineno" valign="top"></td><td class="left"> disclosing one site's fragment to another site. If the first site</td><td> </td><td class="right"> disclosing one site's fragment to another site. If the first site</td><td class="lineno" valign="top"></td></tr> 1401 1371 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1402 <tr bgcolor="gray" ><td></td><th><a name="part-l3 8" /><small>skipping to change at</small><em> page 86, line 15</em></th><th> </th><th><a name="part-r38" /><small>skipping to change at</small><em> page 86, line 15</em></th><td></td></tr>1372 <tr bgcolor="gray" ><td></td><th><a name="part-l39" /><small>skipping to change at</small><em> page 86, line 15</em></th><th> </th><th><a name="part-r39" /><small>skipping to change at</small><em> page 86, line 15</em></th><td></td></tr> 1403 1373 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1404 1374 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying</td><td> </td><td class="right"> [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying</td><td class="lineno" valign="top"></td></tr> … … 1411 1381 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right"> [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr> 1412 1382 <tr><td class="lineno" valign="top"></td><td class="left"> Protocol (HTTP/1.1): Message Syntax and Routing",</td><td> </td><td class="right"> Protocol (HTTP/1.1): Message Syntax and Routing",</td><td class="lineno" valign="top"></td></tr> 1413 <tr><td><a name="diff006 8" /></td></tr>1383 <tr><td><a name="diff0066" /></td></tr> 1414 1384 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p1-messaging-latest (work in progress),</span></td><td> </td><td class="rblock"> <span class="insert">RFC 7230,</span> May 2014.</td><td class="lineno" valign="top"></td></tr> 1415 1385 <tr><td class="lineno" valign="top"></td><td class="lblock"> May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> 1416 1386 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1417 1387 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7232] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right"> [RFC7232] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr> 1418 <tr><td><a name="diff006 9" /></td></tr>1388 <tr><td><a name="diff0067" /></td></tr> 1419 1389 <tr><td class="lineno" valign="top"></td><td class="lblock"> Protocol (HTTP/1.1): Conditional Requests",</td><td> </td><td class="rblock"> Protocol (HTTP/1.1): Conditional Requests", <span class="insert">RFC 7232,</span></td><td class="lineno" valign="top"></td></tr> 1420 1390 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p4-conditional-latest (work in</span></td><td> </td><td class="rblock"> May 2014.</td><td class="lineno" valign="top"></td></tr> … … 1423 1393 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7233] Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td> </td><td class="right"> [RFC7233] Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td class="lineno" valign="top"></td></tr> 1424 1394 <tr><td class="lineno" valign="top"></td><td class="left"> "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",</td><td> </td><td class="right"> "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",</td><td class="lineno" valign="top"></td></tr> 1425 <tr><td><a name="diff00 70" /></td></tr>1395 <tr><td><a name="diff0068" /></td></tr> 1426 1396 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p5-range-latest (work in progress),</span></td><td> </td><td class="rblock"> <span class="insert">RFC 7233,</span> May 2014.</td><td class="lineno" valign="top"></td></tr> 1427 1397 <tr><td class="lineno" valign="top"></td><td class="lblock"> May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> … … 1429 1399 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7234] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td> </td><td class="right"> [RFC7234] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td class="lineno" valign="top"></td></tr> 1430 1400 <tr><td class="lineno" valign="top"></td><td class="left"> Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td> </td><td class="right"> Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td class="lineno" valign="top"></td></tr> 1431 <tr><td><a name="diff00 71" /></td></tr>1401 <tr><td><a name="diff0069" /></td></tr> 1432 1402 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p6-cache-latest (work in progress),</span></td><td> </td><td class="rblock"> <span class="insert">RFC 7234,</span> May 2014.</td><td class="lineno" valign="top"></td></tr> 1433 1403 <tr><td class="lineno" valign="top"></td><td class="lblock"> May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> 1434 1404 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1435 1405 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7235] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right"> [RFC7235] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr> 1436 <tr><td><a name="diff007 2" /></td></tr>1406 <tr><td><a name="diff0070" /></td></tr> 1437 1407 <tr><td class="lineno" valign="top"></td><td class="lblock"> Protocol (HTTP/1.1): Authentication",</td><td> </td><td class="rblock"> Protocol (HTTP/1.1): Authentication", <span class="insert">RFC 7235,</span> May 2014.</td><td class="lineno" valign="top"></td></tr> 1438 1408 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p7-auth-latest (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> … … 1449 1419 <tr><td class="lineno" valign="top"></td><td class="left"> Application Protocols", BCP 178, RFC 6648, June 2012.</td><td> </td><td class="right"> Application Protocols", BCP 178, RFC 6648, June 2012.</td><td class="lineno" valign="top"></td></tr> 1450 1420 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1451 <tr bgcolor="gray" ><td></td><th><a name="part-l 39" /><small>skipping to change at</small><em> page 88, line 32</em></th><th> </th><th><a name="part-r39" /><small>skipping to change at</small><em> page 88, line 26</em></th><td></td></tr>1421 <tr bgcolor="gray" ><td></td><th><a name="part-l40" /><small>skipping to change at</small><em> page 88, line 32</em></th><th> </th><th><a name="part-r40" /><small>skipping to change at</small><em> page 88, line 26</em></th><td></td></tr> 1452 1422 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010.</td><td> </td><td class="right"> [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010.</td><td class="lineno" valign="top"></td></tr> 1453 1423 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1460 1430 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1461 1431 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7238] Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td> </td><td class="right"> [RFC7238] Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td class="lineno" valign="top"></td></tr> 1462 <tr><td><a name="diff007 3" /></td></tr>1432 <tr><td><a name="diff0071" /></td></tr> 1463 1433 <tr><td class="lineno" valign="top"></td><td class="lblock"> Status Code 308 (Permanent Redirect)",</td><td> </td><td class="rblock"> Status Code 308 (Permanent Redirect)", <span class="insert">RFC 7238, May 2014.</span></td><td class="lineno" valign="top"></td></tr> 1464 1434 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-reschke-http-status-308-07 (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> … … 1475 1445 <tr><td class="lineno" valign="top"></td><td class="left"> that differ from MIME. These differences were carefully chosen to</td><td> </td><td class="right"> that differ from MIME. These differences were carefully chosen to</td><td class="lineno" valign="top"></td></tr> 1476 1446 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1477 <tr bgcolor="gray" ><td></td><th><a name="part-l4 0" /><small>skipping to change at</small><em> page 90, line 27</em></th><th> </th><th><a name="part-r40" /><small>skipping to change at</small><em> page 90, line 20</em></th><td></td></tr>1447 <tr bgcolor="gray" ><td></td><th><a name="part-l41" /><small>skipping to change at</small><em> page 90, line 27</em></th><th> </th><th><a name="part-r41" /><small>skipping to change at</small><em> page 90, line 20</em></th><td></td></tr> 1478 1448 <tr><td class="lineno" valign="top"></td><td class="left"> message to an HTTP client.</td><td> </td><td class="right"> message to an HTTP client.</td><td class="lineno" valign="top"></td></tr> 1479 1449 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1486 1456 <tr><td class="lineno" valign="top"></td><td class="left"> likelihood of safe transport over the destination protocol.</td><td> </td><td class="right"> likelihood of safe transport over the destination protocol.</td><td class="lineno" valign="top"></td></tr> 1487 1457 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1488 <tr><td><a name="diff007 4" /></td></tr>1458 <tr><td><a name="diff0072" /></td></tr> 1489 1459 <tr><td class="lineno" valign="top"></td><td class="lblock">A.6. MHTML and Line<span class="delete"> </span>Length Limitations</td><td> </td><td class="rblock">A.6. MHTML and Line<span class="insert">-</span>Length Limitations</td><td class="lineno" valign="top"></td></tr> 1490 1460 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1491 1461 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP implementations that share code with MHTML [RFC2557]</td><td> </td><td class="right"> HTTP implementations that share code with MHTML [RFC2557]</td><td class="lineno" valign="top"></td></tr> 1492 <tr><td><a name="diff007 5" /></td></tr>1462 <tr><td><a name="diff0073" /></td></tr> 1493 1463 <tr><td class="lineno" valign="top"></td><td class="lblock"> implementations need to be aware of MIME line<span class="delete"> </span>length limitations.</td><td> </td><td class="rblock"> implementations need to be aware of MIME line<span class="insert">-</span>length limitations.</td><td class="lineno" valign="top"></td></tr> 1494 1464 <tr><td class="lineno" valign="top"></td><td class="left"> Since HTTP does not have this limitation, HTTP does not fold long</td><td> </td><td class="right"> Since HTTP does not have this limitation, HTTP does not fold long</td><td class="lineno" valign="top"></td></tr> 1495 1465 <tr><td class="lineno" valign="top"></td><td class="left"> lines. MHTML messages being transported by HTTP follow all</td><td> </td><td class="right"> lines. MHTML messages being transported by HTTP follow all</td><td class="lineno" valign="top"></td></tr> 1496 <tr><td><a name="diff007 6" /></td></tr>1466 <tr><td><a name="diff0074" /></td></tr> 1497 1467 <tr><td class="lineno" valign="top"></td><td class="lblock"> conventions of MHTML, including line<span class="delete"> </span>length limitations and folding,</td><td> </td><td class="rblock"> conventions of MHTML, including line<span class="insert">-</span>length limitations and folding,</td><td class="lineno" valign="top"></td></tr> 1498 1468 <tr><td class="lineno" valign="top"></td><td class="left"> canonicalization, etc., since HTTP transfers message-bodies as</td><td> </td><td class="right"> canonicalization, etc., since HTTP transfers message-bodies as</td><td class="lineno" valign="top"></td></tr> … … 1511 1481 <tr><td class="lineno" valign="top"></td><td class="left"> representations and representations from resources.</td><td> </td><td class="right"> representations and representations from resources.</td><td class="lineno" valign="top"></td></tr> 1512 1482 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1513 <tr><td><a name="diff007 7" /></td></tr>1483 <tr><td><a name="diff0075" /></td></tr> 1514 1484 <tr><td class="lineno" valign="top"></td><td class="lblock"> A new requirement has been added that semantics embedded in a URI</td><td> </td><td class="rblock"> A new requirement has been added that semantics embedded in a URI be</td><td class="lineno" valign="top"></td></tr> 1515 1485 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">should</span> be disabled when those semantics are inconsistent with the</td><td> </td><td class="rblock"> disabled when those semantics are inconsistent with the request</td><td class="lineno" valign="top"></td></tr> … … 1518 1488 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1519 1489 <tr><td class="lineno" valign="top"></td><td class="left"> An algorithm has been added for determining if a payload is</td><td> </td><td class="right"> An algorithm has been added for determining if a payload is</td><td class="lineno" valign="top"></td></tr> 1520 <tr><td><a name="diff007 8" /></td></tr>1490 <tr><td><a name="diff0076" /></td></tr> 1521 1491 <tr><td class="lineno" valign="top"></td><td class="lblock"> associated with a specific identifier<span class="delete">. (Section 3.1.4.1)</span></td><td> </td><td class="rblock"> associated with a specific identifier<span class="insert"> (Section 3.1.4.1).</span></td><td class="lineno" valign="top"></td></tr> 1522 1492 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1524 1494 <tr><td class="lineno" valign="top"></td><td class="left"> removed; the default is now whatever the media type definition says.</td><td> </td><td class="right"> removed; the default is now whatever the media type definition says.</td><td class="lineno" valign="top"></td></tr> 1525 1495 <tr><td class="lineno" valign="top"></td><td class="left"> Likewise, special treatment of ISO-8859-1 has been removed from the</td><td> </td><td class="right"> Likewise, special treatment of ISO-8859-1 has been removed from the</td><td class="lineno" valign="top"></td></tr> 1526 <tr><td><a name="diff007 9" /></td></tr>1496 <tr><td><a name="diff0077" /></td></tr> 1527 1497 <tr><td class="lineno" valign="top"></td><td class="lblock"> Accept-Charset header field. (Section<span class="delete"> 3.1.1.3 and Section 5.3.3</span>)</td><td> </td><td class="rblock"> Accept-Charset header field. (Section<span class="insert">s 3.1.1.3 and 5.3.3.</span>)</td><td class="lineno" valign="top"></td></tr> 1528 1498 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1530 1500 <tr><td class="lineno" valign="top"></td><td class="left"> affect the base URI for resolving relative URI references, due to</td><td> </td><td class="right"> affect the base URI for resolving relative URI references, due to</td><td class="lineno" valign="top"></td></tr> 1531 1501 <tr><td class="lineno" valign="top"></td><td class="left"> poor implementation support and the undesirable effect of potentially</td><td> </td><td class="right"> poor implementation support and the undesirable effect of potentially</td><td class="lineno" valign="top"></td></tr> 1532 <tr><td><a name="diff00 80" /></td></tr>1502 <tr><td><a name="diff0078" /></td></tr> 1533 1503 <tr><td class="lineno" valign="top"></td><td class="lblock"> breaking relative links in content-negotiated <span class="delete">resources.</span></td><td> </td><td class="rblock"> breaking relative links in content-negotiated <span class="insert">resources</span></td><td class="lineno" valign="top"></td></tr> 1534 1504 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">3.1.4.2)</span></td><td> </td><td class="rblock"> (Section <span class="insert">3.1.4.2).</span></td><td class="lineno" valign="top"></td></tr> … … 1536 1506 <tr><td class="lineno" valign="top"></td><td class="left"> To be consistent with the method-neutral parsing algorithm of</td><td> </td><td class="right"> To be consistent with the method-neutral parsing algorithm of</td><td class="lineno" valign="top"></td></tr> 1537 1507 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7230], the definition of GET has been relaxed so that requests</td><td> </td><td class="right"> [RFC7230], the definition of GET has been relaxed so that requests</td><td class="lineno" valign="top"></td></tr> 1538 <tr><td><a name="diff00 81" /></td></tr>1508 <tr><td><a name="diff0079" /></td></tr> 1539 1509 <tr><td class="lineno" valign="top"></td><td class="lblock"> can have a body, even though a body has no meaning for <span class="delete">GET.</span></td><td> </td><td class="rblock"> can have a body, even though a body has no meaning for <span class="insert">GET</span></td><td class="lineno" valign="top"></td></tr> 1540 1510 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">4.3.1)</span></td><td> </td><td class="rblock"> (Section <span class="insert">4.3.1).</span></td><td class="lineno" valign="top"></td></tr> 1541 1511 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1542 1512 <tr><td class="lineno" valign="top"></td><td class="left"> Servers are no longer required to handle all Content-* header fields</td><td> </td><td class="right"> Servers are no longer required to handle all Content-* header fields</td><td class="lineno" valign="top"></td></tr> 1543 <tr><td><a name="diff008 2" /></td></tr>1513 <tr><td><a name="diff0080" /></td></tr> 1544 1514 <tr><td class="lineno" valign="top"></td><td class="lblock"> and use of Content-Range has been explicitly banned in PUT <span class="delete">requests.</span></td><td> </td><td class="rblock"> and use of Content-Range has been explicitly banned in PUT <span class="insert">requests</span></td><td class="lineno" valign="top"></td></tr> 1545 1515 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">4.3.4)</span></td><td> </td><td class="rblock"> (Section <span class="insert">4.3.4).</span></td><td class="lineno" valign="top"></td></tr> 1546 1516 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1547 1517 <tr><td class="lineno" valign="top"></td><td class="left"> Definition of the CONNECT method has been moved from [RFC2817] to</td><td> </td><td class="right"> Definition of the CONNECT method has been moved from [RFC2817] to</td><td class="lineno" valign="top"></td></tr> 1548 <tr><td><a name="diff008 3" /></td></tr>1518 <tr><td><a name="diff0081" /></td></tr> 1549 1519 <tr><td class="lineno" valign="top"></td><td class="lblock"> this specification<span class="delete">. (Section 4.3.6)</span></td><td> </td><td class="rblock"> this specification<span class="insert"> (Section 4.3.6).</span></td><td class="lineno" valign="top"></td></tr> 1550 1520 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1551 <tr><td><a name="diff008 4" /></td></tr>1521 <tr><td><a name="diff0082" /></td></tr> 1552 1522 <tr><td class="lineno" valign="top"></td><td class="lblock"> The OPTIONS and TRACE request methods have been defined as being</td><td> </td><td class="rblock"> The OPTIONS and TRACE request methods have been defined as being <span class="insert">safe</span></td><td class="lineno" valign="top"></td></tr> 1553 1523 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">safe.</span> (Section 4.3.7 and Section <span class="delete">4.3.8)</span></td><td> </td><td class="rblock"> (Section 4.3.7 and Section <span class="insert">4.3.8).</span></td><td class="lineno" valign="top"></td></tr> 1554 1524 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1555 1525 <tr><td class="lineno" valign="top"></td><td class="left"> The Expect header field's extension mechanism has been removed due to</td><td> </td><td class="right"> The Expect header field's extension mechanism has been removed due to</td><td class="lineno" valign="top"></td></tr> 1556 <tr><td><a name="diff008 5" /></td></tr>1526 <tr><td><a name="diff0083" /></td></tr> 1557 1527 <tr><td class="lineno" valign="top"></td><td class="lblock"> widely<span class="delete">-deployed broken implementations. (Section 5.1.1)</span></td><td> </td><td class="rblock"> widely<span class="insert"> deployed broken implementations (Section 5.1.1).</span></td><td class="lineno" valign="top"></td></tr> 1558 1528 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1559 1529 <tr><td class="lineno" valign="top"></td><td class="left"> The Max-Forwards header field has been restricted to the OPTIONS and</td><td> </td><td class="right"> The Max-Forwards header field has been restricted to the OPTIONS and</td><td class="lineno" valign="top"></td></tr> 1560 1530 <tr><td class="lineno" valign="top"></td><td class="left"> TRACE methods; previously, extension methods could have used it as</td><td> </td><td class="right"> TRACE methods; previously, extension methods could have used it as</td><td class="lineno" valign="top"></td></tr> 1561 <tr><td><a name="diff008 6" /></td></tr>1531 <tr><td><a name="diff0084" /></td></tr> 1562 1532 <tr><td class="lineno" valign="top"></td><td class="lblock"> well<span class="delete">. (Section 5.1.2)</span></td><td> </td><td class="rblock"> well<span class="insert"> (Section 5.1.2).</span></td><td class="lineno" valign="top"></td></tr> 1563 1533 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1565 1535 <tr><td class="lineno" valign="top"></td><td class="left"> header field when no referring URI is applicable, which distinguishes</td><td> </td><td class="right"> header field when no referring URI is applicable, which distinguishes</td><td class="lineno" valign="top"></td></tr> 1566 1536 <tr><td class="lineno" valign="top"></td><td class="left"> that case from others where the Referer field is not sent or has been</td><td> </td><td class="right"> that case from others where the Referer field is not sent or has been</td><td class="lineno" valign="top"></td></tr> 1567 <tr><td><a name="diff008 7" /></td></tr>1537 <tr><td><a name="diff0085" /></td></tr> 1568 1538 <tr><td class="lineno" valign="top"></td><td class="lblock"> removed<span class="delete">. (Section 5.5.2)</span></td><td> </td><td class="rblock"> removed<span class="insert"> (Section 5.5.2).</span></td><td class="lineno" valign="top"></td></tr> 1569 1539 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1570 1540 <tr><td class="lineno" valign="top"></td><td class="left"> The following status codes are now cacheable (that is, they can be</td><td> </td><td class="right"> The following status codes are now cacheable (that is, they can be</td><td class="lineno" valign="top"></td></tr> 1571 1541 <tr><td class="lineno" valign="top"></td><td class="left"> stored and reused by a cache without explicit freshness information</td><td> </td><td class="right"> stored and reused by a cache without explicit freshness information</td><td class="lineno" valign="top"></td></tr> 1572 <tr><td><a name="diff008 8" /></td></tr>1542 <tr><td><a name="diff0086" /></td></tr> 1573 1543 <tr><td class="lineno" valign="top"></td><td class="lblock"> present): 204, 404, 405, 414, 501<span class="delete">. (Section 6)</span></td><td> </td><td class="rblock"> present): 204, 404, 405, 414, 501<span class="insert"> (Section 6).</span></td><td class="lineno" valign="top"></td></tr> 1574 1544 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1575 1545 <tr><td class="lineno" valign="top"></td><td class="left"> The 201 (Created) status description has been changed to allow for</td><td> </td><td class="right"> The 201 (Created) status description has been changed to allow for</td><td class="lineno" valign="top"></td></tr> 1576 <tr><td><a name="diff008 9" /></td></tr>1546 <tr><td><a name="diff0087" /></td></tr> 1577 1547 <tr><td class="lineno" valign="top"></td><td class="lblock"> the possibility that more than one resource has been <span class="delete">created.</span></td><td> </td><td class="rblock"> the possibility that more than one resource has been <span class="insert">created</span></td><td class="lineno" valign="top"></td></tr> 1578 1548 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">6.3.2)</span></td><td> </td><td class="rblock"> (Section <span class="insert">6.3.2).</span></td><td class="lineno" valign="top"></td></tr> 1579 1549 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1580 1550 <tr><td class="lineno" valign="top"></td><td class="left"> The definition of 203 (Non-Authoritative Information) has been</td><td> </td><td class="right"> The definition of 203 (Non-Authoritative Information) has been</td><td class="lineno" valign="top"></td></tr> 1581 <tr><td><a name="diff00 90" /></td></tr>1551 <tr><td><a name="diff0088" /></td></tr> 1582 1552 <tr><td class="lineno" valign="top"></td><td class="lblock"> broadened to include cases of payload transformations as <span class="delete">well.</span></td><td> </td><td class="rblock"> broadened to include cases of payload transformations as <span class="insert">well</span></td><td class="lineno" valign="top"></td></tr> 1583 1553 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">6.3.4)</span></td><td> </td><td class="rblock"> (Section <span class="insert">6.3.4).</span></td><td class="lineno" valign="top"></td></tr> … … 1587 1557 <tr><td class="lineno" valign="top"></td><td class="left"> based upon the request method semantics. The redirect status codes</td><td> </td><td class="right"> based upon the request method semantics. The redirect status codes</td><td class="lineno" valign="top"></td></tr> 1588 1558 <tr><td class="lineno" valign="top"></td><td class="left"> 301, 302, and 307 no longer have normative requirements on response</td><td> </td><td class="right"> 301, 302, and 307 no longer have normative requirements on response</td><td class="lineno" valign="top"></td></tr> 1559 <tr><td><a name="diff0089" /></td></tr> 1560 <tr><td class="lineno" valign="top"></td><td class="lblock"> payloads and user interaction<span class="delete">. (Section 6.4)</span></td><td> </td><td class="rblock"> payloads and user interaction<span class="insert"> (Section 6.4).</span></td><td class="lineno" valign="top"></td></tr> 1561 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1562 <tr><td class="lineno" valign="top"></td><td class="left"> The status codes 301 and 302 have been changed to allow user agents</td><td> </td><td class="right"> The status codes 301 and 302 have been changed to allow user agents</td><td class="lineno" valign="top"></td></tr> 1563 <tr><td><a name="diff0090" /></td></tr> 1564 <tr><td class="lineno" valign="top"></td><td class="lblock"> to rewrite the method from POST to GET. (Sections 6.4.2 and 6.4.3)</td><td> </td><td class="rblock"> to rewrite the method from POST to GET. (Sections 6.4.2 and 6.4.3<span class="insert">.</span>)</td><td class="lineno" valign="top"></td></tr> 1565 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1589 1566 <tr><td><a name="diff0091" /></td></tr> 1590 <tr><td class="lineno" valign="top"></td><td class="lblock"> payloads and user interaction<span class="delete">. (Section 6.4)</span></td><td> </td><td class="rblock"> payloads and user interaction<span class="insert"> (Section 6.4).</span></td><td class="lineno" valign="top"></td></tr>1591 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1592 <tr><td class="lineno" valign="top"></td><td class="left"> The status codes 301 and 302 have been changed to allow user agents</td><td> </td><td class="right"> The status codes 301 and 302 have been changed to allow user agents</td><td class="lineno" valign="top"></td></tr>1593 <tr><td><a name="diff0092" /></td></tr>1594 <tr><td class="lineno" valign="top"></td><td class="lblock"> to rewrite the method from POST to GET. (Sections 6.4.2 and 6.4.3)</td><td> </td><td class="rblock"> to rewrite the method from POST to GET. (Sections 6.4.2 and 6.4.3<span class="insert">.</span>)</td><td class="lineno" valign="top"></td></tr>1595 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1596 <tr><td><a name="diff0093" /></td></tr>1597 1567 <tr><td class="lineno" valign="top"></td><td class="lblock"> The description of 303 (See Other) status code has been changed to</td><td> </td><td class="rblock"> The description of <span class="insert">the</span> 303 (See Other) status code has been changed</td><td class="lineno" valign="top"></td></tr> 1598 1568 <tr><td class="lineno" valign="top"></td><td class="lblock"> allow it to be cached if explicit freshness information is given, and</td><td> </td><td class="rblock"> to allow it to be cached if explicit freshness information is given,</td><td class="lineno" valign="top"></td></tr> … … 1601 1571 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1602 1572 <tr><td class="lineno" valign="top"></td><td class="left"> The 305 (Use Proxy) status code has been deprecated due to security</td><td> </td><td class="right"> The 305 (Use Proxy) status code has been deprecated due to security</td><td class="lineno" valign="top"></td></tr> 1573 <tr><td><a name="diff0092" /></td></tr> 1574 <tr><td class="lineno" valign="top"></td><td class="lblock"> concerns regarding in-band configuration of a proxy<span class="delete">. (Section 6.4.5)</span></td><td> </td><td class="rblock"> concerns regarding in-band configuration of a proxy<span class="insert"> (Section 6.4.5).</span></td><td class="lineno" valign="top"></td></tr> 1575 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1576 <tr><td class="lineno" valign="top"></td><td class="left"> The 400 (Bad Request) status code has been relaxed so that it isn't</td><td> </td><td class="right"> The 400 (Bad Request) status code has been relaxed so that it isn't</td><td class="lineno" valign="top"></td></tr> 1577 <tr><td><a name="diff0093" /></td></tr> 1578 <tr><td class="lineno" valign="top"></td><td class="lblock"> limited to syntax errors<span class="delete">. (Section 6.5.1)</span></td><td> </td><td class="rblock"> limited to syntax errors<span class="insert"> (Section 6.5.1).</span></td><td class="lineno" valign="top"></td></tr> 1579 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1580 <tr><td class="lineno" valign="top"></td><td class="left"> The 426 (Upgrade Required) status code has been incorporated from</td><td> </td><td class="right"> The 426 (Upgrade Required) status code has been incorporated from</td><td class="lineno" valign="top"></td></tr> 1603 1581 <tr><td><a name="diff0094" /></td></tr> 1604 <tr><td class="lineno" valign="top"></td><td class="lblock"> concerns regarding in-band configuration of a proxy<span class="delete">. (Section 6.4.5)</span></td><td> </td><td class="rblock"> concerns regarding in-band configuration of a proxy<span class="insert"> (Section 6.4.5).</span></td><td class="lineno" valign="top"></td></tr>1605 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1606 <tr><td class="lineno" valign="top"></td><td class="left"> The 400 (Bad Request) status code has been relaxed so that it isn't</td><td> </td><td class="right"> The 400 (Bad Request) status code has been relaxed so that it isn't</td><td class="lineno" valign="top"></td></tr>1607 <tr><td><a name="diff0095" /></td></tr>1608 <tr><td class="lineno" valign="top"></td><td class="lblock"> limited to syntax errors<span class="delete">. (Section 6.5.1)</span></td><td> </td><td class="rblock"> limited to syntax errors<span class="insert"> (Section 6.5.1).</span></td><td class="lineno" valign="top"></td></tr>1609 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1610 <tr><td class="lineno" valign="top"></td><td class="left"> The 426 (Upgrade Required) status code has been incorporated from</td><td> </td><td class="right"> The 426 (Upgrade Required) status code has been incorporated from</td><td class="lineno" valign="top"></td></tr>1611 <tr><td><a name="diff0096" /></td></tr>1612 1582 <tr><td class="lineno" valign="top"></td><td class="lblock"> [RFC2817]<span class="delete">. (Section 6.5.15)</span></td><td> </td><td class="rblock"> [RFC2817]<span class="insert"> (Section 6.5.15).</span></td><td class="lineno" valign="top"></td></tr> 1613 1583 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1614 1584 <tr><td class="lineno" valign="top"></td><td class="left"> The target of requirements on HTTP-date and the Date header field</td><td> </td><td class="right"> The target of requirements on HTTP-date and the Date header field</td><td class="lineno" valign="top"></td></tr> 1615 1585 <tr><td class="lineno" valign="top"></td><td class="left"> have been reduced to those systems generating the date, rather than</td><td> </td><td class="right"> have been reduced to those systems generating the date, rather than</td><td class="lineno" valign="top"></td></tr> 1616 <tr><td><a name="diff009 7" /></td></tr>1586 <tr><td><a name="diff0095" /></td></tr> 1617 1587 <tr><td class="lineno" valign="top"></td><td class="lblock"> all systems sending a date<span class="delete">. (Section 7.1.1)</span></td><td> </td><td class="rblock"> all systems sending a date<span class="insert"> (Section 7.1.1).</span></td><td class="lineno" valign="top"></td></tr> 1618 1588 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1620 1590 <tr><td class="lineno" valign="top"></td><td class="left"> URI references, including relative references and fragments, along</td><td> </td><td class="right"> URI references, including relative references and fragments, along</td><td class="lineno" valign="top"></td></tr> 1621 1591 <tr><td class="lineno" valign="top"></td><td class="left"> with some clarifications as to when use of fragments would not be</td><td> </td><td class="right"> with some clarifications as to when use of fragments would not be</td><td class="lineno" valign="top"></td></tr> 1622 <tr><td><a name="diff009 8" /></td></tr>1592 <tr><td><a name="diff0096" /></td></tr> 1623 1593 <tr><td class="lineno" valign="top"></td><td class="lblock"> appropriate<span class="delete">. (Section 7.1.2)</span></td><td> </td><td class="rblock"> appropriate<span class="insert"> (Section 7.1.2).</span></td><td class="lineno" valign="top"></td></tr> 1624 1594 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1626 1596 <tr><td class="lineno" valign="top"></td><td class="left"> option to specify it in a PUT request. Requirements relating to the</td><td> </td><td class="right"> option to specify it in a PUT request. Requirements relating to the</td><td class="lineno" valign="top"></td></tr> 1627 1597 <tr><td class="lineno" valign="top"></td><td class="left"> content of Allow have been relaxed; correspondingly, clients are not</td><td> </td><td class="right"> content of Allow have been relaxed; correspondingly, clients are not</td><td class="lineno" valign="top"></td></tr> 1598 <tr><td><a name="diff0097" /></td></tr> 1599 <tr><td class="lineno" valign="top"></td><td class="lblock"> required to always trust its value<span class="delete">. (Section 7.4.1)</span></td><td> </td><td class="rblock"> required to always trust its value<span class="insert"> (Section 7.4.1).</span></td><td class="lineno" valign="top"></td></tr> 1600 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1601 <tr><td><a name="diff0098" /></td></tr> 1602 <tr><td class="lineno" valign="top"></td><td class="lblock"> A Method Registry has been defined<span class="delete">. (Section 8.1)</span></td><td> </td><td class="rblock"> A Method Registry has been defined<span class="insert"> (Section 8.1).</span></td><td class="lineno" valign="top"></td></tr> 1603 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1604 <tr><td class="lineno" valign="top"></td><td class="left"> The Status Code Registry has been redefined by this specification;</td><td> </td><td class="right"> The Status Code Registry has been redefined by this specification;</td><td class="lineno" valign="top"></td></tr> 1628 1605 <tr><td><a name="diff0099" /></td></tr> 1629 <tr><td class="lineno" valign="top"></td><td class="lblock"> required to always trust its value<span class="delete">. (Section 7.4.1)</span></td><td> </td><td class="rblock"> required to always trust its value<span class="insert"> (Section 7.4.1).</span></td><td class="lineno" valign="top"></td></tr>1630 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1631 <tr><td><a name="diff0100" /></td></tr>1632 <tr><td class="lineno" valign="top"></td><td class="lblock"> A Method Registry has been defined<span class="delete">. (Section 8.1)</span></td><td> </td><td class="rblock"> A Method Registry has been defined<span class="insert"> (Section 8.1).</span></td><td class="lineno" valign="top"></td></tr>1633 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1634 <tr><td class="lineno" valign="top"></td><td class="left"> The Status Code Registry has been redefined by this specification;</td><td> </td><td class="right"> The Status Code Registry has been redefined by this specification;</td><td class="lineno" valign="top"></td></tr>1635 <tr><td><a name="diff0101" /></td></tr>1636 1606 <tr><td class="lineno" valign="top"></td><td class="lblock"> previously, it was defined in Section 7.1 of <span class="delete">[RFC2817].</span></td><td> </td><td class="rblock"> previously, it was defined in Section 7.1 of <span class="insert">[RFC2817]</span> (Section <span class="insert">8.2).</span></td><td class="lineno" valign="top"></td></tr> 1637 1607 <tr><td class="lineno" valign="top"></td><td class="lblock"> </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> 1638 1608 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">8.2)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> 1639 1609 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1640 <tr><td><a name="diff010 2" /></td></tr>1610 <tr><td><a name="diff0100" /></td></tr> 1641 1611 <tr><td class="lineno" valign="top"></td><td class="lblock"> Registration of <span class="delete">Content Codings</span> has been changed to require IETF</td><td> </td><td class="rblock"> Registration of <span class="insert">content codings</span> has been changed to require IETF</td><td class="lineno" valign="top"></td></tr> 1642 1612 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">Review.</span> (Section <span class="delete">8.4)</span></td><td> </td><td class="rblock"> <span class="insert">Review</span> (Section <span class="insert">8.4).</span></td><td class="lineno" valign="top"></td></tr> … … 1652 1622 <tr><td class="lineno" valign="top"></td><td class="left"> The following core rules are included by reference, as defined in</td><td> </td><td class="right"> The following core rules are included by reference, as defined in</td><td class="lineno" valign="top"></td></tr> 1653 1623 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1654 <tr bgcolor="gray" ><td></td><th><a name="part-l4 1" /><small>skipping to change at</small><em> page 99, line 45</em></th><th> </th><th><a name="part-r41" /><small>skipping to change at</small><em> page 99, line 40</em></th><td></td></tr>1624 <tr bgcolor="gray" ><td></td><th><a name="part-l42" /><small>skipping to change at</small><em> page 99, line 45</em></th><th> </th><th><a name="part-r42" /><small>skipping to change at</small><em> page 99, line 40</em></th><td></td></tr> 1655 1625 <tr><td class="lineno" valign="top"></td><td class="left"> HEAD method 25</td><td> </td><td class="right"> HEAD method 25</td><td class="lineno" valign="top"></td></tr> 1656 1626 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1663 1633 <tr><td class="lineno" valign="top"></td><td class="left"> M</td><td> </td><td class="right"> M</td><td class="lineno" valign="top"></td></tr> 1664 1634 <tr><td class="lineno" valign="top"></td><td class="left"> Max-Forwards header field 36</td><td> </td><td class="right"> Max-Forwards header field 36</td><td class="lineno" valign="top"></td></tr> 1665 <tr><td><a name="diff010 3" /></td></tr>1635 <tr><td><a name="diff0101" /></td></tr> 1666 1636 <tr><td class="lineno" valign="top"></td><td class="lblock"> MIME-Version header field 8<span class="delete">9</span></td><td> </td><td class="rblock"> MIME-Version header field 8<span class="insert">8</span></td><td class="lineno" valign="top"></td></tr> 1667 1637 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1677 1647 1678 1648 <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr> 1679 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 10 3change blocks. </a></th></tr>1680 <tr class="stats"><td></td><th><i>25 4 lines changed or deleted</i></th><th><i> </i></th><th><i>230lines changed or added</i></th><td></td></tr>1649 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 101 change blocks. </a></th></tr> 1650 <tr class="stats"><td></td><th><i>250 lines changed or deleted</i></th><th><i> </i></th><th><i>226 lines changed or added</i></th><td></td></tr> 1681 1651 <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.38. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr> 1682 1652 </table> -
draft-ietf-httpbis/latest/p1-messaging.html
r2650 r2651 1166 1166 </pre><p id="rfc.section.2.7.2.p.4">Note that the "https" URI scheme depends on both TLS and TCP for establishing authority. Resources made available via the 1167 1167 "https" scheme have no shared identity with the "http" scheme even if their resource identifiers indicate the same authority 1168 (the same host listening to the same TCP port). They are distinct name 1168 (the same host listening to the same TCP port). They are distinct namespaces and are considered to be distinct origin servers. 1169 1169 However, an extension to HTTP that is defined to apply to entire host domains, such as the Cookie protocol <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>, can allow information set by one service to impact communication with other services within a matching group of host domains. 1170 1170 </p> … … 2691 2691 <div id="transfer.coding.registry"> 2692 2692 <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a> <a href="#transfer.coding.registry">Transfer Coding Registry</a></h2> 2693 <p id="rfc.section.8.4.p.1">The HTTP Transfer Coding Registry defines the name 2693 <p id="rfc.section.8.4.p.1">The HTTP Transfer Coding Registry defines the namespace for transfer coding names. It is maintained at <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>>. 2694 2694 </p> 2695 2695 <div id="transfer.coding.registry.procedure"> … … 2704 2704 <p id="rfc.section.8.4.1.p.2">Names of transfer codings <em class="bcp14">MUST NOT</em> overlap with names of content codings (<a href="p2-semantics.html#content.codings" title="Content Codings">Section 3.1.2.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.33"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) unless the encoding transformation is identical, as is the case for the compression codings defined in <a href="#compression.codings" title="Compression Codings">Section 4.2</a>. 2705 2705 </p> 2706 <p id="rfc.section.8.4.1.p.3">Values to be added to this name 2706 <p id="rfc.section.8.4.1.p.3">Values to be added to this namespace require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of transfer coding defined in this specification. 2707 2707 </p> 2708 2708 <p id="rfc.section.8.4.1.p.4">Use of program names for the identification of encoding formats is not desirable and is discouraged for future encodings.</p> … … 2817 2817 <div id="upgrade.token.registry"> 2818 2818 <h2 id="rfc.section.8.6"><a href="#rfc.section.8.6">8.6</a> <a href="#upgrade.token.registry">Upgrade Token Registry</a></h2> 2819 <p id="rfc.section.8.6.p.1">The HTTP Upgrade Token Registry defines the name 2819 <p id="rfc.section.8.6.p.1">The HTTP Upgrade Token Registry defines the namespace for protocol-name tokens used to identify protocols in the <a href="#header.upgrade" class="smpl">Upgrade</a> header field. The registry is maintained at <<a href="http://www.iana.org/assignments/http-upgrade-tokens">http://www.iana.org/assignments/http-upgrade-tokens</a>>. 2820 2820 </p> 2821 2821 <div id="upgrade.token.registry.procedure"> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2650 r2651 978 978 identity with the "http" scheme even if their resource identifiers 979 979 indicate the same authority (the same host listening to the same 980 TCP port). They are distinct name 980 TCP port). They are distinct namespaces and are considered to be 981 981 distinct origin servers. However, an extension to HTTP that is 982 982 defined to apply to entire host domains, such as the Cookie protocol … … 3716 3716 <section title="Transfer Coding Registry" anchor="transfer.coding.registry"> 3717 3717 <t> 3718 The HTTP Transfer Coding Registry defines the name 3718 The HTTP Transfer Coding Registry defines the namespace for transfer 3719 3719 coding names. It is maintained at <eref target="http://www.iana.org/assignments/http-parameters"/>. 3720 3720 </t> … … 3736 3736 </t> 3737 3737 <t> 3738 Values to be added to this name 3738 Values to be added to this namespace require IETF Review (see 3739 3739 <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST; 3740 3740 conform to the purpose of transfer coding defined in this specification. … … 3835 3835 <section title="Upgrade Token Registry" anchor="upgrade.token.registry"> 3836 3836 <t> 3837 The HTTP Upgrade Token Registry defines the name 3837 The HTTP Upgrade Token Registry defines the namespace for protocol-name 3838 3838 tokens used to identify protocols in the <x:ref>Upgrade</x:ref> header 3839 3839 field. The registry is maintained at <eref target="http://www.iana.org/assignments/http-upgrade-tokens"/>. -
draft-ietf-httpbis/latest/p2-semantics.html
r2647 r2651 3431 3431 <div id="method.registry"> 3432 3432 <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a> <a href="#method.registry">Method Registry</a></h2> 3433 <p id="rfc.section.8.1.p.1">The HTTP Method Registry defines the name 3433 <p id="rfc.section.8.1.p.1">The HTTP Method Registry defines the namespace for the request method token (<a href="#methods" title="Request Methods">Section 4</a>). The method registry will be created and maintained at (the suggested URI) <<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>>. 3434 3434 </p> 3435 3435 <div id="method.registry.procedure"> … … 3446 3446 <li>Pointer to specification text</li> 3447 3447 </ul> 3448 <p id="rfc.section.8.1.1.p.2">Values to be added to this name 3448 <p id="rfc.section.8.1.1.p.2">Values to be added to this namespace require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 3449 3449 </p> 3450 3450 </div> … … 3550 3550 <div id="status.code.registry"> 3551 3551 <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a> <a href="#status.code.registry">Status Code Registry</a></h2> 3552 <p id="rfc.section.8.2.p.1">The HTTP Status Code Registry defines the name 3552 <p id="rfc.section.8.2.p.1">The HTTP Status Code Registry defines the namespace for the response status-code token (<a href="#status.codes" title="Response Status Codes">Section 6</a>). The status code registry is maintained at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>>. 3553 3553 </p> 3554 3554 <p id="rfc.section.8.2.p.2">This section replaces the registration procedure for HTTP Status Codes previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. … … 3563 3563 <li>Pointer to specification text</li> 3564 3564 </ul> 3565 <p id="rfc.section.8.2.1.p.2">Values to be added to the HTTP status code name 3565 <p id="rfc.section.8.2.1.p.2">Values to be added to the HTTP status code namespace require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 3566 3566 </p> 3567 3567 </div> … … 4079 4079 <div id="content.coding.registry"> 4080 4080 <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a> <a href="#content.coding.registry">Content Coding Registry</a></h2> 4081 <p id="rfc.section.8.4.p.1">The HTTP Content Coding Registry defines the name 4081 <p id="rfc.section.8.4.p.1">The HTTP Content Coding Registry defines the namespace for content coding names (<a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.40"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>). The content coding registry is maintained at <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>>. 4082 4082 </p> 4083 4083 <div id="content.coding.procedure"> … … 4092 4092 <p id="rfc.section.8.4.1.p.2">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.41"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.42"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>). 4093 4093 </p> 4094 <p id="rfc.section.8.4.1.p.3">Values to be added to this name 4094 <p id="rfc.section.8.4.1.p.3">Values to be added to this namespace require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.3"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section. 4095 4095 </p> 4096 4096 </div> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2647 r2651 4205 4205 <section title="Method Registry" anchor="method.registry"> 4206 4206 <t> 4207 The HTTP Method Registry defines the name 4207 The HTTP Method Registry defines the namespace for the request method 4208 4208 token (<xref target="methods"/>). 4209 4209 The method registry will be created and maintained at (the suggested URI) … … 4222 4222 </t> 4223 4223 <t> 4224 Values to be added to this name 4224 Values to be added to this namespace require IETF Review 4225 4225 (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 4226 4226 </t> … … 4335 4335 <section title="Status Code Registry" anchor="status.code.registry"> 4336 4336 <t> 4337 The HTTP Status Code Registry defines the name 4337 The HTTP Status Code Registry defines the namespace for the response 4338 4338 status-code token (<xref target="status.codes"/>). The status code registry 4339 4339 is maintained at <eref target="http://www.iana.org/assignments/http-status-codes"/>. … … 4354 4354 </t> 4355 4355 <t> 4356 Values to be added to the HTTP status code name 4356 Values to be added to the HTTP status code namespace require IETF Review 4357 4357 (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 4358 4358 </t> … … 4859 4859 <section title="Content Coding Registry" anchor="content.coding.registry"> 4860 4860 <t> 4861 The HTTP Content Coding Registry defines the name 4861 The HTTP Content Coding Registry defines the namespace for content 4862 4862 coding names (&compression-codings;). 4863 4863 The content coding registry is maintained at … … 4881 4881 </t> 4882 4882 <t> 4883 Values to be added to this name 4883 Values to be added to this namespace require IETF Review 4884 4884 (see <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST; 4885 4885 conform to the purpose of content coding defined in this section. -
draft-ietf-httpbis/latest/p4-conditional.html
r2632 r2651 663 663 <div id="notation"> 664 664 <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a> <a href="#notation">Syntax Notation</a></h2> 665 <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates665 <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF List Extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates 666 666 repetition). <a href="#imported.abnf" title="Imported ABNF">Appendix B</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix C</a> shows the collected grammar with all list operators expanded to standard ABNF notation. 667 667 </p> … … 1413 1413 </p> 1414 1414 <div id="rfc.figure.u.16"></div><pre class="inline"> <a href="#imported.abnf" class="smpl">OWS</a> = <OWS, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>> 1415 <a href="#imported.abnf" class="smpl">obs-text</a> = <obs-text, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>>1415 <a href="#imported.abnf" class="smpl">obs-text</a> = <obs-text, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field Value Components">Section 3.2.6</a>> 1416 1416 </pre><p id="rfc.section.B.p.4">The rules below are defined in other parts:</p> 1417 1417 <div id="rfc.figure.u.17"></div><pre class="inline"> <a href="#imported.abnf" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#RFC7231" id="rfc.xref.RFC7231.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>> -
draft-ietf-httpbis/latest/p5-range.html
r2643 r2651 983 983 <div id="range.unit.registry"> 984 984 <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a href="#range.unit.registry">Range Unit Registry</a></h2> 985 <p id="rfc.section.5.1.p.1">The HTTP Range Unit Registry defines the name 985 <p id="rfc.section.5.1.p.1">The HTTP Range Unit Registry defines the namespace for the range unit names and refers to their corresponding specifications. 986 986 The registry will be created and maintained at (the suggested URI) <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>>. 987 987 </p> … … 995 995 <li>Pointer to specification text</li> 996 996 </ul> 997 <p id="rfc.section.5.1.1.p.2">Values to be added to this name 997 <p id="rfc.section.5.1.1.p.2">Values to be added to this namespace require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 998 998 </p> 999 999 </div> -
draft-ietf-httpbis/latest/p5-range.xml
r2643 r2651 851 851 <section title="Range Unit Registry" anchor="range.unit.registry"> 852 852 <t> 853 The HTTP Range Unit Registry defines the name 853 The HTTP Range Unit Registry defines the namespace for the range 854 854 unit names and refers to their corresponding specifications. 855 855 The registry will be created and maintained at (the suggested URI) … … 867 867 </t> 868 868 <t> 869 Values to be added to this name 869 Values to be added to this namespace require IETF Review 870 870 (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 871 871 </t> -
draft-ietf-httpbis/latest/p6-cache.html
r2643 r2651 1656 1656 <div id="cache.directive.registry"> 1657 1657 <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a> <a href="#cache.directive.registry">Cache Directive Registry</a></h2> 1658 <p id="rfc.section.7.1.p.1">The HTTP Cache Directive Registry defines the name 1658 <p id="rfc.section.7.1.p.1">The HTTP Cache Directive Registry defines the namespace for the cache directives. It will be created and maintained at (the 1659 1659 suggested URI) <<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>>. 1660 1660 </p> … … 1667 1667 <li>Pointer to specification text</li> 1668 1668 </ul> 1669 <p id="rfc.section.7.1.1.p.2">Values to be added to this name 1669 <p id="rfc.section.7.1.1.p.2">Values to be added to this namespace require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 1670 1670 </p> 1671 1671 </div> … … 1773 1773 <div id="warn.code.registry"> 1774 1774 <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a> <a href="#warn.code.registry">Warn Code Registry</a></h2> 1775 <p id="rfc.section.7.2.p.1">The HTTP Warn Code Registry defines the name 1775 <p id="rfc.section.7.2.p.1">The HTTP Warn Code Registry defines the namespace for warn codes. It will be created and maintained at (the suggested URI) <<a href="http://www.iana.org/assignments/http-warn-codes">http://www.iana.org/assignments/http-warn-codes</a>>. 1776 1776 </p> 1777 1777 <div id="warn.code.registry.procedure"> … … 1784 1784 <li>Pointer to specification text</li> 1785 1785 </ul> 1786 <p id="rfc.section.7.2.1.p.2">Values to be added to this name 1786 <p id="rfc.section.7.2.1.p.2">Values to be added to this namespace require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 1787 1787 </p> 1788 1788 </div> -
draft-ietf-httpbis/latest/p6-cache.xml
r2643 r2651 1900 1900 <section title="Cache Directive Registry" anchor="cache.directive.registry"> 1901 1901 <t> 1902 The HTTP Cache Directive Registry defines the name 1902 The HTTP Cache Directive Registry defines the namespace for the 1903 1903 cache directives. It will be created and maintained at (the suggested URI) 1904 1904 <eref target="http://www.iana.org/assignments/http-cache-directives"/>. … … 1914 1914 </t> 1915 1915 <t> 1916 Values to be added to this name 1916 Values to be added to this namespace require IETF Review (see <xref 1917 1917 target="RFC5226" x:fmt="," x:sec="4.1"/>). 1918 1918 </t> … … 2014 2014 <section title="Warn Code Registry" anchor="warn.code.registry"> 2015 2015 <t> 2016 The HTTP Warn Code Registry defines the name 2016 The HTTP Warn Code Registry defines the namespace for warn codes. 2017 2017 It will be created and maintained at (the suggested URI) 2018 2018 <eref target="http://www.iana.org/assignments/http-warn-codes"/>. … … 2029 2029 </t> 2030 2030 <t> 2031 Values to be added to this name 2031 Values to be added to this namespace require IETF Review (see <xref 2032 2032 target="RFC5226" x:fmt="," x:sec="4.1"/>). 2033 2033 </t> -
draft-ietf-httpbis/latest/p7-auth.html
r2632 r2651 650 650 <div id="notation"> 651 651 <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a> <a href="#notation">Syntax Notation</a></h2> 652 <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates652 <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF List Extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates 653 653 repetition). <a href="#imported.abnf" title="Imported ABNF">Appendix B</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix C</a> shows the collected grammar with all list operators expanded to standard ABNF notation. 654 654 </p> … … 831 831 <div id="authentication.scheme.registry"> 832 832 <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a href="#authentication.scheme.registry">Authentication Scheme Registry</a></h2> 833 <p id="rfc.section.5.1.p.1">The HTTP Authentication Scheme Registry defines the name 833 <p id="rfc.section.5.1.p.1">The HTTP Authentication Scheme Registry defines the namespace for the authentication schemes in challenges and credentials. 834 834 It will be created and maintained at (the suggested URI) <<a href="http://www.iana.org/assignments/http-authschemes">http://www.iana.org/assignments/http-authschemes</a>>. 835 835 </p> … … 843 843 <li>Notes (optional)</li> 844 844 </ul> 845 <p id="rfc.section.5.1.1.p.2">Values to be added to this name 845 <p id="rfc.section.5.1.1.p.2">Values to be added to this namespace require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 846 846 </p> 847 847 </div> … … 1154 1154 <div id="rfc.figure.u.9"></div><pre class="inline"> <a href="#imported.abnf" class="smpl">BWS</a> = <BWS, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>> 1155 1155 <a href="#imported.abnf" class="smpl">OWS</a> = <OWS, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>> 1156 <a href="#imported.abnf" class="smpl">quoted-string</a> = <quoted-string, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>>1157 <a href="#imported.abnf" class="smpl">token</a> = <token, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>>1156 <a href="#imported.abnf" class="smpl">quoted-string</a> = <quoted-string, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field Value Components">Section 3.2.6</a>> 1157 <a href="#imported.abnf" class="smpl">token</a> = <token, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field Value Components">Section 3.2.6</a>> 1158 1158 </pre></div> 1159 1159 <div id="collected.abnf"> -
draft-ietf-httpbis/latest/p7-auth.xml
r2632 r2651 512 512 <section title="Authentication Scheme Registry" anchor="authentication.scheme.registry"> 513 513 <t> 514 The HTTP Authentication Scheme Registry defines the name 514 The HTTP Authentication Scheme Registry defines the namespace for the 515 515 authentication schemes in challenges and credentials. It will be created and 516 516 maintained at (the suggested URI) <eref target="http://www.iana.org/assignments/http-authschemes"/>. … … 527 527 </t> 528 528 <t> 529 Values to be added to this name 529 Values to be added to this namespace require IETF Review 530 530 (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 531 531 </t>
Note: See TracChangeset
for help on using the changeset viewer.