Changeset 2647
- Timestamp:
- 06/05/14 16:20:31 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 10 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/auth48/p1-messaging.unpg.txt
r2646 r2647 633 633 [RFC7234]. 634 634 635 There are a wide variety of architectures and configurations of636 caches deployed across the World Wide Web and inside large637 organizations. These include national hierarchies of proxy caches to638 savetransoceanic bandwidth, collaborative systems that broadcast or635 There is a wide variety of architectures and configurations of caches 636 deployed across the World Wide Web and inside large organizations. 637 These include national hierarchies of proxy caches to save 638 transoceanic bandwidth, collaborative systems that broadcast or 639 639 multicast cache entries, archives of pre-fetched cache entries for 640 640 use in off-line or high-latency environments, and so on. … … 669 669 When a received protocol element is parsed, the recipient MUST be 670 670 able to parse any value of reasonable length that is applicable to 671 the recipient's role and matches the grammar defined by the671 the recipient's role and that matches the grammar defined by the 672 672 corresponding ABNF rules. Note, however, that some received protocol 673 673 elements might not be parsed. For example, an intermediary … … 1118 1118 3.1. Start Line 1119 1119 1120 An HTTP message can either bea request from client to server or a1120 An HTTP message can be either a request from client to server or a 1121 1121 response from server to client. Syntactically, the two types of 1122 1122 message differ only in the start-line, which is either a request-line … … 1378 1378 processed). Consequently, this specification does not use ABNF rules 1379 1379 to define each "Field-Name: Field Value" pair, as was done in 1380 previous editions. Instead, this specification uses ABNF rules which1380 previous editions. Instead, this specification uses ABNF rules that 1381 1381 are named according to each registered field name, wherein the rule 1382 1382 defines the valid grammar for that field's corresponding field values … … 2952 2952 implemented by many HTTP/1.0 clients). 2953 2953 2954 See Appendix A.1.2 for more information on backward compatibility2954 See Appendix A.1.2 for more information on backwards compatibility 2955 2955 with HTTP/1.0 clients. 2956 2956 … … 2999 2999 response). A server MAY process a sequence of pipelined requests in 3000 3000 parallel if they all have safe methods (Section 4.2.1 of [RFC7231]), 3001 but MUST send the corresponding responses in the same order that the3002 requests were received.3001 but it MUST send the corresponding responses in the same order that 3002 the requests were received. 3003 3003 3004 3004 A client that pipelines requests SHOULD retry unanswered requests if … … 3271 3271 until it has completely sent the request message (i.e., the client 3272 3272 can't change the protocol it is sending in the middle of a message). 3273 If a server receives both Upgrade and an Expect header field with the3274 "100-continue" expectation (Section 5.1.1 of [RFC7231]), the server3275 MUST send a 100 (Continue) response before sending a 101 (Switching3276 Protocols) response.3273 If a server receives both an Upgrade and an Expect header field with 3274 the "100-continue" expectation (Section 5.1.1 of [RFC7231]), the 3275 server MUST send a 100 (Continue) response before sending a 101 3276 (Switching Protocols) response. 3277 3277 3278 3278 The Upgrade header field only applies to switching protocols on top … … 3970 3970 securely stored and appropriate guidelines followed for its analysis. 3971 3971 Anonymization of personal information within individual entries 3972 helps, but i s generally not sufficient to prevent real log traces3972 helps, but it is generally not sufficient to prevent real log traces 3973 3973 from being re-identified based on correlation with other access 3974 3974 characteristics. As such, access traces that are keyed to a specific … … 4305 4305 requirements that enable reliable implementations, adding only those 4306 4306 features that can either be safely ignored by an HTTP/1.0 recipient 4307 or only sent when communicating with a party advertising conformance4308 with HTTP/1.1.4307 or only be sent when communicating with a party advertising 4308 conformance with HTTP/1.1. 4309 4309 4310 4310 HTTP/1.1 has been designed to make supporting previous versions easy. … … 4409 4409 4410 4410 The HTTP-version ABNF production has been clarified to be case- 4411 sensitive. Additionally, version numbers ha sbeen restricted to4411 sensitive. Additionally, version numbers have been restricted to 4412 4412 single digits, due to the fact that implementations are known to 4413 4413 handle multi-digit version numbers incorrectly. (Section 2.6) -
draft-ietf-httpbis/latest/auth48/p2-semantics.unpg.txt
r2645 r2647 294 294 relation to the identified request target, and responds to that 295 295 request with one or more response messages. A client constructs 296 request messages to communicate specific intentions, andexamines296 request messages to communicate specific intentions, examines 297 297 received responses to see if the intentions were carried out, and 298 determine how to interpret the results. This document defines298 determines how to interpret the results. This document defines 299 299 HTTP/1.1 request and response semantics in terms of the architecture 300 300 defined in [RFC7230]. … … 385 385 potentially unbounded stream of representation data. 386 386 387 An origin server might be provided with, or capable of generating,387 An origin server might be provided with, or be capable of generating, 388 388 multiple representations that are each intended to reflect the 389 389 current state of a target resource. In such cases, some algorithm is … … 461 461 462 462 A parameter value that matches the token production can be 463 transmitted as eithera token or within a quoted-string. The quoted463 transmitted either as a token or within a quoted-string. The quoted 464 464 and unquoted values are equivalent. For example, the following 465 465 examples are all equivalent, but the first is preferred for … … 486 486 charset = token 487 487 488 Charset names ought to be registered in IANA Character Set registry489 (<http://www.iana.org/assignments/character-sets>) according to the490 procedures defined in [RFC2978].488 Charset names ought to be registered in the IANA Character Set 489 registry (<http://www.iana.org/assignments/character-sets>) according 490 to the procedures defined in [RFC2978]. 491 491 492 492 3.1.1.3. Canonicalization and Text Defaults … … 1555 1555 reflects the new representation. This requirement allows a user 1556 1556 agent to know when the representation body it has in memory remains 1557 current as a result of the PUT, thus not in need of retrieving again1558 from the origin server, and that the new validator(s) received in the1559 response can be used for future conditional requests in order to1560 prevent accidental overwrites (Section 5.2).1557 current as a result of the PUT, thus not in need of being retrieved 1558 again from the origin server, and that the new validator(s) received 1559 in the response can be used for future conditional requests in order 1560 to prevent accidental overwrites (Section 5.2). 1561 1561 1562 1562 The fundamental difference between the POST and PUT methods is … … 1751 1751 1752 1752 The OPTIONS method requests information about the communication 1753 options available for the target resource, either atthe origin1753 options available for the target resource, at either the origin 1754 1754 server or an intervening intermediary. This method allows a client 1755 1755 to determine the options and/or requirements associated with a … … 2601 2601 identifier. A sender SHOULD NOT generate information in product- 2602 2602 version that is not a version identifier (i.e., successive versions 2603 of the same product name ought to onlydiffer in the product-version2603 of the same product name ought only to differ in the product-version 2604 2604 portion of the product identifier). 2605 2605 … … 3284 3284 3285 3285 The 400 (Bad Request) status code indicates that the server cannot or 3286 will not process the request due to something which is perceived to3287 bea client error (e.g., malformed request syntax, invalid request3286 will not process the request due to something that is perceived to be 3287 a client error (e.g., malformed request syntax, invalid request 3288 3288 message framing, or deceptive request routing). 3289 3289 … … 3878 3878 3879 3879 3880 If the Location value provided in a 3xx (Redirection) does not have a3881 fragment component, a user agent MUST process the redirection as if3882 the value inherits the fragment component of the URI reference used3883 to generate the request target (i.e., the redirection inheritsthe3884 original reference's fragment, if any).3880 If the Location value provided in a 3xx (Redirection) response does 3881 not have a fragment component, a user agent MUST process the 3882 redirection as if the value inherits the fragment component of the 3883 URI reference used to generate the request target (i.e., the 3884 redirection inherits the original reference's fragment, if any). 3885 3885 3886 3886 For example, a GET request generated for the URI reference … … 4252 4252 maintained at <http://www.iana.org/assignments/http-status-codes>. 4253 4253 4254 This Section replaces the registration procedure for HTTP Status4254 This section replaces the registration procedure for HTTP Status 4255 4255 Codes previously defined in Section 7.1 of [RFC2817]. 4256 4256 … … 4401 4401 4402 4402 Authors of specifications defining new fields are advised to keep the 4403 name as short as practical and to notprefix the name with "X-"4403 name as short as practical and not to prefix the name with "X-" 4404 4404 unless the header field will never be used on the Internet. (The 4405 " x-" prefix idiom has been extensively misused in practice; it was4405 "X-" prefix idiom has been extensively misused in practice; it was 4406 4406 intended to only be used as a mechanism for avoiding name collisions 4407 4407 inside proprietary software or intranet processing, since the prefix 4408 4408 would ensure that private names never collide with a newly registered 4409 Internet name; see [BCP178] for further information) 4409 Internet name; see [BCP178] for further information). 4410 4410 4411 4411 New header field values typically have their syntax defined using … … 4631 4631 For example, UNIX, Microsoft Windows, and other operating systems use 4632 4632 ".." as a path component to indicate a directory level above the 4633 current one, and use specially named paths or file names to send data4634 to system devices. Similar naming conventions might exist within4635 other types of storage systems. Likewise, local storage systems have4636 an annoying tendency to prefer user-friendliness over security when4637 handling invalid or unexpected characters, recomposition of4638 decomposed characters, and case-normalization of case-insensitive4639 names.4633 current one, and they use specially named paths or file names to send 4634 data to system devices. Similar naming conventions might exist 4635 within other types of storage systems. Likewise, local storage 4636 systems have an annoying tendency to prefer user-friendliness over 4637 security when handling invalid or unexpected characters, 4638 recomposition of decomposed characters, and case-normalization of 4639 case-insensitive names. 4640 4640 4641 4641 Attacks based on such special names tend to focus on either denial- … … 4999 4999 variety of representations and with extensible header fields. 5000 5000 However, RFC 2045 is focused only on email; applications of HTTP have 5001 many characteristics that differ from email , and hence HTTP has5002 features that differ from MIME. These differences were carefully5003 chosen to optimize performance over binary connections, to allow5004 greater freedom in the use of new media types, to make date5005 comparisons easier, and to acknowledge the practice of some early5006 HTTP serversand clients.5001 many characteristics that differ from email; hence, HTTP has features 5002 that differ from MIME. These differences were carefully chosen to 5003 optimize performance over binary connections, to allow greater 5004 freedom in the use of new media types, to make date comparisons 5005 easier, and to acknowledge the practice of some early HTTP servers 5006 and clients. 5007 5007 5008 5008 This appendix describes specific areas where HTTP differs from MIME. -
draft-ietf-httpbis/latest/auth48/rfc7230.abdiff.txt
r2646 r2647 400 400 401 401 402 Section 2.4., paragraph 5:403 OLD:404 405 There are a wide variety of architectures and configurations of406 caches deployed across the World Wide Web and inside large407 organizations. These include national hierarchies of proxy caches to408 save transoceanic bandwidth, collaborative systems that broadcast or409 multicast cache entries, archives of pre-fetched cache entries for410 use in off-line or high-latency environments, and so on.411 412 NEW:413 414 There is a wide variety of architectures and configurations of caches415 deployed across the World Wide Web and inside large organizations.416 These include national hierarchies of proxy caches to save417 transoceanic bandwidth, collaborative systems that broadcast or418 multicast cache entries, archives of pre-fetched cache entries for419 use in off-line or high-latency environments, and so on.420 421 422 Section 2.5., paragraph 5:423 OLD:424 425 When a received protocol element is parsed, the recipient MUST be426 able to parse any value of reasonable length that is applicable to427 the recipient's role and matches the grammar defined by the428 corresponding ABNF rules. Note, however, that some received protocol429 elements might not be parsed. For example, an intermediary430 forwarding a message might parse a header-field into generic field-431 name and field-value components, but then forward the header field432 without further parsing inside the field-value.433 434 NEW:435 436 When a received protocol element is parsed, the recipient MUST be437 able to parse any value of reasonable length that is applicable to438 the recipient's role and that matches the grammar defined by the439 corresponding ABNF rules. Note, however, that some received protocol440 elements might not be parsed. For example, an intermediary441 forwarding a message might parse a header-field into generic field-442 name and field-value components, but then forward the header field443 without further parsing inside the field-value.444 445 446 402 Section 2.6., paragraph 2: 447 403 OLD: … … 582 538 583 539 584 Section 3.1., paragraph 1:585 OLD:586 587 An HTTP message can either be a request from client to server or a588 response from server to client. Syntactically, the two types of589 message differ only in the start-line, which is either a request-line590 (for requests) or a status-line (for responses), and in the algorithm591 for determining the length of the message body (Section 3.3).592 593 NEW:594 595 An HTTP message can be either a request from client to server or a596 response from server to client. Syntactically, the two types of597 message differ only in the start-line, which is either a request-line598 (for requests) or a status-line (for responses), and in the algorithm599 for determining the length of the message body (Section 3.3).600 601 602 540 Section 3.1., paragraph 2: 603 541 OLD: … … 725 663 processed). Consequently, this specification does not use ABNF rules 726 664 to define each "Field-Name: Field Value" pair, as was done in 727 previous editions. Instead, this specification uses ABNF rules which665 previous editions. Instead, this specification uses ABNF rules that 728 666 are named according to each registered field name, wherein the rule 729 667 defines the valid grammar for that field's corresponding field values … … 943 881 944 882 945 Section 6.3., paragraph 10:946 OLD:947 948 See Appendix A.1.2 for more information on backward compatibility949 with HTTP/1.0 clients.950 951 NEW:952 953 See Appendix A.1.2 for more information on backwards compatibility954 with HTTP/1.0 clients.955 956 957 Section 6.3.2., paragraph 1:958 OLD:959 960 A client that supports persistent connections MAY "pipeline" its961 requests (i.e., send multiple requests without waiting for each962 response). A server MAY process a sequence of pipelined requests in963 parallel if they all have safe methods (Section 4.2.1 of [RFC7231]),964 but MUST send the corresponding responses in the same order that the965 requests were received.966 967 NEW:968 969 A client that supports persistent connections MAY "pipeline" its970 requests (i.e., send multiple requests without waiting for each971 response). A server MAY process a sequence of pipelined requests in972 parallel if they all have safe methods (Section 4.2.1 of [RFC7231]),973 but it MUST send the corresponding responses in the same order that974 the requests were received.975 976 977 883 Section 6.5., paragraph 4: 978 884 OLD: … … 1122 1028 and is expected to do so without requiring the request to be 1123 1029 repeated). 1124 1125 1126 Section 101, paragraph 5:1127 OLD:1128 1129 A client cannot begin using an upgraded protocol on the connection1130 until it has completely sent the request message (i.e., the client1131 can't change the protocol it is sending in the middle of a message).1132 If a server receives both Upgrade and an Expect header field with the1133 "100-continue" expectation (Section 5.1.1 of [RFC7231]), the server1134 MUST send a 100 (Continue) response before sending a 101 (Switching1135 Protocols) response.1136 1137 NEW:1138 1139 A client cannot begin using an upgraded protocol on the connection1140 until it has completely sent the request message (i.e., the client1141 can't change the protocol it is sending in the middle of a message).1142 If a server receives both an Upgrade and an Expect header field with1143 the "100-continue" expectation (Section 5.1.1 of [RFC7231]), the1144 server MUST send a 100 (Continue) response before sending a 1011145 (Switching Protocols) response.1146 1030 1147 1031 … … 1444 1328 between a complete and incomplete response message (Section 3.4) when 1445 1329 such verification is desired. 1446 1447 1448 Section 9.8., paragraph 2:1449 OLD:1450 1451 HTTP log information is confidential in nature; its handling is often1452 constrained by laws and regulations. Log information needs to be1453 securely stored and appropriate guidelines followed for its analysis.1454 Anonymization of personal information within individual entries1455 helps, but is generally not sufficient to prevent real log traces1456 from being re-identified based on correlation with other access1457 characteristics. As such, access traces that are keyed to a specific1458 client are unsafe to publish even if the key is pseudonymous.1459 1460 NEW:1461 1462 HTTP log information is confidential in nature; its handling is often1463 constrained by laws and regulations. Log information needs to be1464 securely stored and appropriate guidelines followed for its analysis.1465 Anonymization of personal information within individual entries1466 helps, but it is generally not sufficient to prevent real log traces1467 from being re-identified based on correlation with other access1468 characteristics. As such, access traces that are keyed to a specific1469 client are unsafe to publish even if the key is pseudonymous.1470 1330 1471 1331 … … 1609 1469 1610 1470 1611 Appendix A., paragraph 2:1612 OLD:1613 1614 HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent1615 requirements that enable reliable implementations, adding only those1616 features that can either be safely ignored by an HTTP/1.0 recipient1617 or only sent when communicating with a party advertising conformance1618 with HTTP/1.1.1619 1620 NEW:1621 1622 HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent1623 requirements that enable reliable implementations, adding only those1624 features that can either be safely ignored by an HTTP/1.0 recipient1625 or only be sent when communicating with a party advertising1626 conformance with HTTP/1.1.1627 1628 1629 1471 Appendix A., paragraph 7: 1630 1472 OLD: … … 1651 1493 1652 1494 The HTTP-version ABNF production has been clarified to be case- 1653 sensitive. Additionally, version numbers ha sbeen restricted to1495 sensitive. Additionally, version numbers have been restricted to 1654 1496 single digits, due to the fact that implementations are known to 1655 1497 handle multi-digit version numbers incorrectly. (Section 2.6) -
draft-ietf-httpbis/latest/auth48/rfc7230.diff.html
r2646 r2647 263 263 <tr><td class="lineno" valign="top"></td><td class="left"> subsystem that controls its message storage, retrieval, and deletion.</td><td> </td><td class="right"> subsystem that controls its message storage, retrieval, and deletion.</td><td class="lineno" valign="top"></td></tr> 264 264 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 265 <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 12, line 8</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 12, line 11</em></th><td></td></tr> 266 <tr><td class="lineno" valign="top"></td><td class="left"> < <</td><td> </td><td class="right"> < <</td><td class="lineno" valign="top"></td></tr> 267 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 268 <tr><td class="lineno" valign="top"></td><td class="left"> A response is "cacheable" if a cache is allowed to store a copy of</td><td> </td><td class="right"> A response is "cacheable" if a cache is allowed to store a copy of</td><td class="lineno" valign="top"></td></tr> 269 <tr><td class="lineno" valign="top"></td><td class="left"> the response message for use in answering subsequent requests. Even</td><td> </td><td class="right"> the response message for use in answering subsequent requests. Even</td><td class="lineno" valign="top"></td></tr> 270 <tr><td class="lineno" valign="top"></td><td class="left"> when a response is cacheable, there might be additional constraints</td><td> </td><td class="right"> when a response is cacheable, there might be additional constraints</td><td class="lineno" valign="top"></td></tr> 271 <tr><td class="lineno" valign="top"></td><td class="left"> placed by the client or by the origin server on when that cached</td><td> </td><td class="right"> placed by the client or by the origin server on when that cached</td><td class="lineno" valign="top"></td></tr> 272 <tr><td class="lineno" valign="top"></td><td class="left"> response can be used for a particular request. HTTP requirements for</td><td> </td><td class="right"> response can be used for a particular request. HTTP requirements for</td><td class="lineno" valign="top"></td></tr> 273 <tr><td class="lineno" valign="top"></td><td class="left"> cache behavior and cacheable responses are defined in Section 2 of</td><td> </td><td class="right"> cache behavior and cacheable responses are defined in Section 2 of</td><td class="lineno" valign="top"></td></tr> 274 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7234].</td><td> </td><td class="right"> [RFC7234].</td><td class="lineno" valign="top"></td></tr> 275 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 276 <tr><td><a name="diff0015" /></td></tr> 277 <tr><td class="lineno" valign="top"></td><td class="lblock"> There <span class="delete">are</span> a wide variety of architectures and configurations of</td><td> </td><td class="rblock"> There <span class="insert">is</span> a wide variety of architectures and configurations of caches</td><td class="lineno" valign="top"></td></tr> 278 <tr><td class="lineno" valign="top"></td><td class="lblock"> caches deployed across the World Wide Web and inside large</td><td> </td><td class="rblock"> deployed across the World Wide Web and inside large organizations.</td><td class="lineno" valign="top"></td></tr> 279 <tr><td class="lineno" valign="top"></td><td class="lblock"> organizations. These include national hierarchies of proxy caches to</td><td> </td><td class="rblock"> These include national hierarchies of proxy caches to save</td><td class="lineno" valign="top"></td></tr> 280 <tr><td class="lineno" valign="top"></td><td class="lblock"> save transoceanic bandwidth, collaborative systems that broadcast or</td><td> </td><td class="rblock"> transoceanic bandwidth, collaborative systems that broadcast or</td><td class="lineno" valign="top"></td></tr> 281 <tr><td class="lineno" valign="top"></td><td class="left"> multicast cache entries, archives of pre-fetched cache entries for</td><td> </td><td class="right"> multicast cache entries, archives of pre-fetched cache entries for</td><td class="lineno" valign="top"></td></tr> 282 <tr><td class="lineno" valign="top"></td><td class="left"> use in off-line or high-latency environments, and so on.</td><td> </td><td class="right"> use in off-line or high-latency environments, and so on.</td><td class="lineno" valign="top"></td></tr> 283 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 284 <tr><td class="lineno" valign="top"></td><td class="left">2.5. Conformance and Error Handling</td><td> </td><td class="right">2.5. Conformance and Error Handling</td><td class="lineno" valign="top"></td></tr> 285 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 286 <tr><td class="lineno" valign="top"></td><td class="left"> This specification targets conformance criteria according to the role</td><td> </td><td class="right"> This specification targets conformance criteria according to the role</td><td class="lineno" valign="top"></td></tr> 287 <tr><td class="lineno" valign="top"></td><td class="left"> of a participant in HTTP communication. Hence, HTTP requirements are</td><td> </td><td class="right"> of a participant in HTTP communication. Hence, HTTP requirements are</td><td class="lineno" valign="top"></td></tr> 288 <tr><td class="lineno" valign="top"></td><td class="left"> placed on senders, recipients, clients, servers, user agents,</td><td> </td><td class="right"> placed on senders, recipients, clients, servers, user agents,</td><td class="lineno" valign="top"></td></tr> 289 <tr><td class="lineno" valign="top"></td><td class="left"> intermediaries, origin servers, proxies, gateways, or caches,</td><td> </td><td class="right"> intermediaries, origin servers, proxies, gateways, or caches,</td><td class="lineno" valign="top"></td></tr> 290 <tr><td class="lineno" valign="top"></td><td class="left"> depending on what behavior is being constrained by the requirement.</td><td> </td><td class="right"> depending on what behavior is being constrained by the requirement.</td><td class="lineno" valign="top"></td></tr> 291 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 292 <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 12, line 44</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 12, line 47</em></th><td></td></tr> 293 <tr><td class="lineno" valign="top"></td><td class="left"> elements. A sender MUST NOT generate protocol elements that convey a</td><td> </td><td class="right"> elements. A sender MUST NOT generate protocol elements that convey a</td><td class="lineno" valign="top"></td></tr> 294 <tr><td class="lineno" valign="top"></td><td class="left"> meaning that is known by that sender to be false. A sender MUST NOT</td><td> </td><td class="right"> meaning that is known by that sender to be false. A sender MUST NOT</td><td class="lineno" valign="top"></td></tr> 295 <tr><td class="lineno" valign="top"></td><td class="left"> generate protocol elements that do not match the grammar defined by</td><td> </td><td class="right"> generate protocol elements that do not match the grammar defined by</td><td class="lineno" valign="top"></td></tr> 296 <tr><td class="lineno" valign="top"></td><td class="left"> the corresponding ABNF rules. Within a given message, a sender MUST</td><td> </td><td class="right"> the corresponding ABNF rules. Within a given message, a sender MUST</td><td class="lineno" valign="top"></td></tr> 297 <tr><td class="lineno" valign="top"></td><td class="left"> NOT generate protocol elements or syntax alternatives that are only</td><td> </td><td class="right"> NOT generate protocol elements or syntax alternatives that are only</td><td class="lineno" valign="top"></td></tr> 298 <tr><td class="lineno" valign="top"></td><td class="left"> allowed to be generated by participants in other roles (i.e., a role</td><td> </td><td class="right"> allowed to be generated by participants in other roles (i.e., a role</td><td class="lineno" valign="top"></td></tr> 299 <tr><td class="lineno" valign="top"></td><td class="left"> that the sender does not have for that message).</td><td> </td><td class="right"> that the sender does not have for that message).</td><td class="lineno" valign="top"></td></tr> 300 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 301 <tr><td class="lineno" valign="top"></td><td class="left"> When a received protocol element is parsed, the recipient MUST be</td><td> </td><td class="right"> When a received protocol element is parsed, the recipient MUST be</td><td class="lineno" valign="top"></td></tr> 302 <tr><td class="lineno" valign="top"></td><td class="left"> able to parse any value of reasonable length that is applicable to</td><td> </td><td class="right"> able to parse any value of reasonable length that is applicable to</td><td class="lineno" valign="top"></td></tr> 303 <tr><td><a name="diff0016" /></td></tr> 304 <tr><td class="lineno" valign="top"></td><td class="lblock"> the recipient's role and matches the grammar defined by the</td><td> </td><td class="rblock"> the recipient's role and <span class="insert">that </span>matches the grammar defined by the</td><td class="lineno" valign="top"></td></tr> 305 <tr><td class="lineno" valign="top"></td><td class="left"> corresponding ABNF rules. Note, however, that some received protocol</td><td> </td><td class="right"> corresponding ABNF rules. Note, however, that some received protocol</td><td class="lineno" valign="top"></td></tr> 306 <tr><td class="lineno" valign="top"></td><td class="left"> elements might not be parsed. For example, an intermediary</td><td> </td><td class="right"> elements might not be parsed. For example, an intermediary</td><td class="lineno" valign="top"></td></tr> 307 <tr><td class="lineno" valign="top"></td><td class="left"> forwarding a message might parse a header-field into generic field-</td><td> </td><td class="right"> forwarding a message might parse a header-field into generic field-</td><td class="lineno" valign="top"></td></tr> 308 <tr><td class="lineno" valign="top"></td><td class="left"> name and field-value components, but then forward the header field</td><td> </td><td class="right"> name and field-value components, but then forward the header field</td><td class="lineno" valign="top"></td></tr> 309 <tr><td class="lineno" valign="top"></td><td class="left"> without further parsing inside the field-value.</td><td> </td><td class="right"> without further parsing inside the field-value.</td><td class="lineno" valign="top"></td></tr> 310 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 311 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP does not have specific length limitations for many of its</td><td> </td><td class="right"> HTTP does not have specific length limitations for many of its</td><td class="lineno" valign="top"></td></tr> 312 <tr><td class="lineno" valign="top"></td><td class="left"> protocol elements because the lengths that might be appropriate will</td><td> </td><td class="right"> protocol elements because the lengths that might be appropriate will</td><td class="lineno" valign="top"></td></tr> 313 <tr><td class="lineno" valign="top"></td><td class="left"> vary widely, depending on the deployment context and purpose of the</td><td> </td><td class="right"> vary widely, depending on the deployment context and purpose of the</td><td class="lineno" valign="top"></td></tr> 314 <tr><td class="lineno" valign="top"></td><td class="left"> implementation. Hence, interoperability between senders and</td><td> </td><td class="right"> implementation. Hence, interoperability between senders and</td><td class="lineno" valign="top"></td></tr> 315 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 316 <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 13, line 49</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 14, line 4</em></th><td></td></tr> 265 <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 13, line 49</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 14, line 4</em></th><td></td></tr> 317 266 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 318 267 <tr><td class="lineno" valign="top"></td><td class="left">2.6. Protocol Versioning</td><td> </td><td class="right">2.6. Protocol Versioning</td><td class="lineno" valign="top"></td></tr> … … 325 274 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 326 275 <tr><td class="lineno" valign="top"></td><td class="left"> The version of an HTTP message is indicated by an HTTP-version field</td><td> </td><td class="right"> The version of an HTTP message is indicated by an HTTP-version field</td><td class="lineno" valign="top"></td></tr> 327 <tr><td><a name="diff001 7" /></td></tr>276 <tr><td><a name="diff0015" /></td></tr> 328 277 <tr><td class="lineno" valign="top"></td><td class="lblock"> in the first line of the message. HTTP-version is case<span class="delete">-</span>sensitive.</td><td> </td><td class="rblock"> in the first line of the message. HTTP-version is case<span class="insert"> </span>sensitive.</td><td class="lineno" valign="top"></td></tr> 329 278 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 330 279 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP-version = HTTP-name "/" DIGIT "." DIGIT</td><td> </td><td class="right"> HTTP-version = HTTP-name "/" DIGIT "." DIGIT</td><td class="lineno" valign="top"></td></tr> 331 <tr><td><a name="diff001 8" /></td></tr>280 <tr><td><a name="diff0016" /></td></tr> 332 281 <tr><td class="lineno" valign="top"></td><td class="lblock"> HTTP-name = %x48.54.54.50 ; "HTTP", case<span class="delete">-</span>sensitive</td><td> </td><td class="rblock"> HTTP-name = %x48.54.54.50 ; "HTTP", case<span class="insert"> </span>sensitive</td><td class="lineno" valign="top"></td></tr> 333 282 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 342 291 <tr><td class="lineno" valign="top"></td><td class="left"> recipient know that more advanced features can be used in response</td><td> </td><td class="right"> recipient know that more advanced features can be used in response</td><td class="lineno" valign="top"></td></tr> 343 292 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 344 <tr bgcolor="gray" ><td></td><th><a name="part-l 11" /><small>skipping to change at</small><em> page 14, line 36</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 14, line 39</em></th><td></td></tr>293 <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 14, line 36</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 14, line 39</em></th><td></td></tr> 345 294 <tr><td class="lineno" valign="top"></td><td class="left"> The interpretation of a header field does not change between minor</td><td> </td><td class="right"> The interpretation of a header field does not change between minor</td><td class="lineno" valign="top"></td></tr> 346 295 <tr><td class="lineno" valign="top"></td><td class="left"> versions of the same major HTTP version, though the default behavior</td><td> </td><td class="right"> versions of the same major HTTP version, though the default behavior</td><td class="lineno" valign="top"></td></tr> … … 353 302 <tr><td class="lineno" valign="top"></td><td class="left"> New header fields can be introduced without changing the protocol</td><td> </td><td class="right"> New header fields can be introduced without changing the protocol</td><td class="lineno" valign="top"></td></tr> 354 303 <tr><td class="lineno" valign="top"></td><td class="left"> version if their defined semantics allow them to be safely ignored by</td><td> </td><td class="right"> version if their defined semantics allow them to be safely ignored by</td><td class="lineno" valign="top"></td></tr> 355 <tr><td><a name="diff001 9" /></td></tr>304 <tr><td><a name="diff0017" /></td></tr> 356 305 <tr><td class="lineno" valign="top"></td><td class="lblock"> recipients that do not recognize them. Header<span class="delete"> </span>field extensibility is</td><td> </td><td class="rblock"> recipients that do not recognize them. Header<span class="insert">-</span>field extensibility is</td><td class="lineno" valign="top"></td></tr> 357 306 <tr><td class="lineno" valign="top"></td><td class="left"> discussed in Section 3.2.1.</td><td> </td><td class="right"> discussed in Section 3.2.1.</td><td class="lineno" valign="top"></td></tr> … … 366 315 <tr><td class="lineno" valign="top"></td><td class="left"> version might result in communication errors when downstream</td><td> </td><td class="right"> version might result in communication errors when downstream</td><td class="lineno" valign="top"></td></tr> 367 316 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 368 <tr bgcolor="gray" ><td></td><th><a name="part-l1 2" /><small>skipping to change at</small><em> page 15, line 48</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 15, line 51</em></th><td></td></tr>317 <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 15, line 48</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 15, line 51</em></th><td></td></tr> 369 318 <tr><td class="lineno" valign="top"></td><td class="left"> introduced between [RFC2068] and [RFC2616], and this revision has</td><td> </td><td class="right"> introduced between [RFC2068] and [RFC2616], and this revision has</td><td class="lineno" valign="top"></td></tr> 370 319 <tr><td class="lineno" valign="top"></td><td class="left"> specifically avoided any such changes to the protocol.</td><td> </td><td class="right"> specifically avoided any such changes to the protocol.</td><td class="lineno" valign="top"></td></tr> … … 377 326 <tr><td class="lineno" valign="top"></td><td class="left"> message with a higher minor version, when sent to a recipient that</td><td> </td><td class="right"> message with a higher minor version, when sent to a recipient that</td><td class="lineno" valign="top"></td></tr> 378 327 <tr><td class="lineno" valign="top"></td><td class="left"> has not yet indicated support for that higher version, is</td><td> </td><td class="right"> has not yet indicated support for that higher version, is</td><td class="lineno" valign="top"></td></tr> 379 <tr><td><a name="diff00 20" /></td></tr>328 <tr><td><a name="diff0018" /></td></tr> 380 329 <tr><td class="lineno" valign="top"></td><td class="lblock"> sufficiently backwards<span class="delete">-</span>compatible to be safely processed by any</td><td> </td><td class="rblock"> sufficiently backwards<span class="insert"> </span>compatible to be safely processed by any</td><td class="lineno" valign="top"></td></tr> 381 330 <tr><td class="lineno" valign="top"></td><td class="left"> implementation of the same major version.</td><td> </td><td class="right"> implementation of the same major version.</td><td class="lineno" valign="top"></td></tr> … … 393 342 <tr><td class="lineno" valign="top"></td><td class="left"> "absolute-path" rule is defined for protocol elements that can</td><td> </td><td class="right"> "absolute-path" rule is defined for protocol elements that can</td><td class="lineno" valign="top"></td></tr> 394 343 <tr><td class="lineno" valign="top"></td><td class="left"> contain a non-empty path component. (This rule differs slightly from</td><td> </td><td class="right"> contain a non-empty path component. (This rule differs slightly from</td><td class="lineno" valign="top"></td></tr> 395 <tr><td><a name="diff00 21" /></td></tr>344 <tr><td><a name="diff0019" /></td></tr> 396 345 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">RFC 3986's</span> path-abempty <span class="delete">rule,</span> which allows for an empty path to be</td><td> </td><td class="rblock"> <span class="insert">the</span> path-abempty <span class="insert">rule of RFC 3986,</span> which allows for an empty path to</td><td class="lineno" valign="top"></td></tr> 397 346 <tr><td class="lineno" valign="top"></td><td class="lblock"> used in references, and path-absolute rule, which does not allow</td><td> </td><td class="rblock"> be used in references, and path-absolute rule, which does not allow</td><td class="lineno" valign="top"></td></tr> … … 407 356 <tr><td class="lineno" valign="top"></td><td class="left"> uri-host = <host, defined in [RFC3986], Section 3.2.2></td><td> </td><td class="right"> uri-host = <host, defined in [RFC3986], Section 3.2.2></td><td class="lineno" valign="top"></td></tr> 408 357 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 409 <tr bgcolor="gray" ><td></td><th><a name="part-l1 3" /><small>skipping to change at</small><em> page 16, line 50</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 16, line 50</em></th><td></td></tr>358 <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 16, line 50</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 16, line 50</em></th><td></td></tr> 410 359 <tr><td class="lineno" valign="top"></td><td class="left"> of reference (URI-reference), only a URI in absolute form (absolute-</td><td> </td><td class="right"> of reference (URI-reference), only a URI in absolute form (absolute-</td><td class="lineno" valign="top"></td></tr> 411 360 <tr><td class="lineno" valign="top"></td><td class="left"> URI), only the path and optional query components, or some</td><td> </td><td class="right"> URI), only the path and optional query components, or some</td><td class="lineno" valign="top"></td></tr> … … 418 367 <tr><td class="lineno" valign="top"></td><td class="left"> identifiers according to their association with the hierarchical</td><td> </td><td class="right"> identifiers according to their association with the hierarchical</td><td class="lineno" valign="top"></td></tr> 419 368 <tr><td class="lineno" valign="top"></td><td class="left"> namespace governed by a potential HTTP origin server listening for</td><td> </td><td class="right"> namespace governed by a potential HTTP origin server listening for</td><td class="lineno" valign="top"></td></tr> 420 <tr><td><a name="diff002 2" /></td></tr>369 <tr><td><a name="diff0020" /></td></tr> 421 370 <tr><td class="lineno" valign="top"></td><td class="lblock"> TCP ([RFC<span class="delete">0</span>793]) connections on a given port.</td><td> </td><td class="rblock"> TCP ([RFC793]) connections on a given port.</td><td class="lineno" valign="top"></td></tr> 422 371 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 431 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> 432 381 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 433 <tr bgcolor="gray" ><td></td><th><a name="part-l1 4" /><small>skipping to change at</small><em> page 18, line 44</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 18, line 44</em></th><td></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> 434 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> 435 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> … … 442 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> 443 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> 444 <tr><td><a name="diff002 3" /></td></tr>393 <tr><td><a name="diff0021" /></td></tr> 445 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> 446 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> … … 455 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> 456 405 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 457 <tr bgcolor="gray" ><td></td><th><a name="part-l1 5" /><small>skipping to change at</small><em> page 19, line 18</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 19, line 18</em></th><td></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> 458 407 <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> 459 408 <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> … … 466 415 <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> 467 416 <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> 468 <tr><td><a name="diff002 4" /></td></tr>417 <tr><td><a name="diff0022" /></td></tr> 469 418 <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> 470 419 <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> … … 479 428 <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> 480 429 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 481 <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 20, line 37</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 20, line 37</em></th><td></td></tr> 482 <tr><td class="lineno" valign="top"></td><td class="left"> The presence of such whitespace in a request might be an attempt to</td><td> </td><td class="right"> The presence of such whitespace in a request might be an attempt to</td><td class="lineno" valign="top"></td></tr> 483 <tr><td class="lineno" valign="top"></td><td class="left"> trick a server into ignoring that field or processing the line after</td><td> </td><td class="right"> trick a server into ignoring that field or processing the line after</td><td class="lineno" valign="top"></td></tr> 484 <tr><td class="lineno" valign="top"></td><td class="left"> it as a new request, either of which might result in a security</td><td> </td><td class="right"> it as a new request, either of which might result in a security</td><td class="lineno" valign="top"></td></tr> 485 <tr><td class="lineno" valign="top"></td><td class="left"> vulnerability if other implementations within the request chain</td><td> </td><td class="right"> vulnerability if other implementations within the request chain</td><td class="lineno" valign="top"></td></tr> 486 <tr><td class="lineno" valign="top"></td><td class="left"> interpret the same message differently. Likewise, the presence of</td><td> </td><td class="right"> interpret the same message differently. Likewise, the presence of</td><td class="lineno" valign="top"></td></tr> 487 <tr><td class="lineno" valign="top"></td><td class="left"> such whitespace in a response might be ignored by some clients or</td><td> </td><td class="right"> such whitespace in a response might be ignored by some clients or</td><td class="lineno" valign="top"></td></tr> 488 <tr><td class="lineno" valign="top"></td><td class="left"> cause others to cease parsing.</td><td> </td><td class="right"> cause others to cease parsing.</td><td class="lineno" valign="top"></td></tr> 489 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 430 <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><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> 490 431 <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> 491 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> 492 <tr><td><a name="diff0025" /></td></tr> 493 <tr><td class="lineno" valign="top"></td><td class="lblock"> An HTTP message can <span class="delete">either be</span> a request from client to server or a</td><td> </td><td class="rblock"> An HTTP message can <span class="insert">be either</span> a request from client to server or a</td><td class="lineno" valign="top"></td></tr> 433 <tr><td class="lineno" valign="top"></td><td class="left"> An HTTP message can be either a request from client to server or a</td><td> </td><td class="right"> An HTTP message can be either a request from client to server or a</td><td class="lineno" valign="top"></td></tr> 494 434 <tr><td class="lineno" valign="top"></td><td class="left"> response from server to client. Syntactically, the two types of</td><td> </td><td class="right"> response from server to client. Syntactically, the two types of</td><td class="lineno" valign="top"></td></tr> 495 435 <tr><td class="lineno" valign="top"></td><td class="left"> message differ only in the start-line, which is either a request-line</td><td> </td><td class="right"> message differ only in the start-line, which is either a request-line</td><td class="lineno" valign="top"></td></tr> … … 499 439 <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> 500 440 <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> 501 <tr><td><a name="diff002 6" /></td></tr>441 <tr><td><a name="diff0023" /></td></tr> 502 442 <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> 503 443 <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> … … 508 448 <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> 509 449 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 510 <tr><td><a name="diff002 7" /></td></tr>450 <tr><td><a name="diff0024" /></td></tr> 511 451 <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> 512 452 <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> … … 516 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> 517 457 <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> 518 <tr><td><a name="diff002 8" /></td></tr>458 <tr><td><a name="diff0025" /></td></tr> 519 459 <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> 520 460 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 529 469 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 530 470 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 531 <tr bgcolor="gray" ><td></td><th><a name="part-l1 7" /><small>skipping to change at</small><em> page 22, line 8</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 22, line 8</em></th><td></td></tr>471 <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><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> 532 472 <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> 533 473 <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> … … 540 480 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 541 481 <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> 542 <tr><td><a name="diff002 9" /></td></tr>482 <tr><td><a name="diff0026" /></td></tr> 543 483 <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> 544 484 <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> … … 555 495 <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> 556 496 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 557 <tr bgcolor="gray" ><td></td><th><a name="part-l1 8" /><small>skipping to change at</small><em> page 23, line 29</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 23, line 29</em></th><td></td></tr>497 <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><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> 558 498 <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> 559 499 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 566 506 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 567 507 <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> 568 <tr><td><a name="diff00 30" /></td></tr>508 <tr><td><a name="diff0027" /></td></tr> 569 509 <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> 570 510 <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> … … 579 519 <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> 580 520 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 581 <tr bgcolor="gray" ><td></td><th><a name="part-l1 9" /><small>skipping to change at</small><em> page 24, line 14</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 24, line 14</em></th><td></td></tr>521 <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><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> 582 522 <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> 583 523 <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> … … 590 530 <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> 591 531 <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> 592 <tr><td><a name="diff00 31" /></td></tr>532 <tr><td><a name="diff0028" /></td></tr> 593 533 <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> 594 534 <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> … … 605 545 <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> 606 546 <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> 607 <tr><td><a name="diff00 32" /></td></tr>547 <tr><td><a name="diff0029" /></td></tr> 608 548 <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> 609 549 <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> … … 618 558 <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> 619 559 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 620 <tr bgcolor="gray" ><td></td><th><a name="part-l 20" /><small>skipping to change at</small><em> page 25, line 12</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 25, line 12</em></th><td></td></tr>560 <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><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> 621 561 <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> 622 562 <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> … … 629 569 <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> 630 570 <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> 631 <tr><td><a name="diff003 3" /></td></tr>632 <tr><td class="lineno" valign="top"></td><td class="lblock"> to define each <span class="delete">"Field-Name: Field Value"</span> pair, as was done in</td><td> </td><td class="rblock"> to define each <span class="insert">"field-name: field-value"</span>pair, as was done in</td><td class="lineno" valign="top"></td></tr>633 <tr><td class="lineno" valign="top"></td><td class="l block"> previous editions. Instead, this specification uses ABNF rules <span class="delete">which</span></td><td> </td><td class="rblock"> previous editions. Instead, this specification uses ABNF rules <span class="insert">that</span></td><td class="lineno" valign="top"></td></tr>571 <tr><td><a name="diff0030" /></td></tr> 572 <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 <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> 634 574 <tr><td class="lineno" valign="top"></td><td class="left"> are named according to each registered field name, wherein the rule</td><td> </td><td class="right"> are named according to each registered field name, wherein the rule</td><td class="lineno" valign="top"></td></tr> 635 575 <tr><td class="lineno" valign="top"></td><td class="left"> defines the valid grammar for that field's corresponding field values</td><td> </td><td class="right"> defines the valid grammar for that field's corresponding field values</td><td class="lineno" valign="top"></td></tr> … … 641 581 <tr><td class="lineno" valign="top"></td><td class="left"> security vulnerabilities in request routing and response handling. A</td><td> </td><td class="right"> security vulnerabilities in request routing and response handling. A</td><td class="lineno" valign="top"></td></tr> 642 582 <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> 643 <tr><td class="lineno" valign="top"></td><td class="left"> whitespace between a header field-name and colon with a response code</td><td> </td><td class="right"> whitespace between a header field-name and colon with a response code</td><td class="lineno" valign="top"></td></tr> 644 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 645 <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><small>skipping to change at</small><em> page 26, line 15</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 26, line 15</em></th><td></td></tr> 583 <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-l19" /><small>skipping to change at</small><em> page 26, line 15</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 26, line 15</em></th><td></td></tr> 646 585 <tr><td class="lineno" valign="top"></td><td class="left"> with a representation explaining that unacceptable line folding was</td><td> </td><td class="right"> with a representation explaining that unacceptable line folding was</td><td class="lineno" valign="top"></td></tr> 647 586 <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> … … 654 593 <tr><td class="lineno" valign="top"></td><td class="left"> value.</td><td> </td><td class="right"> value.</td><td class="lineno" valign="top"></td></tr> 655 594 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 656 <tr><td><a name="diff003 4" /></td></tr>595 <tr><td><a name="diff0031" /></td></tr> 657 596 <tr><td class="lineno" valign="top"></td><td class="lblock"> Historically, HTTP has allowed field content with text in the <span class="delete">ISO-</span></td><td> </td><td class="rblock"> Historically, HTTP has allowed field content with text in the</td><td class="lineno" valign="top"></td></tr> 658 597 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> 8859-1</span> [ISO-8859-1] charset, supporting other charsets only through</td><td> </td><td class="rblock"> <span class="insert">ISO-8859-1</span> [ISO-8859-1] charset, supporting other charsets only</td><td class="lineno" valign="top"></td></tr> … … 673 612 <tr><td class="lineno" valign="top"></td><td class="left"> A server that receives a request header field, or set of fields,</td><td> </td><td class="right"> A server that receives a request header field, or set of fields,</td><td class="lineno" valign="top"></td></tr> 674 613 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 675 <tr bgcolor="gray" ><td></td><th><a name="part-l2 2" /><small>skipping to change at</small><em> page 33, line 6</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 33, line 6</em></th><td></td></tr>614 <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><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> 676 615 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 677 616 <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> … … 684 623 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 685 624 <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> 686 <tr><td><a name="diff003 5" /></td></tr>625 <tr><td><a name="diff0032" /></td></tr> 687 626 <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> 688 627 <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> … … 697 636 <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> 698 637 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 699 <tr bgcolor="gray" ><td></td><th><a name="part-l2 3" /><small>skipping to change at</small><em> page 35, line 26</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 35, line 26</em></th><td></td></tr>638 <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><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> 700 639 <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> 701 640 <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> … … 708 647 <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> 709 648 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 710 <tr><td><a name="diff003 6" /></td></tr>649 <tr><td><a name="diff0033" /></td></tr> 711 650 <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> 712 651 <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> … … 722 661 <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> 723 662 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 724 <tr bgcolor="gray" ><td></td><th><a name="part-l2 4" /><small>skipping to change at</small><em> page 38, line 28</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 38, line 28</em></th><td></td></tr>663 <tr bgcolor="gray" ><td></td><th><a name="part-l22" /><small>skipping to change at</small><em> page 38, line 28</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 38, line 28</em></th><td></td></tr> 725 664 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 726 665 <tr><td class="lineno" valign="top"></td><td class="left"> The "deflate" coding is a "zlib" data format [RFC1950] containing a</td><td> </td><td class="right"> The "deflate" coding is a "zlib" data format [RFC1950] containing a</td><td class="lineno" valign="top"></td></tr> … … 733 672 <tr><td class="lineno" valign="top"></td><td class="left">4.2.3. Gzip Coding</td><td> </td><td class="right">4.2.3. Gzip Coding</td><td class="lineno" valign="top"></td></tr> 734 673 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 735 <tr><td><a name="diff003 7" /></td></tr>674 <tr><td><a name="diff0034" /></td></tr> 736 675 <tr><td class="lineno" valign="top"></td><td class="lblock"> The "gzip" coding is an LZ77 coding with a <span class="delete">32 bit CRC</span> that is</td><td> </td><td class="rblock"> The "gzip" coding is an LZ77 coding with a <span class="insert">32-bit Cyclic Redundancy</span></td><td class="lineno" valign="top"></td></tr> 737 676 <tr><td class="lineno" valign="top"></td><td class="lblock"> commonly produced by the gzip file compression program [RFC1952]. A</td><td> </td><td class="rblock"><span class="insert"> Check (CRC)</span> that is commonly produced by the gzip file compression</td><td class="lineno" valign="top"></td></tr> … … 749 688 <tr><td class="lineno" valign="top"></td><td class="left"> coding names, each allowing for optional parameters (as described in</td><td> </td><td class="right"> coding names, each allowing for optional parameters (as described in</td><td class="lineno" valign="top"></td></tr> 750 689 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 751 <tr bgcolor="gray" ><td></td><th><a name="part-l2 5" /><small>skipping to change at</small><em> page 49, line 29</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 49, line 29</em></th><td></td></tr>690 <tr bgcolor="gray" ><td></td><th><a name="part-l23" /><small>skipping to change at</small><em> page 49, line 29</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 49, line 29</em></th><td></td></tr> 752 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> 753 692 <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> … … 760 699 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 761 700 <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> 762 <tr><td><a name="diff003 8" /></td></tr>701 <tr><td><a name="diff0035" /></td></tr> 763 702 <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> 764 703 <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> 765 704 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 766 705 <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> 767 <tr><td><a name="diff003 9" /></td></tr>706 <tr><td><a name="diff0036" /></td></tr> 768 707 <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> 769 708 <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> … … 775 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> 776 715 <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> 777 <tr><td><a name="diff00 40" /></td></tr>716 <tr><td><a name="diff0037" /></td></tr> 778 717 <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> 779 718 <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> … … 783 722 <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> 784 723 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 785 <tr><td><a name="diff00 41" /></td></tr>724 <tr><td><a name="diff0038" /></td></tr> 786 725 <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> 787 726 <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> … … 797 736 <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> 798 737 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 799 <tr bgcolor="gray" ><td></td><th><a name="part-l2 6" /><small>skipping to change at</small><em> page 51, line 8</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 51, line 8</em></th><td></td></tr>738 <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 51, line 8</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 51, line 8</em></th><td></td></tr> 800 739 <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> 801 740 <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> … … 808 747 <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> 809 748 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 810 <tr><td><a name="diff00 42" /></td></tr>749 <tr><td><a name="diff0039" /></td></tr> 811 750 <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> 812 751 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 821 760 <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> 822 761 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 823 <tr bgcolor="gray" ><td></td><th><a name="part-l2 7" /><small>skipping to change at</small><em> page 51, line 51</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 51, line 51</em></th><td></td></tr>762 <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 51, line 51</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 51, line 51</em></th><td></td></tr> 824 763 <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> 825 764 <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> … … 832 771 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 833 772 <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> 834 <tr><td><a name="diff004 3" /></td></tr>773 <tr><td><a name="diff0040" /></td></tr> 835 774 <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> 836 775 <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> … … 840 779 <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> 841 780 <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> 842 <tr><td><a name="diff004 4" /></td></tr>781 <tr><td><a name="diff0041" /></td></tr> 843 782 <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> 844 783 <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> … … 849 788 <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> 850 789 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 851 <tr><td><a name="diff004 5" /></td></tr>790 <tr><td><a name="diff0042" /></td></tr> 852 791 <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> 853 792 <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> … … 864 803 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 865 804 <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> 866 <tr><td><a name="diff004 6" /></td></tr>805 <tr><td><a name="diff0043" /></td></tr> 867 806 <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> 868 807 <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> … … 876 815 <tr><td class="lineno" valign="top"></td><td class="left"> client MUST read the entire response message body if it intends to</td><td> </td><td class="right"> client MUST read the entire response message body if it intends to</td><td class="lineno" valign="top"></td></tr> 877 816 <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> 878 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 879 <tr><td class="lineno" valign="top"></td><td class="left"> A proxy server MUST NOT maintain a persistent connection with an</td><td> </td><td class="right"> A proxy server MUST NOT maintain a persistent connection with an</td><td class="lineno" valign="top"></td></tr> 880 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP/1.0 client (see Section 19.7.1 of [RFC2068] for information and</td><td> </td><td class="right"> HTTP/1.0 client (see Section 19.7.1 of [RFC2068] for information and</td><td class="lineno" valign="top"></td></tr> 881 <tr><td class="lineno" valign="top"></td><td class="left"> discussion of the problems with the Keep-Alive header field</td><td> </td><td class="right"> discussion of the problems with the Keep-Alive header field</td><td class="lineno" valign="top"></td></tr> 882 <tr><td class="lineno" valign="top"></td><td class="left"> implemented by many HTTP/1.0 clients).</td><td> </td><td class="right"> implemented by many HTTP/1.0 clients).</td><td class="lineno" valign="top"></td></tr> 883 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 884 <tr><td><a name="diff0047" /></td></tr> 885 <tr><td class="lineno" valign="top"></td><td class="lblock"> See Appendix A.1.2 for more information on backward compatibility</td><td> </td><td class="rblock"> See Appendix A.1.2 for more information on backward<span class="insert">s</span> compatibility</td><td class="lineno" valign="top"></td></tr> 886 <tr><td class="lineno" valign="top"></td><td class="left"> with HTTP/1.0 clients.</td><td> </td><td class="right"> with HTTP/1.0 clients.</td><td class="lineno" valign="top"></td></tr> 887 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 888 <tr><td class="lineno" valign="top"></td><td class="left">6.3.1. Retrying Requests</td><td> </td><td class="right">6.3.1. Retrying Requests</td><td class="lineno" valign="top"></td></tr> 889 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 890 <tr><td class="lineno" valign="top"></td><td class="left"> Connections can be closed at any time, with or without intention.</td><td> </td><td class="right"> Connections can be closed at any time, with or without intention.</td><td class="lineno" valign="top"></td></tr> 891 <tr><td class="lineno" valign="top"></td><td class="left"> Implementations ought to anticipate the need to recover from</td><td> </td><td class="right"> Implementations ought to anticipate the need to recover from</td><td class="lineno" valign="top"></td></tr> 892 <tr><td class="lineno" valign="top"></td><td class="left"> asynchronous close events.</td><td> </td><td class="right"> asynchronous close events.</td><td class="lineno" valign="top"></td></tr> 893 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 894 <tr><td class="lineno" valign="top"></td><td class="left"> When an inbound connection is closed prematurely, a client MAY open a</td><td> </td><td class="right"> When an inbound connection is closed prematurely, a client MAY open a</td><td class="lineno" valign="top"></td></tr> 895 <tr><td class="lineno" valign="top"></td><td class="left"> new connection and automatically retransmit an aborted sequence of</td><td> </td><td class="right"> new connection and automatically retransmit an aborted sequence of</td><td class="lineno" valign="top"></td></tr> 896 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 897 <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 53, line 38</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 53, line 38</em></th><td></td></tr> 898 <tr><td class="lineno" valign="top"></td><td class="left"> the requests that failed.</td><td> </td><td class="right"> the requests that failed.</td><td class="lineno" valign="top"></td></tr> 899 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 900 <tr><td class="lineno" valign="top"></td><td class="left"> A client SHOULD NOT automatically retry a failed automatic retry.</td><td> </td><td class="right"> A client SHOULD NOT automatically retry a failed automatic retry.</td><td class="lineno" valign="top"></td></tr> 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> 902 <tr><td class="lineno" valign="top"></td><td class="left">6.3.2. Pipelining</td><td> </td><td class="right">6.3.2. Pipelining</td><td class="lineno" valign="top"></td></tr> 903 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 904 <tr><td class="lineno" valign="top"></td><td class="left"> A client that supports persistent connections MAY "pipeline" its</td><td> </td><td class="right"> A client that supports persistent connections MAY "pipeline" its</td><td class="lineno" valign="top"></td></tr> 905 <tr><td class="lineno" valign="top"></td><td class="left"> requests (i.e., send multiple requests without waiting for each</td><td> </td><td class="right"> requests (i.e., send multiple requests without waiting for each</td><td class="lineno" valign="top"></td></tr> 906 <tr><td class="lineno" valign="top"></td><td class="left"> response). A server MAY process a sequence of pipelined requests in</td><td> </td><td class="right"> response). A server MAY process a sequence of pipelined requests in</td><td class="lineno" valign="top"></td></tr> 907 <tr><td class="lineno" valign="top"></td><td class="left"> parallel if they all have safe methods (Section 4.2.1 of [RFC7231]),</td><td> </td><td class="right"> parallel if they all have safe methods (Section 4.2.1 of [RFC7231]),</td><td class="lineno" valign="top"></td></tr> 908 <tr><td><a name="diff0048" /></td></tr> 909 <tr><td class="lineno" valign="top"></td><td class="lblock"> but MUST send the corresponding responses in the same order that the</td><td> </td><td class="rblock"> but <span class="insert">it</span> MUST send the corresponding responses in the same order that</td><td class="lineno" valign="top"></td></tr> 910 <tr><td class="lineno" valign="top"></td><td class="lblock"> requests were received.</td><td> </td><td class="rblock"> the requests were received.</td><td class="lineno" valign="top"></td></tr> 911 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 912 <tr><td class="lineno" valign="top"></td><td class="left"> A client that pipelines requests SHOULD retry unanswered requests if</td><td> </td><td class="right"> A client that pipelines requests SHOULD retry unanswered requests if</td><td class="lineno" valign="top"></td></tr> 913 <tr><td class="lineno" valign="top"></td><td class="left"> the connection closes before it receives all of the corresponding</td><td> </td><td class="right"> the connection closes before it receives all of the corresponding</td><td class="lineno" valign="top"></td></tr> 914 <tr><td class="lineno" valign="top"></td><td class="left"> responses. When retrying pipelined requests after a failed</td><td> </td><td class="right"> responses. When retrying pipelined requests after a failed</td><td class="lineno" valign="top"></td></tr> 915 <tr><td class="lineno" valign="top"></td><td class="left"> connection (a connection not explicitly closed by the server in its</td><td> </td><td class="right"> connection (a connection not explicitly closed by the server in its</td><td class="lineno" valign="top"></td></tr> 916 <tr><td class="lineno" valign="top"></td><td class="left"> last complete response), a client MUST NOT pipeline immediately after</td><td> </td><td class="right"> last complete response), a client MUST NOT pipeline immediately after</td><td class="lineno" valign="top"></td></tr> 917 <tr><td class="lineno" valign="top"></td><td class="left"> connection establishment, since the first remaining request in the</td><td> </td><td class="right"> connection establishment, since the first remaining request in the</td><td class="lineno" valign="top"></td></tr> 918 <tr><td class="lineno" valign="top"></td><td class="left"> prior pipeline might have caused an error response that can be lost</td><td> </td><td class="right"> prior pipeline might have caused an error response that can be lost</td><td class="lineno" valign="top"></td></tr> 919 <tr><td class="lineno" valign="top"></td><td class="left"> again if multiple requests are sent on a prematurely closed</td><td> </td><td class="right"> again if multiple requests are sent on a prematurely closed</td><td class="lineno" valign="top"></td></tr> 920 <tr><td class="lineno" valign="top"></td><td class="left"> connection (see the TCP reset problem described in Section 6.6).</td><td> </td><td class="right"> connection (see the TCP reset problem described in Section 6.6).</td><td class="lineno" valign="top"></td></tr> 921 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 922 <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 55, line 19</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 55, line 19</em></th><td></td></tr> 817 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 818 <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 55, line 19</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 55, line 19</em></th><td></td></tr> 923 819 <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> 924 820 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 931 827 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 932 828 <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> 933 <tr><td><a name="diff004 9" /></td></tr>829 <tr><td><a name="diff0044" /></td></tr> 934 830 <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> 935 831 <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> … … 944 840 <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> 945 841 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 946 <tr><td><a name="diff00 50" /></td></tr>842 <tr><td><a name="diff0045" /></td></tr> 947 843 <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> 948 844 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 951 847 <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> 952 848 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 953 <tr><td><a name="diff00 51" /></td></tr>849 <tr><td><a name="diff0046" /></td></tr> 954 850 <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> 955 851 <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> … … 957 853 <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> 958 854 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 959 <tr><td><a name="diff00 52" /></td></tr>855 <tr><td><a name="diff0047" /></td></tr> 960 856 <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> 961 857 <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> … … 965 861 <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> 966 862 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 967 <tr><td><a name="diff00 53" /></td></tr>863 <tr><td><a name="diff0048" /></td></tr> 968 864 <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> 969 865 <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> … … 971 867 <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> 972 868 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 973 <tr><td><a name="diff00 54" /></td></tr>869 <tr><td><a name="diff0049" /></td></tr> 974 870 <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> 975 871 <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> … … 981 877 <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> 982 878 <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> 983 <tr><td><a name="diff005 5" /></td></tr>879 <tr><td><a name="diff0050" /></td></tr> 984 880 <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> 985 881 <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> … … 994 890 <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> 995 891 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 996 <tr bgcolor="gray" ><td></td><th><a name="part-l 30" /><small>skipping to change at</small><em> page 57, line 31</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 57, line 31</em></th><td></td></tr>892 <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 57, line 31</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 57, line 31</em></th><td></td></tr> 997 893 <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> 998 894 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1005 901 <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> 1006 902 <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> 1007 <tr><td><a name="diff005 6" /></td></tr>903 <tr><td><a name="diff0051" /></td></tr> 1008 904 <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> 1009 905 <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> … … 1023 919 <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> 1024 920 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1025 <tr bgcolor="gray" ><td></td><th><a name="part-l31" /><small>skipping to change at</small><em> page 58, line 25</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 58, line 25</em></th><td></td></tr> 1026 <tr><td class="lineno" valign="top"></td><td class="left"> When Upgrade is sent, the sender MUST also send a Connection header</td><td> </td><td class="right"> When Upgrade is sent, the sender MUST also send a Connection header</td><td class="lineno" valign="top"></td></tr> 1027 <tr><td class="lineno" valign="top"></td><td class="left"> field (Section 6.1) that contains an "upgrade" connection option, in</td><td> </td><td class="right"> field (Section 6.1) that contains an "upgrade" connection option, in</td><td class="lineno" valign="top"></td></tr> 1028 <tr><td class="lineno" valign="top"></td><td class="left"> order to prevent Upgrade from being accidentally forwarded by</td><td> </td><td class="right"> order to prevent Upgrade from being accidentally forwarded by</td><td class="lineno" valign="top"></td></tr> 1029 <tr><td class="lineno" valign="top"></td><td class="left"> intermediaries that might not implement the listed protocols. A</td><td> </td><td class="right"> intermediaries that might not implement the listed protocols. A</td><td class="lineno" valign="top"></td></tr> 1030 <tr><td class="lineno" valign="top"></td><td class="left"> server MUST ignore an Upgrade header field that is received in an</td><td> </td><td class="right"> server MUST ignore an Upgrade header field that is received in an</td><td class="lineno" valign="top"></td></tr> 1031 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP/1.0 request.</td><td> </td><td class="right"> HTTP/1.0 request.</td><td class="lineno" valign="top"></td></tr> 1032 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1033 <tr><td class="lineno" valign="top"></td><td class="left"> A client cannot begin using an upgraded protocol on the connection</td><td> </td><td class="right"> A client cannot begin using an upgraded protocol on the connection</td><td class="lineno" valign="top"></td></tr> 1034 <tr><td class="lineno" valign="top"></td><td class="left"> until it has completely sent the request message (i.e., the client</td><td> </td><td class="right"> until it has completely sent the request message (i.e., the client</td><td class="lineno" valign="top"></td></tr> 1035 <tr><td class="lineno" valign="top"></td><td class="left"> can't change the protocol it is sending in the middle of a message).</td><td> </td><td class="right"> can't change the protocol it is sending in the middle of a message).</td><td class="lineno" valign="top"></td></tr> 1036 <tr><td><a name="diff0057" /></td></tr> 1037 <tr><td class="lineno" valign="top"></td><td class="lblock"> If a server receives both Upgrade and an Expect header field with the</td><td> </td><td class="rblock"> If a server receives both <span class="insert">an</span> Upgrade and an Expect header field with</td><td class="lineno" valign="top"></td></tr> 1038 <tr><td class="lineno" valign="top"></td><td class="lblock"> "100-continue" expectation (Section 5.1.1 of [RFC7231]), the server</td><td> </td><td class="rblock"> the "100-continue" expectation (Section 5.1.1 of [RFC7231]), the</td><td class="lineno" valign="top"></td></tr> 1039 <tr><td class="lineno" valign="top"></td><td class="lblock"> MUST send a 100 (Continue) response before sending a 101 (Switching</td><td> </td><td class="rblock"> server MUST send a 100 (Continue) response before sending a 101</td><td class="lineno" valign="top"></td></tr> 1040 <tr><td class="lineno" valign="top"></td><td class="lblock"> Protocols) response.</td><td> </td><td class="rblock"> (Switching Protocols) response.</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"> The Upgrade header field only applies to switching protocols on top</td><td> </td><td class="right"> The Upgrade header field only applies to switching protocols on top</td><td class="lineno" valign="top"></td></tr> 1043 <tr><td class="lineno" valign="top"></td><td class="left"> of the existing connection; it cannot be used to switch the</td><td> </td><td class="right"> of the existing connection; it cannot be used to switch the</td><td class="lineno" valign="top"></td></tr> 1044 <tr><td class="lineno" valign="top"></td><td class="left"> underlying connection (transport) protocol, nor to switch the</td><td> </td><td class="right"> underlying connection (transport) protocol, nor to switch the</td><td class="lineno" valign="top"></td></tr> 1045 <tr><td class="lineno" valign="top"></td><td class="left"> existing communication to a different connection. For those</td><td> </td><td class="right"> existing communication to a different connection. For those</td><td class="lineno" valign="top"></td></tr> 1046 <tr><td class="lineno" valign="top"></td><td class="left"> purposes, it is more appropriate to use a 3xx (Redirection) response</td><td> </td><td class="right"> purposes, it is more appropriate to use a 3xx (Redirection) response</td><td class="lineno" valign="top"></td></tr> 1047 <tr><td class="lineno" valign="top"></td><td class="left"> (Section 6.4 of [RFC7231]).</td><td> </td><td class="right"> (Section 6.4 of [RFC7231]).</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"> This specification only defines the protocol name "HTTP" for use by</td><td> </td><td class="right"> This specification only defines the protocol name "HTTP" for use by</td><td class="lineno" valign="top"></td></tr> 1050 <tr><td class="lineno" valign="top"></td><td class="left"> the family of Hypertext Transfer Protocols, as defined by the HTTP</td><td> </td><td class="right"> the family of Hypertext Transfer Protocols, as defined by the HTTP</td><td class="lineno" valign="top"></td></tr> 1051 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1052 <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 59, line 35</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 59, line 35</em></th><td></td></tr> 921 <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 59, line 35</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 59, line 35</em></th><td></td></tr> 1053 922 <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> 1054 923 <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 930 <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> 1062 931 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1063 <tr><td><a name="diff005 8" /></td></tr>932 <tr><td><a name="diff0052" /></td></tr> 1064 933 <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> 1065 934 <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> … … 1083 952 <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> 1084 953 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1085 <tr><td><a name="diff005 9" /></td></tr>954 <tr><td><a name="diff0053" /></td></tr> 1086 955 <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> 1087 956 <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> 1088 957 <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> 1089 958 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1090 <tr><td><a name="diff00 60" /></td></tr>959 <tr><td><a name="diff0054" /></td></tr> 1091 960 <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> 1092 961 <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> … … 1106 975 <tr><td class="lineno" valign="top"></td><td class="left"> +-------------------+----------+----------+---------------+</td><td> </td><td class="right"> +-------------------+----------+----------+---------------+</td><td class="lineno" valign="top"></td></tr> 1107 976 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1108 <tr><td><a name="diff00 61" /></td></tr>977 <tr><td><a name="diff0055" /></td></tr> 1109 978 <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> 1110 979 <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> … … 1126 995 <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> 1127 996 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1128 <tr><td><a name="diff00 62" /></td></tr>997 <tr><td><a name="diff0056" /></td></tr> 1129 998 <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> 1130 999 <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> … … 1144 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> 1145 1014 <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> 1146 <tr><td><a name="diff00 63" /></td></tr>1015 <tr><td><a name="diff0057" /></td></tr> 1147 1016 <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> 1148 1017 <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> … … 1157 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> 1158 1027 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1159 <tr bgcolor="gray" ><td></td><th><a name="part-l 33" /><small>skipping to change at</small><em> page 62, line 20</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 62, line 20</em></th><td></td></tr>1028 <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 62, line 20</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 62, line 20</em></th><td></td></tr> 1160 1029 <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> 1161 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> … … 1168 1037 <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> 1169 1038 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1170 <tr><td><a name="diff00 64" /></td></tr>1039 <tr><td><a name="diff0058" /></td></tr> 1171 1040 <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> 1172 1041 <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> … … 1182 1051 <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> 1183 1052 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1184 <tr bgcolor="gray" ><td></td><th><a name="part-l3 4" /><small>skipping to change at</small><em> page 63, line 7</em></th><th> </th><th><a name="part-r34" /><small>skipping to change at</small><em> page 63, line 7</em></th><td></td></tr>1053 <tr bgcolor="gray" ><td></td><th><a name="part-l30" /><small>skipping to change at</small><em> page 63, line 7</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 63, line 7</em></th><td></td></tr> 1185 1054 <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> 1186 1055 <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> … … 1193 1062 <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> 1194 1063 <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> 1195 <tr><td><a name="diff00 65" /></td></tr>1064 <tr><td><a name="diff0059" /></td></tr> 1196 1065 <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> 1197 1066 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1206 1075 <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> 1207 1076 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1208 <tr bgcolor="gray" ><td></td><th><a name="part-l3 5" /><small>skipping to change at</small><em> page 63, line 29</em></th><th> </th><th><a name="part-r35" /><small>skipping to change at</small><em> page 63, line 29</em></th><td></td></tr>1077 <tr bgcolor="gray" ><td></td><th><a name="part-l31" /><small>skipping to change at</small><em> page 63, line 29</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 63, line 29</em></th><td></td></tr> 1209 1078 <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> 1210 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> … … 1217 1086 <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> 1218 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> 1219 <tr><td><a name="diff006 6" /></td></tr>1088 <tr><td><a name="diff0060" /></td></tr> 1220 1089 <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> 1221 1090 <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> … … 1231 1100 <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> 1232 1101 <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 <tr><td><a name="diff006 7" /></td></tr>1102 <tr><td><a name="diff0061" /></td></tr> 1234 1103 <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> 1235 1104 <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> … … 1250 1119 <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> 1251 1120 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1252 <tr><td><a name="diff006 8" /></td></tr>1121 <tr><td><a name="diff0062" /></td></tr> 1253 1122 <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> 1254 1123 <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> … … 1260 1129 <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> 1261 1130 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1262 <tr><td><a name="diff006 9" /></td></tr>1131 <tr><td><a name="diff0063" /></td></tr> 1263 1132 <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> 1264 1133 <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> … … 1279 1148 <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> 1280 1149 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1281 <tr><td><a name="diff00 70" /></td></tr>1150 <tr><td><a name="diff0064" /></td></tr> 1282 1151 <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> 1283 1152 <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> 1284 1153 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1285 <tr><td><a name="diff00 71" /></td></tr>1154 <tr><td><a name="diff0065" /></td></tr> 1286 1155 <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> 1287 1156 <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> … … 1301 1170 <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> 1302 1171 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1303 <tr><td><a name="diff00 72" /></td></tr>1172 <tr><td><a name="diff0066" /></td></tr> 1304 1173 <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> 1305 1174 <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> … … 1316 1185 <tr><td class="lineno" valign="top"></td><td class="left"> Section 4.1 of [RFC5226]) and are subject to the following rules:</td><td> </td><td class="right"> Section 4.1 of [RFC5226]) and are subject to the following rules:</td><td class="lineno" valign="top"></td></tr> 1317 1186 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1318 <tr bgcolor="gray" ><td></td><th><a name="part-l3 6" /><small>skipping to change at</small><em> page 66, line 10</em></th><th> </th><th><a name="part-r36" /><small>skipping to change at</small><em> page 66, line 10</em></th><td></td></tr>1187 <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 66, line 10</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 66, line 10</em></th><td></td></tr> 1319 1188 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1320 1189 <tr><td class="lineno" valign="top"></td><td class="left"> 7. The IESG MAY reassign responsibility for a protocol token. This</td><td> </td><td class="right"> 7. The IESG MAY reassign responsibility for a protocol token. This</td><td class="lineno" valign="top"></td></tr> … … 1327 1196 <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> 1328 1197 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1329 <tr><td><a name="diff00 73" /></td></tr>1198 <tr><td><a name="diff0067" /></td></tr> 1330 1199 <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> 1331 1200 <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> … … 1341 1210 <tr><td class="lineno" valign="top"></td><td class="left"> The responsible party is: "IETF (iesg@ietf.org) - Internet</td><td> </td><td class="right"> The responsible party is: "IETF (iesg@ietf.org) - Internet</td><td class="lineno" valign="top"></td></tr> 1342 1211 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1343 <tr bgcolor="gray" ><td></td><th><a name="part-l3 7" /><small>skipping to change at</small><em> page 67, line 13</em></th><th> </th><th><a name="part-r37" /><small>skipping to change at</small><em> page 67, line 13</em></th><td></td></tr>1212 <tr bgcolor="gray" ><td></td><th><a name="part-l33" /><small>skipping to change at</small><em> page 67, line 13</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 67, line 13</em></th><td></td></tr> 1344 1213 <tr><td class="lineno" valign="top"></td><td class="left"> unknown or untrusted source.</td><td> </td><td class="right"> unknown or untrusted source.</td><td class="lineno" valign="top"></td></tr> 1345 1214 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1352 1221 <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> 1353 1222 <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> 1354 <tr><td><a name="diff00 74" /></td></tr>1223 <tr><td><a name="diff0068" /></td></tr> 1355 1224 <tr><td class="lineno" valign="top"></td><td class="lblock"> mappings; <span class="delete">DNSSEC</span> ([RFC4033]) is one way to improve authenticity.</td><td> </td><td class="rblock"> mappings; <span class="insert">DNS Security Extensions (DNSSEC)</span> ([RFC4033]) is one way to</td><td class="lineno" valign="top"></td></tr> 1356 1225 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"> improve authenticity.</td><td class="lineno" valign="top"></td></tr> … … 1370 1239 <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> 1371 1240 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1372 <tr><td><a name="diff00 75" /></td></tr>1241 <tr><td><a name="diff0069" /></td></tr> 1373 1242 <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> 1374 1243 <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> … … 1384 1253 <tr><td class="lineno" valign="top"></td><td class="left"> Intermediaries that contain a shared cache are especially vulnerable</td><td> </td><td class="right"> Intermediaries that contain a shared cache are especially vulnerable</td><td class="lineno" valign="top"></td></tr> 1385 1254 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1386 <tr bgcolor="gray" ><td></td><th><a name="part-l3 8" /><small>skipping to change at</small><em> page 70, line 9</em></th><th> </th><th><a name="part-r38" /><small>skipping to change at</small><em> page 70, line 9</em></th><td></td></tr>1255 <tr bgcolor="gray" ><td></td><th><a name="part-l34" /><small>skipping to change at</small><em> page 70, line 9</em></th><th> </th><th><a name="part-r34" /><small>skipping to change at</small><em> page 70, line 9</em></th><td></td></tr> 1387 1256 <tr><td class="lineno" valign="top"></td><td class="left"> access mechanism has resulted in its increasing use within</td><td> </td><td class="right"> access mechanism has resulted in its increasing use within</td><td class="lineno" valign="top"></td></tr> 1388 1257 <tr><td class="lineno" valign="top"></td><td class="left"> environments where verification of message integrity is crucial.</td><td> </td><td class="right"> environments where verification of message integrity is crucial.</td><td class="lineno" valign="top"></td></tr> … … 1395 1264 <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> 1396 1265 <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> 1397 <tr><td><a name="diff007 6" /></td></tr>1266 <tr><td><a name="diff0070" /></td></tr> 1398 1267 <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> 1399 1268 <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> … … 1408 1277 <tr><td class="lineno" valign="top"></td><td class="left"> designed to be independent of the transport protocol, such that it</td><td> </td><td class="right"> designed to be independent of the transport protocol, such that it</td><td class="lineno" valign="top"></td></tr> 1409 1278 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1410 <tr bgcolor="gray" ><td></td><th><a name="part-l39" /><small>skipping to change at</small><em> page 70, line 39</em></th><th> </th><th><a name="part-r39" /><small>skipping to change at</small><em> page 70, line 39</em></th><td></td></tr> 1411 <tr><td class="lineno" valign="top"></td><td class="left"> A server is in the position to save personal data about a user's</td><td> </td><td class="right"> A server is in the position to save personal data about a user's</td><td class="lineno" valign="top"></td></tr> 1412 <tr><td class="lineno" valign="top"></td><td class="left"> requests over time, which might identify their reading patterns or</td><td> </td><td class="right"> requests over time, which might identify their reading patterns or</td><td class="lineno" valign="top"></td></tr> 1413 <tr><td class="lineno" valign="top"></td><td class="left"> subjects of interest. In particular, log information gathered at an</td><td> </td><td class="right"> subjects of interest. In particular, log information gathered at an</td><td class="lineno" valign="top"></td></tr> 1414 <tr><td class="lineno" valign="top"></td><td class="left"> intermediary often contains a history of user agent interaction,</td><td> </td><td class="right"> intermediary often contains a history of user agent interaction,</td><td class="lineno" valign="top"></td></tr> 1415 <tr><td class="lineno" valign="top"></td><td class="left"> across a multitude of sites, that can be traced to individual users.</td><td> </td><td class="right"> across a multitude of sites, that can be traced to individual users.</td><td class="lineno" valign="top"></td></tr> 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> 1417 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP log information is confidential in nature; its handling is often</td><td> </td><td class="right"> HTTP log information is confidential in nature; its handling is often</td><td class="lineno" valign="top"></td></tr> 1418 <tr><td class="lineno" valign="top"></td><td class="left"> constrained by laws and regulations. Log information needs to be</td><td> </td><td class="right"> constrained by laws and regulations. Log information needs to be</td><td class="lineno" valign="top"></td></tr> 1419 <tr><td class="lineno" valign="top"></td><td class="left"> securely stored and appropriate guidelines followed for its analysis.</td><td> </td><td class="right"> securely stored and appropriate guidelines followed for its analysis.</td><td class="lineno" valign="top"></td></tr> 1420 <tr><td class="lineno" valign="top"></td><td class="left"> Anonymization of personal information within individual entries</td><td> </td><td class="right"> Anonymization of personal information within individual entries</td><td class="lineno" valign="top"></td></tr> 1421 <tr><td><a name="diff0077" /></td></tr> 1422 <tr><td class="lineno" valign="top"></td><td class="lblock"> helps, but is generally not sufficient to prevent real log traces</td><td> </td><td class="rblock"> helps, but i<span class="insert">t i</span>s generally not sufficient to prevent real log traces</td><td class="lineno" valign="top"></td></tr> 1423 <tr><td class="lineno" valign="top"></td><td class="left"> from being re-identified based on correlation with other access</td><td> </td><td class="right"> from being re-identified based on correlation with other access</td><td class="lineno" valign="top"></td></tr> 1424 <tr><td class="lineno" valign="top"></td><td class="left"> characteristics. As such, access traces that are keyed to a specific</td><td> </td><td class="right"> characteristics. As such, access traces that are keyed to a specific</td><td class="lineno" valign="top"></td></tr> 1425 <tr><td class="lineno" valign="top"></td><td class="left"> client are unsafe to publish even if the key is pseudonymous.</td><td> </td><td class="right"> client are unsafe to publish even if the key is pseudonymous.</td><td class="lineno" valign="top"></td></tr> 1426 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1427 <tr><td class="lineno" valign="top"></td><td class="left"> To minimize the risk of theft or accidental publication, log</td><td> </td><td class="right"> To minimize the risk of theft or accidental publication, log</td><td class="lineno" valign="top"></td></tr> 1428 <tr><td class="lineno" valign="top"></td><td class="left"> information ought to be purged of personally identifiable</td><td> </td><td class="right"> information ought to be purged of personally identifiable</td><td class="lineno" valign="top"></td></tr> 1429 <tr><td class="lineno" valign="top"></td><td class="left"> information, including user identifiers, IP addresses, and user-</td><td> </td><td class="right"> information, including user identifiers, IP addresses, and user-</td><td class="lineno" valign="top"></td></tr> 1430 <tr><td class="lineno" valign="top"></td><td class="left"> provided query parameters, as soon as that information is no longer</td><td> </td><td class="right"> provided query parameters, as soon as that information is no longer</td><td class="lineno" valign="top"></td></tr> 1431 <tr><td class="lineno" valign="top"></td><td class="left"> necessary to support operational needs for security, auditing, or</td><td> </td><td class="right"> necessary to support operational needs for security, auditing, or</td><td class="lineno" valign="top"></td></tr> 1432 <tr><td class="lineno" valign="top"></td><td class="left"> fraud control.</td><td> </td><td class="right"> fraud control.</td><td class="lineno" valign="top"></td></tr> 1433 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1434 <tr bgcolor="gray" ><td></td><th><a name="part-l40" /><small>skipping to change at</small><em> page 72, line 50</em></th><th> </th><th><a name="part-r40" /><small>skipping to change at</small><em> page 72, line 50</em></th><td></td></tr> 1279 <tr bgcolor="gray" ><td></td><th><a name="part-l35" /><small>skipping to change at</small><em> page 72, line 50</em></th><th> </th><th><a name="part-r35" /><small>skipping to change at</small><em> page 72, line 50</em></th><td></td></tr> 1435 1280 <tr><td class="lineno" valign="top"></td><td class="left"> Yuchung Cheng, Yutaka Oiwa, Yves Lafon (long-time member of the</td><td> </td><td class="right"> Yuchung Cheng, Yutaka Oiwa, Yves Lafon (long-time member of the</td><td class="lineno" valign="top"></td></tr> 1436 1281 <tr><td class="lineno" valign="top"></td><td class="left"> editor team), Zed A. Shaw, and Zhong Yu.</td><td> </td><td class="right"> editor team), Zed A. Shaw, and Zhong Yu.</td><td class="lineno" valign="top"></td></tr> … … 1443 1288 <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> 1444 1289 <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="diff007 8" /></td></tr>1290 <tr><td><a name="diff0071" /></td></tr> 1446 1291 <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> 1447 1292 <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> … … 1458 1303 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1459 1304 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1460 <tr bgcolor="gray" ><td></td><th><a name="part-l 41" /><small>skipping to change at</small><em> page 73, line 28</em></th><th> </th><th><a name="part-r41" /><small>skipping to change at</small><em> page 73, line 25</em></th><td></td></tr>1305 <tr bgcolor="gray" ><td></td><th><a name="part-l36" /><small>skipping to change at</small><em> page 73, line 28</em></th><th> </th><th><a name="part-r36" /><small>skipping to change at</small><em> page 73, line 25</em></th><td></td></tr> 1461 1306 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter,</td><td> </td><td class="right"> [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter,</td><td class="lineno" valign="top"></td></tr> 1462 1307 <tr><td class="lineno" valign="top"></td><td class="left"> "Uniform Resource Identifier (URI): Generic Syntax",</td><td> </td><td class="right"> "Uniform Resource Identifier (URI): Generic Syntax",</td><td class="lineno" valign="top"></td></tr> … … 1469 1314 <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> 1470 1315 <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> 1471 <tr><td><a name="diff007 9" /></td></tr>1316 <tr><td><a name="diff0072" /></td></tr> 1472 1317 <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> 1473 1318 <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> … … 1475 1320 <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> 1476 1321 <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> 1477 <tr><td><a name="diff00 80" /></td></tr>1322 <tr><td><a name="diff0073" /></td></tr> 1478 1323 <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> 1479 1324 <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> … … 1481 1326 <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> 1482 1327 <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> 1483 <tr><td><a name="diff00 81" /></td></tr>1328 <tr><td><a name="diff0074" /></td></tr> 1484 1329 <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> 1485 1330 <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> … … 1487 1332 <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> 1488 1333 <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> 1489 <tr><td><a name="diff00 82" /></td></tr>1334 <tr><td><a name="diff0075" /></td></tr> 1490 1335 <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> 1491 1336 <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> … … 1493 1338 <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> 1494 1339 <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> 1495 <tr><td><a name="diff00 83" /></td></tr>1340 <tr><td><a name="diff0076" /></td></tr> 1496 1341 <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> 1497 1342 <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> … … 1503 1348 <tr><td class="lineno" valign="top"></td><td class="left"> Interchange", ANSI X3.4, 1986.</td><td> </td><td class="right"> Interchange", ANSI X3.4, 1986.</td><td class="lineno" valign="top"></td></tr> 1504 1349 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1505 <tr><td><a name="diff00 84" /></td></tr>1350 <tr><td><a name="diff0077" /></td></tr> 1506 1351 <tr><td class="lineno" valign="top"></td><td class="lblock"> [Welch] Welch, T., "A Technique for High<span class="delete"> </span>Performance Data</td><td> </td><td class="rblock"> [Welch] Welch, T., "A Technique for High<span class="insert">-</span>Performance Data</td><td class="lineno" valign="top"></td></tr> 1507 1352 <tr><td class="lineno" valign="top"></td><td class="left"> Compression", IEEE Computer 17(6), June 1984.</td><td> </td><td class="right"> Compression", IEEE Computer 17(6), June 1984.</td><td class="lineno" valign="top"></td></tr> … … 1516 1361 <tr><td class="lineno" valign="top"></td><td class="left"> Specifications and Registration Procedures", BCP 13,</td><td> </td><td class="right"> Specifications and Registration Procedures", BCP 13,</td><td class="lineno" valign="top"></td></tr> 1517 1362 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1518 <tr bgcolor="gray" ><td></td><th><a name="part-l 42" /><small>skipping to change at</small><em> page 76, line 25</em></th><th> </th><th><a name="part-r42" /><small>skipping to change at</small><em> page 76, line 22</em></th><td></td></tr>1363 <tr bgcolor="gray" ><td></td><th><a name="part-l37" /><small>skipping to change at</small><em> page 76, line 25</em></th><th> </th><th><a name="part-r37" /><small>skipping to change at</small><em> page 76, line 22</em></th><td></td></tr> 1519 1364 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1520 1365 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP has been in use since 1990. The first version, later referred</td><td> </td><td class="right"> HTTP has been in use since 1990. The first version, later referred</td><td class="lineno" valign="top"></td></tr> … … 1527 1372 <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> 1528 1373 <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> 1529 <tr><td><a name="diff00 85" /></td></tr>1374 <tr><td><a name="diff0078" /></td></tr> 1530 1375 <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> 1531 1376 <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> … … 1536 1381 <tr><td class="lineno" valign="top"></td><td class="left"> requirements that enable reliable implementations, adding only those</td><td> </td><td class="right"> requirements that enable reliable implementations, adding only those</td><td class="lineno" valign="top"></td></tr> 1537 1382 <tr><td class="lineno" valign="top"></td><td class="left"> features that can either be safely ignored by an HTTP/1.0 recipient</td><td> </td><td class="right"> features that can either be safely ignored by an HTTP/1.0 recipient</td><td class="lineno" valign="top"></td></tr> 1538 <tr><td><a name="diff0086" /></td></tr> 1539 <tr><td class="lineno" valign="top"></td><td class="lblock"> or only sent when communicating with a party advertising conformance</td><td> </td><td class="rblock"> or only <span class="insert">be</span> sent when communicating with a party advertising</td><td class="lineno" valign="top"></td></tr> 1540 <tr><td class="lineno" valign="top"></td><td class="lblock"> with HTTP/1.1.</td><td> </td><td class="rblock"> conformance with HTTP/1.1.</td><td class="lineno" valign="top"></td></tr> 1541 <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 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP/1.1 has been designed to make supporting previous versions easy.</td><td> </td><td class="right"> HTTP/1.1 has been designed to make supporting previous versions easy.</td><td class="lineno" valign="top"></td></tr> 1543 <tr><td class="lineno" valign="top"></td><td class="left"> A general-purpose HTTP/1.1 server ought to be able to understand any</td><td> </td><td class="right"> A general-purpose HTTP/1.1 server ought to be able to understand any</td><td class="lineno" valign="top"></td></tr> 1544 <tr><td class="lineno" valign="top"></td><td class="left"> valid request in the format of HTTP/1.0, responding appropriately</td><td> </td><td class="right"> valid request in the format of HTTP/1.0, responding appropriately</td><td class="lineno" valign="top"></td></tr> 1545 <tr><td class="lineno" valign="top"></td><td class="left"> with an HTTP/1.1 message that only uses features understood (or</td><td> </td><td class="right"> with an HTTP/1.1 message that only uses features understood (or</td><td class="lineno" valign="top"></td></tr> 1546 <tr><td class="lineno" valign="top"></td><td class="left"> safely ignored) by HTTP/1.0 clients. Likewise, an HTTP/1.1 client</td><td> </td><td class="right"> safely ignored) by HTTP/1.0 clients. Likewise, an HTTP/1.1 client</td><td class="lineno" valign="top"></td></tr> 1547 <tr><td class="lineno" valign="top"></td><td class="left"> can be expected to understand any valid HTTP/1.0 response.</td><td> </td><td class="right"> can be expected to understand any valid HTTP/1.0 response.</td><td class="lineno" valign="top"></td></tr> 1548 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1549 <tr><td class="lineno" valign="top"></td><td class="left"> Since HTTP/0.9 did not support header fields in a request, there is</td><td> </td><td class="right"> Since HTTP/0.9 did not support header fields in a request, there is</td><td class="lineno" valign="top"></td></tr> 1550 <tr><td class="lineno" valign="top"></td><td class="left"> no mechanism for it to support name-based virtual hosts (selection of</td><td> </td><td class="right"> no mechanism for it to support name-based virtual hosts (selection of</td><td class="lineno" valign="top"></td></tr> 1551 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1552 <tr bgcolor="gray" ><td></td><th><a name="part-l43" /><small>skipping to change at</small><em> page 77, line 10</em></th><th> </th><th><a name="part-r43" /><small>skipping to change at</small><em> page 77, line 5</em></th><td></td></tr> 1383 <tr><td class="lineno" valign="top"></td><td class="left"> or only be sent when communicating with a party advertising</td><td> </td><td class="right"> or only be sent when communicating with a party advertising</td><td class="lineno" valign="top"></td></tr> 1384 <tr><td class="lineno" valign="top"></td><td class="left"> conformance with HTTP/1.1.</td><td> </td><td class="right"> conformance with HTTP/1.1.</td><td class="lineno" valign="top"></td></tr> 1385 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1386 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1387 <tr bgcolor="gray" ><td></td><th><a name="part-l38" /><small>skipping to change at</small><em> page 77, line 10</em></th><th> </th><th><a name="part-r38" /><small>skipping to change at</small><em> page 77, line 5</em></th><td></td></tr> 1553 1388 <tr><td class="lineno" valign="top"></td><td class="left"> implements name-based virtual hosts ought to disable support for</td><td> </td><td class="right"> implements name-based virtual hosts ought to disable support for</td><td class="lineno" valign="top"></td></tr> 1554 1389 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP/0.9. Most requests that appear to be HTTP/0.9 are, in fact,</td><td> </td><td class="right"> HTTP/0.9. Most requests that appear to be HTTP/0.9 are, in fact,</td><td class="lineno" valign="top"></td></tr> … … 1561 1396 <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> 1562 1397 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1563 <tr><td><a name="diff00 87" /></td></tr>1398 <tr><td><a name="diff0079" /></td></tr> 1564 1399 <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> 1565 1400 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1574 1409 <tr><td class="lineno" valign="top"></td><td class="left"> to which that request was directed. The Host header field was</td><td> </td><td class="right"> to which that request was directed. The Host header field was</td><td class="lineno" valign="top"></td></tr> 1575 1410 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1576 <tr bgcolor="gray" ><td></td><th><a name="part-l 44" /><small>skipping to change at</small><em> page 78, line 20</em></th><th> </th><th><a name="part-r44" /><small>skipping to change at</small><em> page 78, line 14</em></th><td></td></tr>1411 <tr bgcolor="gray" ><td></td><th><a name="part-l39" /><small>skipping to change at</small><em> page 78, line 20</em></th><th> </th><th><a name="part-r39" /><small>skipping to change at</small><em> page 78, line 14</em></th><td></td></tr> 1577 1412 <tr><td class="lineno" valign="top"></td><td class="left"> not be used by clients at all when a proxy is being used.</td><td> </td><td class="right"> not be used by clients at all when a proxy is being used.</td><td class="lineno" valign="top"></td></tr> 1578 1413 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1585 1420 <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> 1586 1421 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1587 <tr><td><a name="diff008 8" /></td></tr>1422 <tr><td><a name="diff0080" /></td></tr> 1588 1423 <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> 1589 1424 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1590 <tr><td><a name="diff008 9" /></td></tr>1591 <tr><td class="lineno" valign="top"></td><td class="lblock"> The HTTP-version ABNF production has been clarified to be <span class="delete">case-</span></td><td> </td><td class="rblock"> The HTTP-version ABNF production has been clarified to be <span class="insert">case</span></td><td class="lineno" valign="top"></td></tr>1592 <tr><td class="lineno" valign="top"></td><td class="l block"> sensitive. Additionally, version numbers <span class="delete">has</span> been restricted to</td><td> </td><td class="rblock"> sensitive. Additionally, version numbers <span class="insert">have</span>been restricted to</td><td class="lineno" valign="top"></td></tr>1425 <tr><td><a name="diff0081" /></td></tr> 1426 <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> 1427 <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> 1593 1428 <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> 1594 <tr><td><a name="diff00 90" /></td></tr>1429 <tr><td><a name="diff0082" /></td></tr> 1595 1430 <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> 1596 1431 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1597 1432 <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> 1598 1433 <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> 1599 <tr><td><a name="diff00 91" /></td></tr>1434 <tr><td><a name="diff0083" /></td></tr> 1600 1435 <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> 1601 1436 <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 1437 <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> 1603 <tr><td><a name="diff00 92" /></td></tr>1438 <tr><td><a name="diff0084" /></td></tr> 1604 1439 <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> 1605 1440 <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> … … 1609 1444 <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> 1610 1445 <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> 1611 <tr><td><a name="diff00 93" /></td></tr>1446 <tr><td><a name="diff0085" /></td></tr> 1612 1447 <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> 1613 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> 1614 1449 <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> 1615 1450 <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> 1616 <tr><td><a name="diff00 94" /></td></tr>1451 <tr><td><a name="diff0086" /></td></tr> 1617 1452 <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> 1618 1453 <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> … … 1620 1455 <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> 1621 1456 <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> 1622 <tr><td><a name="diff00 95" /></td></tr>1457 <tr><td><a name="diff0087" /></td></tr> 1623 1458 <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> 1624 1459 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1625 1460 <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> 1626 <tr><td><a name="diff00 96" /></td></tr>1461 <tr><td><a name="diff0088" /></td></tr> 1627 1462 <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> 1628 1463 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"> </td><td class="lineno" valign="top"></td></tr> … … 1630 1465 <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> 1631 1466 <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> 1632 <tr><td><a name="diff00 97" /></td></tr>1467 <tr><td><a name="diff0089" /></td></tr> 1633 1468 <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> 1634 1469 <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> … … 1636 1471 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1637 1472 <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> 1638 <tr><td><a name="diff009 8" /></td></tr>1473 <tr><td><a name="diff0090" /></td></tr> 1639 1474 <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> 1640 1475 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1644 1479 <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> 1645 1480 <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> 1646 <tr><td><a name="diff009 9" /></td></tr>1481 <tr><td><a name="diff0091" /></td></tr> 1647 1482 <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> 1648 1483 <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> 1649 1484 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1650 <tr><td><a name="diff0 100" /></td></tr>1485 <tr><td><a name="diff0092" /></td></tr> 1651 1486 <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> 1652 1487 <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> 1653 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> 1654 1489 <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> 1655 <tr><td><a name="diff0 101" /></td></tr>1490 <tr><td><a name="diff0093" /></td></tr> 1656 1491 <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> 1657 1492 <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> 1658 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> 1659 <tr><td><a name="diff0 102" /></td></tr>1494 <tr><td><a name="diff0094" /></td></tr> 1660 1495 <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> 1661 1496 <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> … … 1663 1498 <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> 1664 1499 <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> 1665 <tr><td><a name="diff0 103" /></td></tr>1500 <tr><td><a name="diff0095" /></td></tr> 1666 1501 <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> 1667 1502 <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> 1668 1503 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1669 <tr><td><a name="diff0 104" /></td></tr>1504 <tr><td><a name="diff0096" /></td></tr> 1670 1505 <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> 1671 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> 1672 <tr><td><a name="diff0 105" /></td></tr>1507 <tr><td><a name="diff0097" /></td></tr> 1673 1508 <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> 1674 1509 <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> … … 1677 1512 <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> 1678 1513 <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> 1679 <tr><td><a name="diff0 106" /></td></tr>1514 <tr><td><a name="diff0098" /></td></tr> 1680 1515 <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> 1681 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> … … 1685 1520 <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> 1686 1521 <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> 1687 <tr><td><a name="diff0 107" /></td></tr>1522 <tr><td><a name="diff0099" /></td></tr> 1688 1523 <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> 1689 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> 1690 1525 <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> 1691 1526 <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> 1692 <tr><td><a name="diff010 8" /></td></tr>1527 <tr><td><a name="diff0100" /></td></tr> 1693 1528 <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> 1694 1529 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1695 1530 <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> 1696 <tr><td><a name="diff010 9" /></td></tr>1531 <tr><td><a name="diff0101" /></td></tr> 1697 1532 <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> 1698 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> 1699 1534 <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> 1700 <tr><td><a name="diff01 10" /></td></tr>1535 <tr><td><a name="diff0102" /></td></tr> 1701 1536 <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> 1702 1537 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1703 <tr><td><a name="diff01 11" /></td></tr>1538 <tr><td><a name="diff0103" /></td></tr> 1704 1539 <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> 1705 1540 <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> 1706 1541 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1707 <tr><td><a name="diff01 12" /></td></tr>1542 <tr><td><a name="diff0104" /></td></tr> 1708 1543 <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> 1709 1544 <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> … … 1711 1546 <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> 1712 1547 <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> 1713 <tr><td><a name="diff01 13" /></td></tr>1548 <tr><td><a name="diff0105" /></td></tr> 1714 1549 <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> 1715 1550 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1724 1559 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP-message = start-line *( header-field CRLF ) CRLF [ message-body</td><td> </td><td class="right"> HTTP-message = start-line *( header-field CRLF ) CRLF [ message-body</td><td class="lineno" valign="top"></td></tr> 1725 1560 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1726 <tr bgcolor="gray" ><td></td><th><a name="part-l4 5" /><small>skipping to change at</small><em> page 83, line 25</em></th><th> </th><th><a name="part-r45" /><small>skipping to change at</small><em> page 83, line 20</em></th><td></td></tr>1561 <tr bgcolor="gray" ><td></td><th><a name="part-l40" /><small>skipping to change at</small><em> page 83, line 25</em></th><th> </th><th><a name="part-r40" /><small>skipping to change at</small><em> page 83, line 20</em></th><td></td></tr> 1727 1562 <tr><td class="lineno" valign="top"></td><td class="left"> client 7</td><td> </td><td class="right"> client 7</td><td class="lineno" valign="top"></td></tr> 1728 1563 <tr><td class="lineno" valign="top"></td><td class="left"> close 50, 55</td><td> </td><td class="right"> close 50, 55</td><td class="lineno" valign="top"></td></tr> … … 1735 1570 <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> 1736 1571 <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> 1737 <tr><td><a name="diff01 14" /></td></tr>1572 <tr><td><a name="diff0106" /></td></tr> 1738 1573 <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> 1739 1574 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1748 1583 <tr><td class="lineno" valign="top"></td><td class="left"> absolute-URI 16</td><td> </td><td class="right"> absolute-URI 16</td><td class="lineno" valign="top"></td></tr> 1749 1584 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1750 <tr bgcolor="gray" ><td></td><th><a name="part-l4 6" /><small>skipping to change at</small><em> page 84, line 20</em></th><th> </th><th><a name="part-r46" /><small>skipping to change at</small><em> page 84, line 14</em></th><td></td></tr>1585 <tr bgcolor="gray" ><td></td><th><a name="part-l41" /><small>skipping to change at</small><em> page 84, line 20</em></th><th> </th><th><a name="part-r41" /><small>skipping to change at</small><em> page 84, line 14</em></th><td></td></tr> 1751 1586 <tr><td class="lineno" valign="top"></td><td class="left"> field-content 22</td><td> </td><td class="right"> field-content 22</td><td class="lineno" valign="top"></td></tr> 1752 1587 <tr><td class="lineno" valign="top"></td><td class="left"> field-name 22, 39</td><td> </td><td class="right"> field-name 22, 39</td><td class="lineno" valign="top"></td></tr> … … 1759 1594 <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> 1760 1595 <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> 1761 <tr><td><a name="diff01 15" /></td></tr>1596 <tr><td><a name="diff0107" /></td></tr> 1762 1597 <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> 1763 1598 <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> 1764 <tr><td><a name="diff01 16" /></td></tr>1599 <tr><td><a name="diff0108" /></td></tr> 1765 1600 <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> 1766 1601 <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> … … 1775 1610 <tr><td class="lineno" valign="top"></td><td class="left"> OWS 24</td><td> </td><td class="right"> OWS 24</td><td class="lineno" valign="top"></td></tr> 1776 1611 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1777 <tr bgcolor="gray" ><td></td><th><a name="part-l4 7" /><small>skipping to change at</small><em> page 85, line 34</em></th><th> </th><th><a name="part-r47" /><small>skipping to change at</small><em> page 85, line 28</em></th><td></td></tr>1612 <tr bgcolor="gray" ><td></td><th><a name="part-l42" /><small>skipping to change at</small><em> page 85, line 34</em></th><th> </th><th><a name="part-r42" /><small>skipping to change at</small><em> page 85, line 28</em></th><td></td></tr> 1778 1613 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1779 1614 <tr><td class="lineno" valign="top"></td><td class="left"> H</td><td> </td><td class="right"> H</td><td class="lineno" valign="top"></td></tr> … … 1786 1621 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1787 1622 <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> 1788 <tr><td><a name="diff01 17" /></td></tr>1623 <tr><td><a name="diff0109" /></td></tr> 1789 1624 <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> 1790 1625 <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> … … 1805 1640 <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> 1806 1641 <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> 1807 <tr><td><a name="diff011 8" /></td></tr>1642 <tr><td><a name="diff0110" /></td></tr> 1808 1643 <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> 1809 1644 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1818 1653 <tr><td class="lineno" valign="top"></td><td class="left"> resource 16</td><td> </td><td class="right"> resource 16</td><td class="lineno" valign="top"></td></tr> 1819 1654 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1820 <tr bgcolor="gray" ><td></td><th><a name="part-l4 8" /><small>skipping to change at</small><em> page 86, line 35</em></th><th> </th><th><a name="part-r48" /><small>skipping to change at</small><em> page 86, line 30</em></th><td></td></tr>1655 <tr bgcolor="gray" ><td></td><th><a name="part-l43" /><small>skipping to change at</small><em> page 86, line 35</em></th><th> </th><th><a name="part-r43" /><small>skipping to change at</small><em> page 86, line 30</em></th><td></td></tr> 1821 1656 <tr><td class="lineno" valign="top"></td><td class="left"> target URI 40</td><td> </td><td class="right"> target URI 40</td><td class="lineno" valign="top"></td></tr> 1822 1657 <tr><td class="lineno" valign="top"></td><td class="left"> TE header field 38</td><td> </td><td class="right"> TE header field 38</td><td class="lineno" valign="top"></td></tr> … … 1829 1664 <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> 1830 1665 <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> 1831 <tr><td><a name="diff011 9" /></td></tr>1666 <tr><td><a name="diff0111" /></td></tr> 1832 1667 <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> 1833 1668 <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> … … 1843 1678 1844 1679 <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr> 1845 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 11 9change blocks. </a></th></tr>1846 <tr class="stats"><td></td><th><i> 212 lines changed or deleted</i></th><th><i> </i></th><th><i>191lines changed or added</i></th><td></td></tr>1680 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 111 change blocks. </a></th></tr> 1681 <tr class="stats"><td></td><th><i>194 lines changed or deleted</i></th><th><i> </i></th><th><i>173 lines changed or added</i></th><td></td></tr> 1847 1682 <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> 1848 1683 </table> -
draft-ietf-httpbis/latest/auth48/rfc7231.abdiff.txt
r2645 r2647 387 387 388 388 389 Section 1., paragraph 1:390 OLD:391 392 Each Hypertext Transfer Protocol (HTTP) message is either a request393 or a response. A server listens on a connection for a request,394 parses each message received, interprets the message semantics in395 relation to the identified request target, and responds to that396 request with one or more response messages. A client constructs397 request messages to communicate specific intentions, and examines398 received responses to see if the intentions were carried out, and399 determine how to interpret the results. This document defines400 HTTP/1.1 request and response semantics in terms of the architecture401 defined in [RFC7230].402 403 NEW:404 405 Each Hypertext Transfer Protocol (HTTP) message is either a request406 or a response. A server listens on a connection for a request,407 parses each message received, interprets the message semantics in408 relation to the identified request target, and responds to that409 request with one or more response messages. A client constructs410 request messages to communicate specific intentions, examines411 received responses to see if the intentions were carried out, and412 determines how to interpret the results. This document defines413 HTTP/1.1 request and response semantics in terms of the architecture414 defined in [RFC7230].415 416 417 389 Section 2., paragraph 1: 418 390 OLD: … … 431 403 identified by a Uniform Resource Identifier (URI), as described in 432 404 Section 2.7 of [RFC7230]. 433 434 435 Section 3., paragraph 3:436 OLD:437 438 An origin server might be provided with, or capable of generating,439 multiple representations that are each intended to reflect the440 current state of a target resource. In such cases, some algorithm is441 used by the origin server to select one of those representations as442 most applicable to a given request, usually based on content443 negotiation. This "selected representation" is used to provide the444 data and metadata for evaluating conditional requests [RFC7232] and445 constructing the payload for 200 (OK) and 304 (Not Modified)446 responses to GET (Section 4.3.1).447 448 NEW:449 450 An origin server might be provided with, or be capable of generating,451 multiple representations that are each intended to reflect the452 current state of a target resource. In such cases, some algorithm is453 used by the origin server to select one of those representations as454 most applicable to a given request, usually based on content455 negotiation. This "selected representation" is used to provide the456 data and metadata for evaluating conditional requests [RFC7232] and457 constructing the payload for 200 (OK) and 304 (Not Modified)458 responses to GET (Section 4.3.1).459 405 460 406 … … 497 443 498 444 499 Section 3.1.1.1., paragraph 6:500 OLD:501 502 A parameter value that matches the token production can be503 transmitted as either a token or within a quoted-string. The quoted504 and unquoted values are equivalent. For example, the following505 examples are all equivalent, but the first is preferred for506 consistency:507 508 NEW:509 510 A parameter value that matches the token production can be511 transmitted either as a token or within a quoted-string. The quoted512 and unquoted values are equivalent. For example, the following513 examples are all equivalent, but the first is preferred for514 consistency:515 516 517 445 Section 3.1.1.2., paragraph 3: 518 446 OLD: 519 447 520 Charset names ought to be registered in IANA Character Set registry521 (<http://www.iana.org/assignments/character-sets>) according to the522 procedures defined in [RFC2978].448 Charset names ought to be registered in the IANA Character Set 449 registry (<http://www.iana.org/assignments/character-sets>) according 450 to the procedures defined in [RFC2978]. 523 451 524 452 NEW: … … 790 718 791 719 792 Section 4.3.4., paragraph 10:793 OLD:794 795 An origin server MUST NOT send a validator header field796 (Section 7.2), such as an ETag or Last-Modified field, in a797 successful response to PUT unless the request's representation data798 was saved without any transformation applied to the body (i.e., the799 resource's new representation data is identical to the representation800 data received in the PUT request) and the validator field value801 reflects the new representation. This requirement allows a user802 agent to know when the representation body it has in memory remains803 current as a result of the PUT, thus not in need of retrieving again804 from the origin server, and that the new validator(s) received in the805 response can be used for future conditional requests in order to806 prevent accidental overwrites (Section 5.2).807 808 NEW:809 810 An origin server MUST NOT send a validator header field811 (Section 7.2), such as an ETag or Last-Modified field, in a812 successful response to PUT unless the request's representation data813 was saved without any transformation applied to the body (i.e., the814 resource's new representation data is identical to the representation815 data received in the PUT request) and the validator field value816 reflects the new representation. This requirement allows a user817 agent to know when the representation body it has in memory remains818 current as a result of the PUT, thus not in need of being retrieved819 again from the origin server, and that the new validator(s) received820 in the response can be used for future conditional requests in order821 to prevent accidental overwrites (Section 5.2).822 823 824 720 Section 4.3.4., paragraph 13: 825 721 OLD: … … 862 758 2xx (Successful) status code to indicate that a connection is 863 759 established. However, most origin servers do not implement CONNECT. 864 865 866 Section 4.3.7., paragraph 1:867 OLD:868 869 The OPTIONS method requests information about the communication870 options available for the target resource, either at the origin871 server or an intervening intermediary. This method allows a client872 to determine the options and/or requirements associated with a873 resource, or the capabilities of a server, without implying a874 resource action.875 876 NEW:877 878 The OPTIONS method requests information about the communication879 options available for the target resource, at either the origin880 server or an intervening intermediary. This method allows a client881 to determine the options and/or requirements associated with a882 resource, or the capabilities of a server, without implying a883 resource action.884 760 885 761 … … 1069 945 identifier. A sender SHOULD NOT generate information in product- 1070 946 version that is not a version identifier (i.e., successive versions 1071 of the same product name ought to onlydiffer in the product-version947 of the same product name ought only to differ in the product-version 1072 948 portion of the product identifier). 1073 949 … … 1229 1105 Permanently) ([RFC7238]; however, it defines the status code 308 1230 1106 (Permanent Redirect) for this purpose). 1231 1232 1233 Section 6.5.1., paragraph 1:1234 OLD:1235 1236 The 400 (Bad Request) status code indicates that the server cannot or1237 will not process the request due to something which is perceived to1238 be a client error (e.g., malformed request syntax, invalid request1239 message framing, or deceptive request routing).1240 1241 NEW:1242 1243 The 400 (Bad Request) status code indicates that the server cannot or1244 will not process the request due to something that is perceived to be1245 a client error (e.g., malformed request syntax, invalid request1246 message framing, or deceptive request routing).1247 1107 1248 1108 … … 1337 1197 1338 1198 1339 Section 7.1.2., paragraph 5:1340 OLD:1341 1342 If the Location value provided in a 3xx (Redirection) does not have a1343 fragment component, a user agent MUST process the redirection as if1344 the value inherits the fragment component of the URI reference used1345 to generate the request target (i.e., the redirection inherits the1346 original reference's fragment, if any).1347 1348 NEW:1349 1350 If the Location value provided in a 3xx (Redirection) response does1351 not have a fragment component, a user agent MUST process the1352 redirection as if the value inherits the fragment component of the1353 URI reference used to generate the request target (i.e., the1354 redirection inherits the original reference's fragment, if any).1355 1356 1357 1199 Section 7.1.4., paragraph 1: 1358 1200 OLD: … … 1484 1326 1485 1327 1486 Section 8.2., paragraph 2:1487 OLD:1488 1489 This Section replaces the registration procedure for HTTP Status1490 Codes previously defined in Section 7.1 of [RFC2817].1491 1492 NEW:1493 1494 This section replaces the registration procedure for HTTP Status1495 Codes previously defined in Section 7.1 of [RFC2817].1496 1497 1498 1328 Section 8.2.3., paragraph 1: 1499 1329 OLD: … … 1520 1350 registry located at <http://www.iana.org/assignments/message-headers> 1521 1351 as defined by [BCP90]. 1522 1523 1524 Section 8.3.1., paragraph 3:1525 OLD:1526 1527 Authors of specifications defining new fields are advised to keep the1528 name as short as practical and to not prefix the name with "X-"1529 unless the header field will never be used on the Internet. (The1530 "x-" prefix idiom has been extensively misused in practice; it was1531 intended to only be used as a mechanism for avoiding name collisions1532 inside proprietary software or intranet processing, since the prefix1533 would ensure that private names never collide with a newly registered1534 Internet name; see [BCP178] for further information)1535 1536 NEW:1537 1538 Authors of specifications defining new fields are advised to keep the1539 name as short as practical and not to prefix the name with "X-"1540 unless the header field will never be used on the Internet. (The1541 "X-" prefix idiom has been extensively misused in practice; it was1542 intended to only be used as a mechanism for avoiding name collisions1543 inside proprietary software or intranet processing, since the prefix1544 would ensure that private names never collide with a newly registered1545 Internet name; see [BCP178] for further information).1546 1352 1547 1353 … … 1650 1456 1651 1457 1652 Section 9.1., paragraph 2:1653 OLD:1654 1655 For example, UNIX, Microsoft Windows, and other operating systems use1656 ".." as a path component to indicate a directory level above the1657 current one, and use specially named paths or file names to send data1658 to system devices. Similar naming conventions might exist within1659 other types of storage systems. Likewise, local storage systems have1660 an annoying tendency to prefer user-friendliness over security when1661 handling invalid or unexpected characters, recomposition of1662 decomposed characters, and case-normalization of case-insensitive1663 names.1664 1665 NEW:1666 1667 For example, UNIX, Microsoft Windows, and other operating systems use1668 ".." as a path component to indicate a directory level above the1669 current one, and they use specially named paths or file names to send1670 data to system devices. Similar naming conventions might exist1671 within other types of storage systems. Likewise, local storage1672 systems have an annoying tendency to prefer user-friendliness over1673 security when handling invalid or unexpected characters,1674 recomposition of decomposed characters, and case-normalization of1675 case-insensitive names.1676 1677 1678 1458 Section 9.1., paragraph 3: 1679 1459 OLD: … … 1798 1578 [RFC7238] Reschke, J., "The Hypertext Transfer Protocol (HTTP) 1799 1579 Status Code 308 (Permanent Redirect)", RFC 7238, May 2014. 1800 1801 1802 Appendix A., paragraph 1:1803 OLD:1804 1805 HTTP/1.1 uses many of the constructs defined for the Internet Message1806 Format [RFC5322] and the Multipurpose Internet Mail Extensions (MIME)1807 [RFC2045] to allow a message body to be transmitted in an open1808 variety of representations and with extensible header fields.1809 However, RFC 2045 is focused only on email; applications of HTTP have1810 many characteristics that differ from email, and hence HTTP has1811 features that differ from MIME. These differences were carefully1812 chosen to optimize performance over binary connections, to allow1813 greater freedom in the use of new media types, to make date1814 comparisons easier, and to acknowledge the practice of some early1815 HTTP servers and clients.1816 1817 NEW:1818 1819 HTTP/1.1 uses many of the constructs defined for the Internet Message1820 Format [RFC5322] and the Multipurpose Internet Mail Extensions (MIME)1821 [RFC2045] to allow a message body to be transmitted in an open1822 variety of representations and with extensible header fields.1823 However, RFC 2045 is focused only on email; applications of HTTP have1824 many characteristics that differ from email; hence, HTTP has features1825 that differ from MIME. These differences were carefully chosen to1826 optimize performance over binary connections, to allow greater1827 freedom in the use of new media types, to make date comparisons1828 easier, and to acknowledge the practice of some early HTTP servers1829 and clients.1830 1580 1831 1581 -
draft-ietf-httpbis/latest/auth48/rfc7231.diff.html
r2645 r2647 137 137 <tr><td class="lineno" valign="top"></td><td class="left"> or a response. A server listens on a connection for a request,</td><td> </td><td class="right"> or a response. A server listens on a connection for a request,</td><td class="lineno" valign="top"></td></tr> 138 138 <tr><td class="lineno" valign="top"></td><td class="left"> parses each message received, interprets the message semantics in</td><td> </td><td class="right"> parses each message received, interprets the message semantics in</td><td class="lineno" valign="top"></td></tr> 139 <tr><td class="lineno" valign="top"></td><td class="left"> relation to the identified request target, and responds to that</td><td> </td><td class="right"> relation to the identified request target, and responds to that</td><td class="lineno" valign="top"></td></tr>140 <tr><td class="lineno" valign="top"></td><td class="left"> request with one or more response messages. A client constructs</td><td> </td><td class="right"> request with one or more response messages. A client constructs</td><td class="lineno" valign="top"></td></tr>141 <tr><td><a name="diff0009" /></td></tr>142 <tr><td class="lineno" valign="top"></td><td class="lblock"> request messages to communicate specific intentions, <span class="delete">and </span>examines</td><td> </td><td class="rblock"> request messages to communicate specific intentions, examines</td><td class="lineno" valign="top"></td></tr>143 <tr><td class="lineno" valign="top"></td><td class="left"> received responses to see if the intentions were carried out, and</td><td> </td><td class="right"> received responses to see if the intentions were carried out, and</td><td class="lineno" valign="top"></td></tr>144 <tr><td><a name="diff0010" /></td></tr>145 <tr><td class="lineno" valign="top"></td><td class="lblock"> determine how to interpret the results. This document defines</td><td> </td><td class="rblock"> determine<span class="insert">s</span> how to interpret the results. This document defines</td><td class="lineno" valign="top"></td></tr>146 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP/1.1 request and response semantics in terms of the architecture</td><td> </td><td class="right"> HTTP/1.1 request and response semantics in terms of the architecture</td><td class="lineno" valign="top"></td></tr>147 <tr><td class="lineno" valign="top"></td><td class="left"> defined in [RFC7230].</td><td> </td><td class="right"> defined in [RFC7230].</td><td class="lineno" valign="top"></td></tr>148 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>149 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP provides a uniform interface for interacting with a resource</td><td> </td><td class="right"> HTTP provides a uniform interface for interacting with a resource</td><td class="lineno" valign="top"></td></tr>150 <tr><td class="lineno" valign="top"></td><td class="left"> (Section 2), regardless of its type, nature, or implementation, via</td><td> </td><td class="right"> (Section 2), regardless of its type, nature, or implementation, via</td><td class="lineno" valign="top"></td></tr>151 <tr><td class="lineno" valign="top"></td><td class="left"> the manipulation and transfer of representations (Section 3).</td><td> </td><td class="right"> the manipulation and transfer of representations (Section 3).</td><td class="lineno" valign="top"></td></tr>152 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>153 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP semantics include the intentions defined by each request method</td><td> </td><td class="right"> HTTP semantics include the intentions defined by each request method</td><td class="lineno" valign="top"></td></tr>154 <tr><td class="lineno" valign="top"></td><td class="left"> (Section 4), extensions to those semantics that might be described in</td><td> </td><td class="right"> (Section 4), extensions to those semantics that might be described in</td><td class="lineno" valign="top"></td></tr>155 <tr><td class="lineno" valign="top"></td><td class="left"> request header fields (Section 5), the meaning of status codes to</td><td> </td><td class="right"> request header fields (Section 5), the meaning of status codes to</td><td class="lineno" valign="top"></td></tr>156 139 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 157 140 <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 7, line 11</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 7, line 11</em></th><td></td></tr> … … 166 149 <tr><td class="lineno" valign="top"></td><td class="left">2. Resources</td><td> </td><td class="right">2. Resources</td><td class="lineno" valign="top"></td></tr> 167 150 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 168 <tr><td><a name="diff00 11" /></td></tr>151 <tr><td><a name="diff0009" /></td></tr> 169 152 <tr><td class="lineno" valign="top"></td><td class="lblock"> The target of an HTTP request is called a <span class="delete">resource</span>. HTTP does not</td><td> </td><td class="rblock"> The target of an HTTP request is called a <span class="insert">"resource"</span>. HTTP does not</td><td class="lineno" valign="top"></td></tr> 170 153 <tr><td class="lineno" valign="top"></td><td class="left"> limit the nature of a resource; it merely defines an interface that</td><td> </td><td class="right"> limit the nature of a resource; it merely defines an interface that</td><td class="lineno" valign="top"></td></tr> … … 179 162 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7230]).</td><td> </td><td class="right"> [RFC7230]).</td><td class="lineno" valign="top"></td></tr> 180 163 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 181 <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 7, line 46</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 7, line 46</em></th><td></td></tr> 182 <tr><td class="lineno" valign="top"></td><td class="left"> abstraction is needed to represent ("take the place of") the current</td><td> </td><td class="right"> abstraction is needed to represent ("take the place of") the current</td><td class="lineno" valign="top"></td></tr> 183 <tr><td class="lineno" valign="top"></td><td class="left"> or desired state of that thing in our communications. That</td><td> </td><td class="right"> or desired state of that thing in our communications. That</td><td class="lineno" valign="top"></td></tr> 184 <tr><td class="lineno" valign="top"></td><td class="left"> abstraction is called a representation [REST].</td><td> </td><td class="right"> abstraction is called a representation [REST].</td><td class="lineno" valign="top"></td></tr> 185 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 186 <tr><td class="lineno" valign="top"></td><td class="left"> For the purposes of HTTP, a "representation" is information that is</td><td> </td><td class="right"> For the purposes of HTTP, a "representation" is information that is</td><td class="lineno" valign="top"></td></tr> 187 <tr><td class="lineno" valign="top"></td><td class="left"> intended to reflect a past, current, or desired state of a given</td><td> </td><td class="right"> intended to reflect a past, current, or desired state of a given</td><td class="lineno" valign="top"></td></tr> 188 <tr><td class="lineno" valign="top"></td><td class="left"> resource, in a format that can be readily communicated via the</td><td> </td><td class="right"> resource, in a format that can be readily communicated via the</td><td class="lineno" valign="top"></td></tr> 189 <tr><td class="lineno" valign="top"></td><td class="left"> protocol, and that consists of a set of representation metadata and a</td><td> </td><td class="right"> protocol, and that consists of a set of representation metadata and a</td><td class="lineno" valign="top"></td></tr> 190 <tr><td class="lineno" valign="top"></td><td class="left"> potentially unbounded stream of representation data.</td><td> </td><td class="right"> potentially unbounded stream of representation data.</td><td class="lineno" valign="top"></td></tr> 191 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 192 <tr><td><a name="diff0012" /></td></tr> 193 <tr><td class="lineno" valign="top"></td><td class="lblock"> An origin server might be provided with, or capable of generating,</td><td> </td><td class="rblock"> An origin server might be provided with, or <span class="insert">be </span>capable of generating,</td><td class="lineno" valign="top"></td></tr> 194 <tr><td class="lineno" valign="top"></td><td class="left"> multiple representations that are each intended to reflect the</td><td> </td><td class="right"> multiple representations that are each intended to reflect the</td><td class="lineno" valign="top"></td></tr> 195 <tr><td class="lineno" valign="top"></td><td class="left"> current state of a target resource. In such cases, some algorithm is</td><td> </td><td class="right"> current state of a target resource. In such cases, some algorithm is</td><td class="lineno" valign="top"></td></tr> 196 <tr><td class="lineno" valign="top"></td><td class="left"> used by the origin server to select one of those representations as</td><td> </td><td class="right"> used by the origin server to select one of those representations as</td><td class="lineno" valign="top"></td></tr> 197 <tr><td class="lineno" valign="top"></td><td class="left"> most applicable to a given request, usually based on content</td><td> </td><td class="right"> most applicable to a given request, usually based on content</td><td class="lineno" valign="top"></td></tr> 198 <tr><td class="lineno" valign="top"></td><td class="left"> negotiation. This "selected representation" is used to provide the</td><td> </td><td class="right"> negotiation. This "selected representation" is used to provide the</td><td class="lineno" valign="top"></td></tr> 199 <tr><td class="lineno" valign="top"></td><td class="left"> data and metadata for evaluating conditional requests [RFC7232] and</td><td> </td><td class="right"> data and metadata for evaluating conditional requests [RFC7232] and</td><td class="lineno" valign="top"></td></tr> 200 <tr><td class="lineno" valign="top"></td><td class="left"> constructing the payload for 200 (OK) and 304 (Not Modified)</td><td> </td><td class="right"> constructing the payload for 200 (OK) and 304 (Not Modified)</td><td class="lineno" valign="top"></td></tr> 201 <tr><td class="lineno" valign="top"></td><td class="left"> responses to GET (Section 4.3.1).</td><td> </td><td class="right"> responses to GET (Section 4.3.1).</td><td class="lineno" valign="top"></td></tr> 202 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 203 <tr><td class="lineno" valign="top"></td><td class="left">3.1. Representation Metadata</td><td> </td><td class="right">3.1. Representation Metadata</td><td class="lineno" valign="top"></td></tr> 204 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 205 <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 8, line 32</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 8, line 32</em></th><td></td></tr> 164 <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 8, line 32</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 8, line 32</em></th><td></td></tr> 206 165 <tr><td class="lineno" valign="top"></td><td class="left"> | Content-Type | Section 3.1.1.5 |</td><td> </td><td class="right"> | Content-Type | Section 3.1.1.5 |</td><td class="lineno" valign="top"></td></tr> 207 166 <tr><td class="lineno" valign="top"></td><td class="left"> | Content-Encoding | Section 3.1.2.2 |</td><td> </td><td class="right"> | Content-Encoding | Section 3.1.2.2 |</td><td class="lineno" valign="top"></td></tr> … … 214 173 <tr><td class="lineno" valign="top"></td><td class="left">3.1.1.1. Media Type</td><td> </td><td class="right">3.1.1.1. Media Type</td><td class="lineno" valign="top"></td></tr> 215 174 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 216 <tr><td><a name="diff001 3" /></td></tr>175 <tr><td><a name="diff0010" /></td></tr> 217 176 <tr><td class="lineno" valign="top"></td><td class="lblock"> HTTP uses Internet <span class="delete">Media T</span>ypes [RFC2046] in the Content-Type</td><td> </td><td class="rblock"> HTTP uses Internet <span class="insert">media t</span>ypes [RFC2046] in the Content-Type</td><td class="lineno" valign="top"></td></tr> 218 177 <tr><td class="lineno" valign="top"></td><td class="left"> (Section 3.1.1.5) and Accept (Section 5.3.2) header fields in order</td><td> </td><td class="right"> (Section 3.1.1.5) and Accept (Section 5.3.2) header fields in order</td><td class="lineno" valign="top"></td></tr> … … 231 190 <tr><td class="lineno" valign="top"></td><td class="left"> parameter = token "=" ( token / quoted-string )</td><td> </td><td class="right"> parameter = token "=" ( token / quoted-string )</td><td class="lineno" valign="top"></td></tr> 232 191 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 233 <tr><td><a name="diff001 4" /></td></tr>192 <tr><td><a name="diff0011" /></td></tr> 234 193 <tr><td class="lineno" valign="top"></td><td class="lblock"> The type, subtype, and parameter name tokens are <span class="delete">case-insensitive.</span></td><td> </td><td class="rblock"> The type, subtype, and parameter name tokens are <span class="insert">case insensitive.</span></td><td class="lineno" valign="top"></td></tr> 235 194 <tr><td class="lineno" valign="top"></td><td class="lblock"> Parameter values might or might not be <span class="delete">case-sensitive,</span> depending on</td><td> </td><td class="rblock"> Parameter values might or might not be <span class="insert">case sensitive,</span> depending on</td><td class="lineno" valign="top"></td></tr> … … 239 198 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 240 199 <tr><td class="lineno" valign="top"></td><td class="left"> A parameter value that matches the token production can be</td><td> </td><td class="right"> A parameter value that matches the token production can be</td><td class="lineno" valign="top"></td></tr> 241 <tr><td><a name="diff0015" /></td></tr> 242 <tr><td class="lineno" valign="top"></td><td class="lblock"> transmitted <span class="delete">as either</span> a token or within a quoted-string. The quoted</td><td> </td><td class="rblock"> transmitted <span class="insert">either as</span> a token or within a quoted-string. The quoted</td><td class="lineno" valign="top"></td></tr> 200 <tr><td class="lineno" valign="top"></td><td class="left"> transmitted either as a token or within a quoted-string. The quoted</td><td> </td><td class="right"> transmitted either as a token or within a quoted-string. The quoted</td><td class="lineno" valign="top"></td></tr> 243 201 <tr><td class="lineno" valign="top"></td><td class="left"> and unquoted values are equivalent. For example, the following</td><td> </td><td class="right"> and unquoted values are equivalent. For example, the following</td><td class="lineno" valign="top"></td></tr> 244 202 <tr><td class="lineno" valign="top"></td><td class="left"> examples are all equivalent, but the first is preferred for</td><td> </td><td class="right"> examples are all equivalent, but the first is preferred for</td><td class="lineno" valign="top"></td></tr> 245 203 <tr><td class="lineno" valign="top"></td><td class="left"> consistency:</td><td> </td><td class="right"> consistency:</td><td class="lineno" valign="top"></td></tr> 246 204 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 247 <tr><td class="lineno" valign="top"></td><td class="left"> text/html;charset=utf-8</td><td> </td><td class="right"> text/html;charset=utf-8</td><td class="lineno" valign="top"></td></tr> 248 <tr><td class="lineno" valign="top"></td><td class="left"> text/html;charset=UTF-8</td><td> </td><td class="right"> text/html;charset=UTF-8</td><td class="lineno" valign="top"></td></tr> 249 <tr><td class="lineno" valign="top"></td><td class="left"> Text/HTML;Charset="utf-8"</td><td> </td><td class="right"> Text/HTML;Charset="utf-8"</td><td class="lineno" valign="top"></td></tr> 250 <tr><td class="lineno" valign="top"></td><td class="left"> text/html; charset="utf-8"</td><td> </td><td class="right"> text/html; charset="utf-8"</td><td class="lineno" valign="top"></td></tr> 251 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 252 <tr><td class="lineno" valign="top"></td><td class="left"> Internet media types ought to be registered with IANA according to</td><td> </td><td class="right"> Internet media types ought to be registered with IANA according to</td><td class="lineno" valign="top"></td></tr> 253 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 254 <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 9, line 32</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 9, line 32</em></th><td></td></tr> 205 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 206 <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 9, line 32</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 9, line 32</em></th><td></td></tr> 255 207 <tr><td class="lineno" valign="top"></td><td class="left"> around the "=" character.</td><td> </td><td class="right"> around the "=" character.</td><td class="lineno" valign="top"></td></tr> 256 208 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 263 215 <tr><td class="lineno" valign="top"></td><td class="left"> charset = token</td><td> </td><td class="right"> charset = token</td><td class="lineno" valign="top"></td></tr> 264 216 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 265 <tr><td><a name="diff001 6" /></td></tr>266 <tr><td class="lineno" valign="top"></td><td class="lblock"> Charset names ought to be registered in IANA <span class="delete">Character Set</span> registry</td><td> </td><td class="rblock"> Charset names ought to be registered in <span class="insert">the</span>IANA <span class="insert">"Character Sets"</span></td><td class="lineno" valign="top"></td></tr>267 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">(<http://www.iana.org/assignments/character-sets>)</span> according to the</td><td> </td><td class="rblock"> registry <span class="insert"><http://www.iana.org/assignments/character-sets></span> according</td><td class="lineno" valign="top"></td></tr>268 <tr><td class="lineno" valign="top"></td><td class="l block"> procedures defined in [RFC2978].</td><td> </td><td class="rblock"> to the procedures defined in [RFC2978].</td><td class="lineno" valign="top"></td></tr>217 <tr><td><a name="diff0012" /></td></tr> 218 <tr><td class="lineno" valign="top"></td><td class="lblock"> Charset names ought to be registered in the IANA <span class="delete">Character Set</span></td><td> </td><td class="rblock"> Charset names ought to be registered in the IANA <span class="insert">"Character Sets"</span></td><td class="lineno" valign="top"></td></tr> 219 <tr><td class="lineno" valign="top"></td><td class="lblock"> registry <span class="delete">(<http://www.iana.org/assignments/character-sets>)</span> according</td><td> </td><td class="rblock"> registry <span class="insert"><http://www.iana.org/assignments/character-sets></span> according</td><td class="lineno" valign="top"></td></tr> 220 <tr><td class="lineno" valign="top"></td><td class="left"> to the procedures defined in [RFC2978].</td><td> </td><td class="right"> to the procedures defined in [RFC2978].</td><td class="lineno" valign="top"></td></tr> 269 221 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 270 222 <tr><td class="lineno" valign="top"></td><td class="left">3.1.1.3. Canonicalization and Text Defaults</td><td> </td><td class="right">3.1.1.3. Canonicalization and Text Defaults</td><td class="lineno" valign="top"></td></tr> … … 283 235 <tr><td class="lineno" valign="top"></td><td class="left"> MIME's canonical form requires that media subtypes of the "text" type</td><td> </td><td class="right"> MIME's canonical form requires that media subtypes of the "text" type</td><td class="lineno" valign="top"></td></tr> 284 236 <tr><td class="lineno" valign="top"></td><td class="left"> use CRLF as the text line break. HTTP allows the transfer of text</td><td> </td><td class="right"> use CRLF as the text line break. HTTP allows the transfer of text</td><td class="lineno" valign="top"></td></tr> 285 <tr><td><a name="diff001 7" /></td></tr>237 <tr><td><a name="diff0013" /></td></tr> 286 238 <tr><td class="lineno" valign="top"></td><td class="lblock"> media with plain <span class="delete">CR</span> or <span class="delete">LF</span> alone representing a line break, when such</td><td> </td><td class="rblock"> media with plain <span class="insert">carriage return (CR)</span> or <span class="insert">line feed (LF)</span> alone</td><td class="lineno" valign="top"></td></tr> 287 239 <tr><td class="lineno" valign="top"></td><td class="lblock"> line breaks are consistent for an entire representation. An HTTP</td><td> </td><td class="rblock"> representing a line break, when such line breaks are consistent for</td><td class="lineno" valign="top"></td></tr> … … 305 257 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC2046], and include a boundary parameter as part of the media type</td><td> </td><td class="right"> [RFC2046], and include a boundary parameter as part of the media type</td><td class="lineno" valign="top"></td></tr> 306 258 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 307 <tr bgcolor="gray" ><td></td><th><a name="part-l 7" /><small>skipping to change at</small><em> page 11, line 35</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 11, line 35</em></th><td></td></tr>259 <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 11, line 35</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 11, line 35</em></th><td></td></tr> 308 260 <tr><td class="lineno" valign="top"></td><td class="left"> Content coding values indicate an encoding transformation that has</td><td> </td><td class="right"> Content coding values indicate an encoding transformation that has</td><td class="lineno" valign="top"></td></tr> 309 261 <tr><td class="lineno" valign="top"></td><td class="left"> been or can be applied to a representation. Content codings are</td><td> </td><td class="right"> been or can be applied to a representation. Content codings are</td><td class="lineno" valign="top"></td></tr> … … 316 268 <tr><td class="lineno" valign="top"></td><td class="left"> content-coding = token</td><td> </td><td class="right"> content-coding = token</td><td class="lineno" valign="top"></td></tr> 317 269 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 318 <tr><td><a name="diff001 8" /></td></tr>270 <tr><td><a name="diff0014" /></td></tr> 319 271 <tr><td class="lineno" valign="top"></td><td class="lblock"> All content-coding values are <span class="delete">case-insensitive</span> and ought to be</td><td> </td><td class="rblock"> All content-coding values are <span class="insert">case insensitive</span> and ought to be</td><td class="lineno" valign="top"></td></tr> 320 272 <tr><td class="lineno" valign="top"></td><td class="lblock"> registered within the <span class="delete">HTTP</span> Content Coding <span class="delete">registry,</span> as defined in</td><td> </td><td class="rblock"> registered within the <span class="insert">"HTTP</span> Content Coding <span class="insert">Registry",</span> as defined in</td><td class="lineno" valign="top"></td></tr> … … 330 282 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 331 283 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 332 <tr bgcolor="gray" ><td></td><th><a name="part-l 8" /><small>skipping to change at</small><em> page 14, line 5</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 14, line 5</em></th><td></td></tr>284 <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 14, line 5</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 14, line 5</em></th><td></td></tr> 333 285 <tr><td class="lineno" valign="top"></td><td class="left"> Content-Language is to allow a user to identify and differentiate</td><td> </td><td class="right"> Content-Language is to allow a user to identify and differentiate</td><td class="lineno" valign="top"></td></tr> 334 286 <tr><td class="lineno" valign="top"></td><td class="left"> representations according to the users' own preferred language.</td><td> </td><td class="right"> representations according to the users' own preferred language.</td><td class="lineno" valign="top"></td></tr> … … 341 293 <tr><td class="lineno" valign="top"></td><td class="left"> is intended for all language audiences. This might mean that the</td><td> </td><td class="right"> is intended for all language audiences. This might mean that the</td><td class="lineno" valign="top"></td></tr> 342 294 <tr><td class="lineno" valign="top"></td><td class="left"> sender does not consider it to be specific to any natural language,</td><td> </td><td class="right"> sender does not consider it to be specific to any natural language,</td><td class="lineno" valign="top"></td></tr> 343 <tr><td><a name="diff001 9" /></td></tr>295 <tr><td><a name="diff0015" /></td></tr> 344 296 <tr><td class="lineno" valign="top"></td><td class="lblock"> or that the sender does not know <span class="delete">for which language it is intend</span>ed.</td><td> </td><td class="rblock"> or that the sender does not know <span class="insert">which language is being us</span>ed.</td><td class="lineno" valign="top"></td></tr> 345 297 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 354 306 <tr><td class="lineno" valign="top"></td><td class="left"> representation does not mean that it is intended for multiple</td><td> </td><td class="right"> representation does not mean that it is intended for multiple</td><td class="lineno" valign="top"></td></tr> 355 307 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 356 <tr bgcolor="gray" ><td></td><th><a name="part-l 9" /><small>skipping to change at</small><em> page 19, line 21</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 19, line 21</em></th><td></td></tr>308 <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 19, line 21</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 19, line 21</em></th><td></td></tr> 357 309 <tr><td class="lineno" valign="top"></td><td class="left"> representations for a response (the dimensions over which it might</td><td> </td><td class="right"> representations for a response (the dimensions over which it might</td><td class="lineno" valign="top"></td></tr> 358 310 <tr><td class="lineno" valign="top"></td><td class="left"> vary, such as language, content-coding, etc.) compared to various</td><td> </td><td class="right"> vary, such as language, content-coding, etc.) compared to various</td><td class="lineno" valign="top"></td></tr> … … 365 317 <tr><td class="lineno" valign="top"></td><td class="left"> describe to a user agent, or when the server desires to send its</td><td> </td><td class="right"> describe to a user agent, or when the server desires to send its</td><td class="lineno" valign="top"></td></tr> 366 318 <tr><td class="lineno" valign="top"></td><td class="left"> "best guess" to the user agent along with the first response (hoping</td><td> </td><td class="right"> "best guess" to the user agent along with the first response (hoping</td><td class="lineno" valign="top"></td></tr> 367 <tr><td><a name="diff00 20" /></td></tr>319 <tr><td><a name="diff0016" /></td></tr> 368 320 <tr><td class="lineno" valign="top"></td><td class="lblock"> to avoid the round<span class="delete"> </span>trip delay of a subsequent request if the "best</td><td> </td><td class="rblock"> to avoid the round<span class="insert">-</span>trip delay of a subsequent request if the "best</td><td class="lineno" valign="top"></td></tr> 369 321 <tr><td class="lineno" valign="top"></td><td class="left"> guess" is good enough for the user). In order to improve the</td><td> </td><td class="right"> guess" is good enough for the user). In order to improve the</td><td class="lineno" valign="top"></td></tr> … … 378 330 <tr><td class="lineno" valign="top"></td><td class="left"> intended use for the response (e.g., does the user want to view it</td><td> </td><td class="right"> intended use for the response (e.g., does the user want to view it</td><td class="lineno" valign="top"></td></tr> 379 331 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 380 <tr bgcolor="gray" ><td></td><th><a name="part-l 10" /><small>skipping to change at</small><em> page 20, line 37</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 20, line 37</em></th><td></td></tr>332 <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 20, line 37</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 20, line 37</em></th><td></td></tr> 381 333 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 382 334 <tr><td class="lineno" valign="top"></td><td class="left"> A server might choose not to send an initial representation, other</td><td> </td><td class="right"> A server might choose not to send an initial representation, other</td><td class="lineno" valign="top"></td></tr> … … 389 341 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 390 342 <tr><td class="lineno" valign="top"></td><td class="left"> Reactive negotiation is advantageous when the response would vary</td><td> </td><td class="right"> Reactive negotiation is advantageous when the response would vary</td><td class="lineno" valign="top"></td></tr> 391 <tr><td><a name="diff00 21" /></td></tr>343 <tr><td><a name="diff0017" /></td></tr> 392 344 <tr><td class="lineno" valign="top"></td><td class="lblock"> over commonly<span class="delete">-</span>used dimensions (such as type, language, or encoding),</td><td> </td><td class="rblock"> over commonly<span class="insert"> </span>used dimensions (such as type, language, or encoding),</td><td class="lineno" valign="top"></td></tr> 393 345 <tr><td class="lineno" valign="top"></td><td class="left"> when the origin server is unable to determine a user agent's</td><td> </td><td class="right"> when the origin server is unable to determine a user agent's</td><td class="lineno" valign="top"></td></tr> … … 402 354 <tr><td class="lineno" valign="top"></td><td class="left"> selection, though it does not prevent such a mechanism from being</td><td> </td><td class="right"> selection, though it does not prevent such a mechanism from being</td><td class="lineno" valign="top"></td></tr> 403 355 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 404 <tr bgcolor="gray" ><td></td><th><a name="part-l1 1" /><small>skipping to change at</small><em> page 21, line 26</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 21, line 26</em></th><td></td></tr>356 <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 21, line 26</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 21, line 26</em></th><td></td></tr> 405 357 <tr><td class="lineno" valign="top"></td><td class="left"> example, a client can send conditional request header fields</td><td> </td><td class="right"> example, a client can send conditional request header fields</td><td class="lineno" valign="top"></td></tr> 406 358 <tr><td class="lineno" valign="top"></td><td class="left"> (Section 5.2) to make the requested action conditional on the current</td><td> </td><td class="right"> (Section 5.2) to make the requested action conditional on the current</td><td class="lineno" valign="top"></td></tr> … … 413 365 <tr><td class="lineno" valign="top"></td><td class="left"> applying semantics to a target resource in much the same way as</td><td> </td><td class="right"> applying semantics to a target resource in much the same way as</td><td class="lineno" valign="top"></td></tr> 414 366 <tr><td class="lineno" valign="top"></td><td class="left"> invoking a defined method on an identified object would apply</td><td> </td><td class="right"> invoking a defined method on an identified object would apply</td><td class="lineno" valign="top"></td></tr> 415 <tr><td><a name="diff00 22" /></td></tr>367 <tr><td><a name="diff0018" /></td></tr> 416 368 <tr><td class="lineno" valign="top"></td><td class="lblock"> semantics. The method token is case<span class="delete">-</span>sensitive because it might be</td><td> </td><td class="rblock"> semantics. The method token is case<span class="insert"> </span>sensitive because it might be</td><td class="lineno" valign="top"></td></tr> 417 369 <tr><td class="lineno" valign="top"></td><td class="left"> used as a gateway to object-based systems with case-sensitive method</td><td> </td><td class="right"> used as a gateway to object-based systems with case-sensitive method</td><td class="lineno" valign="top"></td></tr> … … 419 371 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 420 372 <tr><td class="lineno" valign="top"></td><td class="left"> Unlike distributed objects, the standardized request methods in HTTP</td><td> </td><td class="right"> Unlike distributed objects, the standardized request methods in HTTP</td><td class="lineno" valign="top"></td></tr> 421 <tr><td><a name="diff00 23" /></td></tr>373 <tr><td><a name="diff0019" /></td></tr> 422 374 <tr><td class="lineno" valign="top"></td><td class="lblock"> are not resource<span class="delete">-</span>specific, since uniform interfaces provide for</td><td> </td><td class="rblock"> are not resource<span class="insert"> </span>specific, since uniform interfaces provide for</td><td class="lineno" valign="top"></td></tr> 423 375 <tr><td class="lineno" valign="top"></td><td class="left"> better visibility and reuse in network-based systems [REST]. Once</td><td> </td><td class="right"> better visibility and reuse in network-based systems [REST]. Once</td><td class="lineno" valign="top"></td></tr> … … 432 384 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 433 385 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 434 <tr bgcolor="gray" ><td></td><th><a name="part-l1 2" /><small>skipping to change at</small><em> page 22, line 31</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 22, line 31</em></th><td></td></tr>386 <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 22, line 31</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 22, line 31</em></th><td></td></tr> 435 387 <tr><td class="lineno" valign="top"></td><td class="left"> | | target resource. | |</td><td> </td><td class="right"> | | target resource. | |</td><td class="lineno" valign="top"></td></tr> 436 388 <tr><td class="lineno" valign="top"></td><td class="left"> | TRACE | Perform a message loop-back test along the path | 4.3.8 |</td><td> </td><td class="right"> | TRACE | Perform a message loop-back test along the path | 4.3.8 |</td><td class="lineno" valign="top"></td></tr> … … 443 395 <tr><td class="lineno" valign="top"></td><td class="left"> Additional methods, outside the scope of this specification, have</td><td> </td><td class="right"> Additional methods, outside the scope of this specification, have</td><td class="lineno" valign="top"></td></tr> 444 396 <tr><td class="lineno" valign="top"></td><td class="left"> been standardized for use in HTTP. All such methods ought to be</td><td> </td><td class="right"> been standardized for use in HTTP. All such methods ought to be</td><td class="lineno" valign="top"></td></tr> 445 <tr><td><a name="diff002 4" /></td></tr>397 <tr><td><a name="diff0020" /></td></tr> 446 398 <tr><td class="lineno" valign="top"></td><td class="lblock"> registered within the <span class="delete">HTTP Method Registry</span> maintained by IANA, as</td><td> </td><td class="rblock"> registered within the <span class="insert">"Hypertext Transfer Protocol (HTTP) Method"</span></td><td class="lineno" valign="top"></td></tr> 447 399 <tr><td class="lineno" valign="top"></td><td class="lblock"> defined in Section 8.1.</td><td> </td><td class="rblock"><span class="insert"> registry</span> maintained by IANA, as defined in Section 8.1.</td><td class="lineno" valign="top"></td></tr> … … 457 409 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 458 410 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 459 <tr bgcolor="gray" ><td></td><th><a name="part-l1 3" /><small>skipping to change at</small><em> page 23, line 5</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 23, line 5</em></th><td></td></tr>411 <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 23, line 5</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 23, line 5</em></th><td></td></tr> 460 412 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 461 413 <tr><td class="lineno" valign="top"></td><td class="left">4.2.1. Safe Methods</td><td> </td><td class="right">4.2.1. Safe Methods</td><td class="lineno" valign="top"></td></tr> … … 468 420 <tr><td class="lineno" valign="top"></td><td class="left"> property, or unusual burden on the origin server.</td><td> </td><td class="right"> property, or unusual burden on the origin server.</td><td class="lineno" valign="top"></td></tr> 469 421 <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 <tr><td><a name="diff002 5" /></td></tr>422 <tr><td><a name="diff0021" /></td></tr> 471 423 <tr><td class="lineno" valign="top"></td><td class="lblock"> This definition of safe <span class="delete">methods</span> does not prevent an implementation</td><td> </td><td class="rblock"> This definition of safe <span class="insert">method</span> does not prevent an implementation</td><td class="lineno" valign="top"></td></tr> 472 424 <tr><td class="lineno" valign="top"></td><td class="lblock"> from including behavior that is potentially harmful, not entirely</td><td> </td><td class="rblock"> from including behavior that is potentially harmful, <span class="insert">that is</span> not</td><td class="lineno" valign="top"></td></tr> … … 491 443 <tr><td class="lineno" valign="top"></td><td class="left"> untrusted content.</td><td> </td><td class="right"> untrusted content.</td><td class="lineno" valign="top"></td></tr> 492 444 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 493 <tr bgcolor="gray" ><td></td><th><a name="part-l1 4" /><small>skipping to change at</small><em> page 23, line 39</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 23, line 39</em></th><td></td></tr>445 <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 23, line 39</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 23, line 39</em></th><td></td></tr> 494 446 <tr><td class="lineno" valign="top"></td><td class="left"> made aware of an unsafe action before it is requested.</td><td> </td><td class="right"> made aware of an unsafe action before it is requested.</td><td class="lineno" valign="top"></td></tr> 495 447 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 502 454 <tr><td class="lineno" valign="top"></td><td class="left"> resource is to perform an unsafe action, then the resource owner MUST</td><td> </td><td class="right"> resource is to perform an unsafe action, then the resource owner MUST</td><td class="lineno" valign="top"></td></tr> 503 455 <tr><td class="lineno" valign="top"></td><td class="left"> disable or disallow that action when it is accessed using a safe</td><td> </td><td class="right"> disable or disallow that action when it is accessed using a safe</td><td class="lineno" valign="top"></td></tr> 504 <tr><td><a name="diff002 6" /></td></tr>456 <tr><td><a name="diff0022" /></td></tr> 505 457 <tr><td class="lineno" valign="top"></td><td class="lblock"> request method. Failure to do so will result in unfortunate side<span class="delete">-</span></td><td> </td><td class="rblock"> request method. Failure to do so will result in unfortunate side</td><td class="lineno" valign="top"></td></tr> 506 458 <tr><td class="lineno" valign="top"></td><td class="left"> effects when automated processes perform a GET on every URI reference</td><td> </td><td class="right"> effects when automated processes perform a GET on every URI reference</td><td class="lineno" valign="top"></td></tr> … … 519 471 <tr><td class="lineno" valign="top"></td><td class="left"> what has been requested by the user; a server is free to log each</td><td> </td><td class="right"> what has been requested by the user; a server is free to log each</td><td class="lineno" valign="top"></td></tr> 520 472 <tr><td class="lineno" valign="top"></td><td class="left"> request separately, retain a revision control history, or implement</td><td> </td><td class="right"> request separately, retain a revision control history, or implement</td><td class="lineno" valign="top"></td></tr> 521 <tr><td><a name="diff002 7" /></td></tr>473 <tr><td><a name="diff0023" /></td></tr> 522 474 <tr><td class="lineno" valign="top"></td><td class="lblock"> other non-idempotent side<span class="delete">-</span>effects for each idempotent request.</td><td> </td><td class="rblock"> other non-idempotent side<span class="insert"> </span>effects for each idempotent request.</td><td class="lineno" valign="top"></td></tr> 523 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> … … 532 484 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 533 485 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 534 <tr bgcolor="gray" ><td></td><th><a name="part-l1 5" /><small>skipping to change at</small><em> page 26, line 14</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 26, line 14</em></th><td></td></tr>486 <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 26, line 14</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 26, line 14</em></th><td></td></tr> 535 487 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 536 488 <tr><td class="lineno" valign="top"></td><td class="left"> o Creating a new resource that has yet to be identified by the</td><td> </td><td class="right"> o Creating a new resource that has yet to be identified by the</td><td class="lineno" valign="top"></td></tr> … … 543 495 <tr><td class="lineno" valign="top"></td><td class="left"> POST request; almost all of the status codes defined by this</td><td> </td><td class="right"> POST request; almost all of the status codes defined by this</td><td class="lineno" valign="top"></td></tr> 544 496 <tr><td class="lineno" valign="top"></td><td class="left"> specification might be received in a response to POST (the exceptions</td><td> </td><td class="right"> specification might be received in a response to POST (the exceptions</td><td class="lineno" valign="top"></td></tr> 545 <tr><td><a name="diff002 8" /></td></tr>497 <tr><td><a name="diff0024" /></td></tr> 546 498 <tr><td class="lineno" valign="top"></td><td class="lblock"> being <span class="delete">206, 304,</span> and <span class="delete">416).</span></td><td> </td><td class="rblock"> being <span class="insert">206 (Partial Content), 304 (Not Modified),</span> and <span class="insert">416 (Range Not</span></td><td class="lineno" valign="top"></td></tr> 547 499 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Satisfiable)).</span></td><td class="lineno" valign="top"></td></tr> … … 557 509 <tr><td class="lineno" valign="top"></td><td class="left"> explicit freshness information (see Section 4.2.1 of [RFC7234]).</td><td> </td><td class="right"> explicit freshness information (see Section 4.2.1 of [RFC7234]).</td><td class="lineno" valign="top"></td></tr> 558 510 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 559 <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 28, line 18</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 28, line 19</em></th><td></td></tr> 560 <tr><td class="lineno" valign="top"></td><td class="left"> intentionally hidden by the server.</td><td> </td><td class="right"> intentionally hidden by the server.</td><td class="lineno" valign="top"></td></tr> 561 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 562 <tr><td class="lineno" valign="top"></td><td class="left"> An origin server MUST NOT send a validator header field</td><td> </td><td class="right"> An origin server MUST NOT send a validator header field</td><td class="lineno" valign="top"></td></tr> 563 <tr><td class="lineno" valign="top"></td><td class="left"> (Section 7.2), such as an ETag or Last-Modified field, in a</td><td> </td><td class="right"> (Section 7.2), such as an ETag or Last-Modified field, in a</td><td class="lineno" valign="top"></td></tr> 564 <tr><td class="lineno" valign="top"></td><td class="left"> successful response to PUT unless the request's representation data</td><td> </td><td class="right"> successful response to PUT unless the request's representation data</td><td class="lineno" valign="top"></td></tr> 565 <tr><td class="lineno" valign="top"></td><td class="left"> was saved without any transformation applied to the body (i.e., the</td><td> </td><td class="right"> was saved without any transformation applied to the body (i.e., the</td><td class="lineno" valign="top"></td></tr> 566 <tr><td class="lineno" valign="top"></td><td class="left"> resource's new representation data is identical to the representation</td><td> </td><td class="right"> resource's new representation data is identical to the representation</td><td class="lineno" valign="top"></td></tr> 567 <tr><td class="lineno" valign="top"></td><td class="left"> data received in the PUT request) and the validator field value</td><td> </td><td class="right"> data received in the PUT request) and the validator field value</td><td class="lineno" valign="top"></td></tr> 568 <tr><td class="lineno" valign="top"></td><td class="left"> reflects the new representation. This requirement allows a user</td><td> </td><td class="right"> reflects the new representation. This requirement allows a user</td><td class="lineno" valign="top"></td></tr> 569 <tr><td class="lineno" valign="top"></td><td class="left"> agent to know when the representation body it has in memory remains</td><td> </td><td class="right"> agent to know when the representation body it has in memory remains</td><td class="lineno" valign="top"></td></tr> 570 <tr><td><a name="diff0029" /></td></tr> 571 <tr><td class="lineno" valign="top"></td><td class="lblock"> current as a result of the PUT, thus not in need of <span class="delete">retrieving</span> again</td><td> </td><td class="rblock"> current as a result of the PUT, thus not in need of <span class="insert">being retrieved</span></td><td class="lineno" valign="top"></td></tr> 572 <tr><td class="lineno" valign="top"></td><td class="lblock"> from the origin server, and that the new validator(s) received in the</td><td> </td><td class="rblock"> again from the origin server, and that the new validator(s) received</td><td class="lineno" valign="top"></td></tr> 573 <tr><td class="lineno" valign="top"></td><td class="lblock"> response can be used for future conditional requests in order to</td><td> </td><td class="rblock"> in the response can be used for future conditional requests in order</td><td class="lineno" valign="top"></td></tr> 574 <tr><td class="lineno" valign="top"></td><td class="lblock"> prevent accidental overwrites (Section 5.2).</td><td> </td><td class="rblock"> to prevent accidental overwrites (Section 5.2).</td><td class="lineno" valign="top"></td></tr> 575 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 576 <tr><td class="lineno" valign="top"></td><td class="left"> The fundamental difference between the POST and PUT methods is</td><td> </td><td class="right"> The fundamental difference between the POST and PUT methods is</td><td class="lineno" valign="top"></td></tr> 577 <tr><td class="lineno" valign="top"></td><td class="left"> highlighted by the different intent for the enclosed representation.</td><td> </td><td class="right"> highlighted by the different intent for the enclosed representation.</td><td class="lineno" valign="top"></td></tr> 578 <tr><td class="lineno" valign="top"></td><td class="left"> The target resource in a POST request is intended to handle the</td><td> </td><td class="right"> The target resource in a POST request is intended to handle the</td><td class="lineno" valign="top"></td></tr> 579 <tr><td class="lineno" valign="top"></td><td class="left"> enclosed representation according to the resource's own semantics,</td><td> </td><td class="right"> enclosed representation according to the resource's own semantics,</td><td class="lineno" valign="top"></td></tr> 580 <tr><td class="lineno" valign="top"></td><td class="left"> whereas the enclosed representation in a PUT request is defined as</td><td> </td><td class="right"> whereas the enclosed representation in a PUT request is defined as</td><td class="lineno" valign="top"></td></tr> 581 <tr><td class="lineno" valign="top"></td><td class="left"> replacing the state of the target resource. Hence, the intent of PUT</td><td> </td><td class="right"> replacing the state of the target resource. Hence, the intent of PUT</td><td class="lineno" valign="top"></td></tr> 582 <tr><td class="lineno" valign="top"></td><td class="left"> is idempotent and visible to intermediaries, even though the exact</td><td> </td><td class="right"> is idempotent and visible to intermediaries, even though the exact</td><td class="lineno" valign="top"></td></tr> 583 <tr><td class="lineno" valign="top"></td><td class="left"> effect is only known by the origin server.</td><td> </td><td class="right"> effect is only known by the origin server.</td><td class="lineno" valign="top"></td></tr> 584 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 585 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 586 <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 28, line 43</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 28, line 44</em></th><td></td></tr> 511 <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 28, line 43</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 28, line 44</em></th><td></td></tr> 587 512 <tr><td class="lineno" valign="top"></td><td class="left"> knows which target resource is desired. A service that selects a</td><td> </td><td class="right"> knows which target resource is desired. A service that selects a</td><td class="lineno" valign="top"></td></tr> 588 513 <tr><td class="lineno" valign="top"></td><td class="left"> proper URI on behalf of the client, after receiving a state-changing</td><td> </td><td class="right"> proper URI on behalf of the client, after receiving a state-changing</td><td class="lineno" valign="top"></td></tr> … … 595 520 <tr><td class="lineno" valign="top"></td><td class="left"> regarding whether or not to redirect the request.</td><td> </td><td class="right"> regarding whether or not to redirect the request.</td><td class="lineno" valign="top"></td></tr> 596 521 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 597 <tr><td><a name="diff00 30" /></td></tr>522 <tr><td><a name="diff0025" /></td></tr> 598 523 <tr><td class="lineno" valign="top"></td><td class="lblock"> A PUT request applied to the target resource can have side<span class="delete">-</span>effects on</td><td> </td><td class="rblock"> A PUT request applied to the target resource can have side<span class="insert"> </span>effects on</td><td class="lineno" valign="top"></td></tr> 599 524 <tr><td class="lineno" valign="top"></td><td class="left"> other resources. For example, an article might have a URI for</td><td> </td><td class="right"> other resources. For example, an article might have a URI for</td><td class="lineno" valign="top"></td></tr> … … 608 533 <tr><td class="lineno" valign="top"></td><td class="left"> An origin server that allows PUT on a given target resource MUST send</td><td> </td><td class="right"> An origin server that allows PUT on a given target resource MUST send</td><td class="lineno" valign="top"></td></tr> 609 534 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 610 <tr bgcolor="gray" ><td></td><th><a name="part-l1 8" /><small>skipping to change at</small><em> page 30, line 31</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 30, line 33</em></th><td></td></tr>535 <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 30, line 31</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 30, line 33</em></th><td></td></tr> 611 536 <tr><td class="lineno" valign="top"></td><td class="left"> The CONNECT method requests that the recipient establish a tunnel to</td><td> </td><td class="right"> The CONNECT method requests that the recipient establish a tunnel to</td><td class="lineno" valign="top"></td></tr> 612 537 <tr><td class="lineno" valign="top"></td><td class="left"> the destination origin server identified by the request-target and,</td><td> </td><td class="right"> the destination origin server identified by the request-target and,</td><td class="lineno" valign="top"></td></tr> … … 619 544 <tr><td class="lineno" valign="top"></td><td class="left"> CONNECT is intended only for use in requests to a proxy. An origin</td><td> </td><td class="right"> CONNECT is intended only for use in requests to a proxy. An origin</td><td class="lineno" valign="top"></td></tr> 620 545 <tr><td class="lineno" valign="top"></td><td class="left"> server that receives a CONNECT request for itself MAY respond with a</td><td> </td><td class="right"> server that receives a CONNECT request for itself MAY respond with a</td><td class="lineno" valign="top"></td></tr> 621 <tr><td><a name="diff00 31" /></td></tr>546 <tr><td><a name="diff0026" /></td></tr> 622 547 <tr><td class="lineno" valign="top"></td><td class="lblock"> 2xx status code to indicate that a connection is established.</td><td> </td><td class="rblock"> 2xx <span class="insert">(Successful)</span> status code to indicate that a connection is</td><td class="lineno" valign="top"></td></tr> 623 548 <tr><td class="lineno" valign="top"></td><td class="lblock"> However, most origin servers do not implement CONNECT.</td><td> </td><td class="rblock"> established. However, most origin servers do not implement CONNECT.</td><td class="lineno" valign="top"></td></tr> … … 633 558 <tr><td class="lineno" valign="top"></td><td class="left"> The recipient proxy can establish a tunnel either by directly</td><td> </td><td class="right"> The recipient proxy can establish a tunnel either by directly</td><td class="lineno" valign="top"></td></tr> 634 559 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 635 <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 31, line 42</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 31, line 43</em></th><td></td></tr> 636 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 637 <tr><td class="lineno" valign="top"></td><td class="left"> A payload within a CONNECT request message has no defined semantics;</td><td> </td><td class="right"> A payload within a CONNECT request message has no defined semantics;</td><td class="lineno" valign="top"></td></tr> 638 <tr><td class="lineno" valign="top"></td><td class="left"> sending a payload body on a CONNECT request might cause some existing</td><td> </td><td class="right"> sending a payload body on a CONNECT request might cause some existing</td><td class="lineno" valign="top"></td></tr> 639 <tr><td class="lineno" valign="top"></td><td class="left"> implementations to reject the request.</td><td> </td><td class="right"> implementations to reject the request.</td><td class="lineno" valign="top"></td></tr> 640 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 641 <tr><td class="lineno" valign="top"></td><td class="left"> Responses to the CONNECT method are not cacheable.</td><td> </td><td class="right"> Responses to the CONNECT method are not cacheable.</td><td class="lineno" valign="top"></td></tr> 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> 643 <tr><td class="lineno" valign="top"></td><td class="left">4.3.7. OPTIONS</td><td> </td><td class="right">4.3.7. OPTIONS</td><td class="lineno" valign="top"></td></tr> 644 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 645 <tr><td class="lineno" valign="top"></td><td class="left"> The OPTIONS method requests information about the communication</td><td> </td><td class="right"> The OPTIONS method requests information about the communication</td><td class="lineno" valign="top"></td></tr> 646 <tr><td><a name="diff0032" /></td></tr> 647 <tr><td class="lineno" valign="top"></td><td class="lblock"> options available for the target resource, <span class="delete">either at</span> the origin</td><td> </td><td class="rblock"> options available for the target resource, <span class="insert">at either</span> the origin</td><td class="lineno" valign="top"></td></tr> 648 <tr><td class="lineno" valign="top"></td><td class="left"> server or an intervening intermediary. This method allows a client</td><td> </td><td class="right"> server or an intervening intermediary. This method allows a client</td><td class="lineno" valign="top"></td></tr> 649 <tr><td class="lineno" valign="top"></td><td class="left"> to determine the options and/or requirements associated with a</td><td> </td><td class="right"> to determine the options and/or requirements associated with a</td><td class="lineno" valign="top"></td></tr> 650 <tr><td class="lineno" valign="top"></td><td class="left"> resource, or the capabilities of a server, without implying a</td><td> </td><td class="right"> resource, or the capabilities of a server, without implying a</td><td class="lineno" valign="top"></td></tr> 651 <tr><td class="lineno" valign="top"></td><td class="left"> resource action.</td><td> </td><td class="right"> resource action.</td><td class="lineno" valign="top"></td></tr> 652 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 653 <tr><td class="lineno" valign="top"></td><td class="left"> An OPTIONS request with an asterisk ("*") as the request-target</td><td> </td><td class="right"> An OPTIONS request with an asterisk ("*") as the request-target</td><td class="lineno" valign="top"></td></tr> 654 <tr><td class="lineno" valign="top"></td><td class="left"> (Section 5.3 of [RFC7230]) applies to the server in general rather</td><td> </td><td class="right"> (Section 5.3 of [RFC7230]) applies to the server in general rather</td><td class="lineno" valign="top"></td></tr> 655 <tr><td class="lineno" valign="top"></td><td class="left"> than to a specific resource. Since a server's communication options</td><td> </td><td class="right"> than to a specific resource. Since a server's communication options</td><td class="lineno" valign="top"></td></tr> 656 <tr><td class="lineno" valign="top"></td><td class="left"> typically depend on the resource, the "*" request is only useful as a</td><td> </td><td class="right"> typically depend on the resource, the "*" request is only useful as a</td><td class="lineno" valign="top"></td></tr> 657 <tr><td class="lineno" valign="top"></td><td class="left"> "ping" or "no-op" type of method; it does nothing beyond allowing the</td><td> </td><td class="right"> "ping" or "no-op" type of method; it does nothing beyond allowing the</td><td class="lineno" valign="top"></td></tr> 658 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 659 <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><small>skipping to change at</small><em> page 34, line 14</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 34, line 14</em></th><td></td></tr> 560 <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 34, line 14</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 34, line 14</em></th><td></td></tr> 660 561 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 661 562 <tr><td class="lineno" valign="top"></td><td class="left">5.1.1. Expect</td><td> </td><td class="right">5.1.1. Expect</td><td class="lineno" valign="top"></td></tr> … … 668 569 <tr><td class="lineno" valign="top"></td><td class="left"> Expect = "100-continue"</td><td> </td><td class="right"> Expect = "100-continue"</td><td class="lineno" valign="top"></td></tr> 669 570 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 670 <tr><td><a name="diff00 33" /></td></tr>571 <tr><td><a name="diff0027" /></td></tr> 671 572 <tr><td class="lineno" valign="top"></td><td class="lblock"> The Expect field-value is case<span class="delete">-</span>insensitive.</td><td> </td><td class="rblock"> The Expect field-value is case<span class="insert"> </span>insensitive.</td><td class="lineno" valign="top"></td></tr> 672 573 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 681 582 <tr><td class="lineno" valign="top"></td><td class="left"> success, redirect, or error response. This allows the client to wait</td><td> </td><td class="right"> success, redirect, or error response. This allows the client to wait</td><td class="lineno" valign="top"></td></tr> 682 583 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 683 <tr bgcolor="gray" ><td></td><th><a name="part-l 21" /><small>skipping to change at</small><em> page 36, line 12</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 36, line 12</em></th><td></td></tr>584 <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 36, line 12</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 36, line 12</em></th><td></td></tr> 684 585 <tr><td class="lineno" valign="top"></td><td class="left"> determined by examining just the request-line and header fields, or</td><td> </td><td class="right"> determined by examining just the request-line and header fields, or</td><td class="lineno" valign="top"></td></tr> 685 586 <tr><td class="lineno" valign="top"></td><td class="left"> begin forwarding the request toward the origin server by sending a</td><td> </td><td class="right"> begin forwarding the request toward the origin server by sending a</td><td class="lineno" valign="top"></td></tr> … … 692 593 <tr><td class="lineno" valign="top"></td><td class="left"> Note: The Expect header field was added after the original</td><td> </td><td class="right"> Note: The Expect header field was added after the original</td><td class="lineno" valign="top"></td></tr> 693 594 <tr><td class="lineno" valign="top"></td><td class="left"> publication of HTTP/1.1 [RFC2068] as both the means to request an</td><td> </td><td class="right"> publication of HTTP/1.1 [RFC2068] as both the means to request an</td><td class="lineno" valign="top"></td></tr> 694 <tr><td><a name="diff00 34" /></td></tr>595 <tr><td><a name="diff0028" /></td></tr> 695 596 <tr><td class="lineno" valign="top"></td><td class="lblock"> interim 100 response and the general mechanism for indicating</td><td> </td><td class="rblock"> interim 100 <span class="insert">(Continue)</span> response and the general mechanism for</td><td class="lineno" valign="top"></td></tr> 696 597 <tr><td class="lineno" valign="top"></td><td class="lblock"> must-understand extensions. However, the extension mechanism has</td><td> </td><td class="rblock"> indicating must-understand extensions. However, the extension</td><td class="lineno" valign="top"></td></tr> … … 711 612 <tr><td class="lineno" valign="top"></td><td class="left"> Max-Forwards = 1*DIGIT</td><td> </td><td class="right"> Max-Forwards = 1*DIGIT</td><td class="lineno" valign="top"></td></tr> 712 613 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 713 <tr bgcolor="gray" ><td></td><th><a name="part-l 22" /><small>skipping to change at</small><em> page 39, line 12</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 39, line 12</em></th><td></td></tr>614 <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 39, line 12</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 39, line 12</em></th><td></td></tr> 714 615 <tr><td class="lineno" valign="top"></td><td class="left"> to be unlikely given the lack of any "q" parameters in the IANA</td><td> </td><td class="right"> to be unlikely given the lack of any "q" parameters in the IANA</td><td class="lineno" valign="top"></td></tr> 715 616 <tr><td class="lineno" valign="top"></td><td class="left"> media type registry and the rare usage of any media type</td><td> </td><td class="right"> media type registry and the rare usage of any media type</td><td class="lineno" valign="top"></td></tr> … … 722 623 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 723 624 <tr><td class="lineno" valign="top"></td><td class="left"> is interpreted as "I prefer audio/basic, but send me any audio type</td><td> </td><td class="right"> is interpreted as "I prefer audio/basic, but send me any audio type</td><td class="lineno" valign="top"></td></tr> 724 <tr><td><a name="diff00 35" /></td></tr>625 <tr><td><a name="diff0029" /></td></tr> 725 626 <tr><td class="lineno" valign="top"></td><td class="lblock"> if it is the best available after an 80% mark<span class="delete">-</span>down in quality".</td><td> </td><td class="rblock"> if it is the best available after an 80% markdown in quality".</td><td class="lineno" valign="top"></td></tr> 726 627 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 735 636 <tr><td class="lineno" valign="top"></td><td class="left"> A more elaborate example is</td><td> </td><td class="right"> A more elaborate example is</td><td class="lineno" valign="top"></td></tr> 736 637 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 737 <tr bgcolor="gray" ><td></td><th><a name="part-l2 3" /><small>skipping to change at</small><em> page 44, line 30</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 44, line 30</em></th><td></td></tr>638 <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><small>skipping to change at</small><em> page 44, line 30</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 44, line 30</em></th><td></td></tr> 738 639 <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 640 <tr><td class="lineno" valign="top"></td><td class="left"> | From | Section 5.5.1 |</td><td> </td><td class="right"> | From | Section 5.5.1 |</td><td class="lineno" valign="top"></td></tr> … … 746 647 <tr><td class="lineno" valign="top"></td><td class="left"> The "From" header field contains an Internet email address for a</td><td> </td><td class="right"> The "From" header field contains an Internet email address for a</td><td class="lineno" valign="top"></td></tr> 747 648 <tr><td class="lineno" valign="top"></td><td class="left"> human user who controls the requesting user agent. The address ought</td><td> </td><td class="right"> human user who controls the requesting user agent. The address ought</td><td class="lineno" valign="top"></td></tr> 748 <tr><td><a name="diff003 6" /></td></tr>649 <tr><td><a name="diff0030" /></td></tr> 749 650 <tr><td class="lineno" valign="top"></td><td class="lblock"> to be machine<span class="delete">-</span>usable, as defined by "mailbox" in Section 3.4 of</td><td> </td><td class="rblock"> to be machine<span class="insert"> </span>usable, as defined by "mailbox" in Section 3.4 of</td><td class="lineno" valign="top"></td></tr> 750 651 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC5322]:</td><td> </td><td class="right"> [RFC5322]:</td><td class="lineno" valign="top"></td></tr> … … 759 660 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 760 661 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 761 <tr bgcolor="gray" ><td></td><th><a name="part-l2 4" /><small>skipping to change at</small><em> page 45, line 31</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 45, line 31</em></th><td></td></tr>662 <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><small>skipping to change at</small><em> page 45, line 31</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 45, line 31</em></th><td></td></tr> 762 663 <tr><td class="lineno" valign="top"></td><td class="left"> denying links from other sites (so-called "deep linking") or</td><td> </td><td class="right"> denying links from other sites (so-called "deep linking") or</td><td class="lineno" valign="top"></td></tr> 763 664 <tr><td class="lineno" valign="top"></td><td class="left"> restricting cross-site request forgery (CSRF), but not all requests</td><td> </td><td class="right"> restricting cross-site request forgery (CSRF), but not all requests</td><td class="lineno" valign="top"></td></tr> … … 770 671 <tr><td class="lineno" valign="top"></td><td class="left"> If the target URI was obtained from a source that does not have its</td><td> </td><td class="right"> If the target URI was obtained from a source that does not have its</td><td class="lineno" valign="top"></td></tr> 771 672 <tr><td class="lineno" valign="top"></td><td class="left"> own URI (e.g., input from the user keyboard, or an entry within the</td><td> </td><td class="right"> own URI (e.g., input from the user keyboard, or an entry within the</td><td class="lineno" valign="top"></td></tr> 772 <tr><td><a name="diff003 7" /></td></tr>673 <tr><td><a name="diff0031" /></td></tr> 773 674 <tr><td class="lineno" valign="top"></td><td class="lblock"> user's bookmarks/favorites), the user agent MUST either exclude</td><td> </td><td class="rblock"> user's bookmarks/favorites), the user agent MUST either exclude<span class="insert"> the</span></td><td class="lineno" valign="top"></td></tr> 774 675 <tr><td class="lineno" valign="top"></td><td class="left"> Referer or send it with a value of "about:blank".</td><td> </td><td class="right"> Referer or send it with a value of "about:blank".</td><td class="lineno" valign="top"></td></tr> … … 788 689 <tr><td class="lineno" valign="top"></td><td class="left"> Some intermediaries have been known to indiscriminately remove</td><td> </td><td class="right"> Some intermediaries have been known to indiscriminately remove</td><td class="lineno" valign="top"></td></tr> 789 690 <tr><td class="lineno" valign="top"></td><td class="left"> Referer header fields from outgoing requests. This has the</td><td> </td><td class="right"> Referer header fields from outgoing requests. This has the</td><td class="lineno" valign="top"></td></tr> 790 <tr><td><a name="diff003 8" /></td></tr>691 <tr><td><a name="diff0032" /></td></tr> 791 692 <tr><td class="lineno" valign="top"></td><td class="lblock"> unfortunate side<span class="delete">-</span>effect of interfering with protection against CSRF</td><td> </td><td class="rblock"> unfortunate side<span class="insert"> </span>effect of interfering with protection against CSRF</td><td class="lineno" valign="top"></td></tr> 792 693 <tr><td class="lineno" valign="top"></td><td class="left"> attacks, which can be far more harmful to their users.</td><td> </td><td class="right"> attacks, which can be far more harmful to their users.</td><td class="lineno" valign="top"></td></tr> … … 804 705 <tr><td class="lineno" valign="top"></td><td class="left"> agent originating the request, which is often used by servers to help</td><td> </td><td class="right"> agent originating the request, which is often used by servers to help</td><td class="lineno" valign="top"></td></tr> 805 706 <tr><td class="lineno" valign="top"></td><td class="left"> identify the scope of reported interoperability problems, to work</td><td> </td><td class="right"> identify the scope of reported interoperability problems, to work</td><td class="lineno" valign="top"></td></tr> 806 <tr><td><a name="diff003 9" /></td></tr>707 <tr><td><a name="diff0033" /></td></tr> 807 708 <tr><td class="lineno" valign="top"></td><td class="lblock"> around or tailor responses to avoid particular user<span class="delete"> </span>agent</td><td> </td><td class="rblock"> around or tailor responses to avoid particular user<span class="insert">-</span>agent</td><td class="lineno" valign="top"></td></tr> 808 709 <tr><td class="lineno" valign="top"></td><td class="left"> limitations, and for analytics regarding browser or operating system</td><td> </td><td class="right"> limitations, and for analytics regarding browser or operating system</td><td class="lineno" valign="top"></td></tr> … … 814 715 <tr><td class="lineno" valign="top"></td><td class="left"> The User-Agent field-value consists of one or more product</td><td> </td><td class="right"> The User-Agent field-value consists of one or more product</td><td class="lineno" valign="top"></td></tr> 815 716 <tr><td class="lineno" valign="top"></td><td class="left"> identifiers, each followed by zero or more comments (Section 3.2 of</td><td> </td><td class="right"> identifiers, each followed by zero or more comments (Section 3.2 of</td><td class="lineno" valign="top"></td></tr> 816 <tr><td><a name="diff00 40" /></td></tr>717 <tr><td><a name="diff0034" /></td></tr> 817 718 <tr><td class="lineno" valign="top"></td><td class="lblock"> [RFC7230]), which together identify the user<span class="delete"> </span>agent software and its</td><td> </td><td class="rblock"> [RFC7230]), which together identify the user<span class="insert">-</span>agent software and its</td><td class="lineno" valign="top"></td></tr> 818 719 <tr><td class="lineno" valign="top"></td><td class="left"> significant subproducts. By convention, the product identifiers are</td><td> </td><td class="right"> significant subproducts. By convention, the product identifiers are</td><td class="lineno" valign="top"></td></tr> 819 720 <tr><td class="lineno" valign="top"></td><td class="left"> listed in decreasing order of their significance for identifying the</td><td> </td><td class="right"> listed in decreasing order of their significance for identifying the</td><td class="lineno" valign="top"></td></tr> 820 <tr><td><a name="diff00 41" /></td></tr>721 <tr><td><a name="diff0035" /></td></tr> 821 722 <tr><td class="lineno" valign="top"></td><td class="lblock"> user<span class="delete"> </span>agent software. Each product identifier consists of a name and</td><td> </td><td class="rblock"> user<span class="insert">-</span>agent software. Each product identifier consists of a name and</td><td class="lineno" valign="top"></td></tr> 822 723 <tr><td class="lineno" valign="top"></td><td class="left"> optional version.</td><td> </td><td class="right"> optional version.</td><td class="lineno" valign="top"></td></tr> … … 827 728 <tr><td class="lineno" valign="top"></td><td class="left"> A sender SHOULD limit generated product identifiers to what is</td><td> </td><td class="right"> A sender SHOULD limit generated product identifiers to what is</td><td class="lineno" valign="top"></td></tr> 828 729 <tr><td class="lineno" valign="top"></td><td class="left"> necessary to identify the product; a sender MUST NOT generate</td><td> </td><td class="right"> necessary to identify the product; a sender MUST NOT generate</td><td class="lineno" valign="top"></td></tr> 829 <tr><td><a name="diff00 42" /></td></tr>730 <tr><td><a name="diff0036" /></td></tr> 830 731 <tr><td class="lineno" valign="top"></td><td class="lblock"> advertising or other non<span class="delete">-</span>essential information within the product</td><td> </td><td class="rblock"> advertising or other nonessential information within the product</td><td class="lineno" valign="top"></td></tr> 831 732 <tr><td class="lineno" valign="top"></td><td class="left"> identifier. A sender SHOULD NOT generate information in product-</td><td> </td><td class="right"> identifier. A sender SHOULD NOT generate information in product-</td><td class="lineno" valign="top"></td></tr> 832 733 <tr><td class="lineno" valign="top"></td><td class="left"> version that is not a version identifier (i.e., successive versions</td><td> </td><td class="right"> version that is not a version identifier (i.e., successive versions</td><td class="lineno" valign="top"></td></tr> 833 <tr><td><a name="diff0043" /></td></tr> 834 <tr><td class="lineno" valign="top"></td><td class="lblock"> of the same product name ought <span class="delete">to only</span> differ in the product-version</td><td> </td><td class="rblock"> of the same product name ought <span class="insert">only to</span> differ in the product-version</td><td class="lineno" valign="top"></td></tr> 734 <tr><td class="lineno" valign="top"></td><td class="left"> of the same product name ought only to differ in the product-version</td><td> </td><td class="right"> of the same product name ought only to differ in the product-version</td><td class="lineno" valign="top"></td></tr> 835 735 <tr><td class="lineno" valign="top"></td><td class="left"> portion of the product identifier).</td><td> </td><td class="right"> portion of the product identifier).</td><td class="lineno" valign="top"></td></tr> 836 736 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 840 740 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 841 741 <tr><td class="lineno" valign="top"></td><td class="left"> A user agent SHOULD NOT generate a User-Agent field containing</td><td> </td><td class="right"> A user agent SHOULD NOT generate a User-Agent field containing</td><td class="lineno" valign="top"></td></tr> 842 <tr><td class="lineno" valign="top"></td><td class="left"> needlessly fine-grained detail and SHOULD limit the addition of</td><td> </td><td class="right"> needlessly fine-grained detail and SHOULD limit the addition of</td><td class="lineno" valign="top"></td></tr> 742 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 743 <tr bgcolor="gray" ><td></td><th><a name="part-l22" /><small>skipping to change at</small><em> page 47, line 9</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 47, line 9</em></th><td></td></tr> 843 744 <tr><td class="lineno" valign="top"></td><td class="left"> subproducts by third parties. Overly long and detailed User-Agent</td><td> </td><td class="right"> subproducts by third parties. Overly long and detailed User-Agent</td><td class="lineno" valign="top"></td></tr> 844 745 <tr><td class="lineno" valign="top"></td><td class="left"> field values increase request latency and the risk of a user being</td><td> </td><td class="right"> field values increase request latency and the risk of a user being</td><td class="lineno" valign="top"></td></tr> … … 851 752 <tr><td class="lineno" valign="top"></td><td class="left"> that the user intentionally desires to see responses tailored for</td><td> </td><td class="right"> that the user intentionally desires to see responses tailored for</td><td class="lineno" valign="top"></td></tr> 852 753 <tr><td class="lineno" valign="top"></td><td class="left"> that identified user agent, even if they might not work as well for</td><td> </td><td class="right"> that identified user agent, even if they might not work as well for</td><td class="lineno" valign="top"></td></tr> 853 <tr><td><a name="diff00 44" /></td></tr>754 <tr><td><a name="diff0037" /></td></tr> 854 755 <tr><td class="lineno" valign="top"></td><td class="lblock"> the actual user agent being <span class="delete">us</span>ed.</td><td> </td><td class="rblock"> the actual user agent being <span class="insert">implement</span>ed.</td><td class="lineno" valign="top"></td></tr> 855 756 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 869 770 <tr><td class="lineno" valign="top"></td><td class="left"> For example, if an unrecognized status code of 471 is received by a</td><td> </td><td class="right"> For example, if an unrecognized status code of 471 is received by a</td><td class="lineno" valign="top"></td></tr> 870 771 <tr><td class="lineno" valign="top"></td><td class="left"> client, the client can assume that there was something wrong with its</td><td> </td><td class="right"> client, the client can assume that there was something wrong with its</td><td class="lineno" valign="top"></td></tr> 871 <tr><td><a name="diff00 45" /></td></tr>772 <tr><td><a name="diff0038" /></td></tr> 872 773 <tr><td class="lineno" valign="top"></td><td class="lblock"> request and treat the response as if it had received a 400 status</td><td> </td><td class="rblock"> request and treat the response as if it had received a 400 <span class="insert">(Bad</span></td><td class="lineno" valign="top"></td></tr> 873 774 <tr><td class="lineno" valign="top"></td><td class="lblock"> code. The response message will usually contain a representation</td><td> </td><td class="rblock"><span class="insert"> Request)</span> status code. The response message will usually contain a</td><td class="lineno" valign="top"></td></tr> … … 884 785 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 885 786 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 886 <tr bgcolor="gray" ><td></td><th><a name="part-l2 5" /><small>skipping to change at</small><em> page 48, line 14</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 48, line 14</em></th><td></td></tr>787 <tr bgcolor="gray" ><td></td><th><a name="part-l23" /><small>skipping to change at</small><em> page 48, line 14</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 48, line 14</em></th><td></td></tr> 887 788 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 888 789 <tr><td class="lineno" valign="top"></td><td class="left">6.1. Overview of Status Codes</td><td> </td><td class="right">6.1. Overview of Status Codes</td><td class="lineno" valign="top"></td></tr> … … 895 796 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 896 797 <tr><td class="lineno" valign="top"></td><td class="left"> Responses with status codes that are defined as cacheable by default</td><td> </td><td class="right"> Responses with status codes that are defined as cacheable by default</td><td class="lineno" valign="top"></td></tr> 897 <tr><td><a name="diff00 46" /></td></tr>798 <tr><td><a name="diff0039" /></td></tr> 898 799 <tr><td class="lineno" valign="top"></td><td class="lblock"> (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414, 501 in this</td><td> </td><td class="rblock"> (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414, <span class="insert">and</span> 501 in</td><td class="lineno" valign="top"></td></tr> 899 800 <tr><td class="lineno" valign="top"></td><td class="lblock"> specification) can be reused by a cache with heuristic expiration</td><td> </td><td class="rblock"> this specification) can be reused by a cache with heuristic</td><td class="lineno" valign="top"></td></tr> … … 912 813 <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> 913 814 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 914 <tr bgcolor="gray" ><td></td><th><a name="part-l2 6" /><small>skipping to change at</small><em> page 52, line 27</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 52, line 27</em></th><td></td></tr>815 <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 52, line 27</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 52, line 27</em></th><td></td></tr> 915 816 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 916 817 <tr><td class="lineno" valign="top"></td><td class="left">6.3.3. 202 Accepted</td><td> </td><td class="right">6.3.3. 202 Accepted</td><td class="lineno" valign="top"></td></tr> … … 923 824 <tr><td class="lineno" valign="top"></td><td class="left"> operation.</td><td> </td><td class="right"> operation.</td><td class="lineno" valign="top"></td></tr> 924 825 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 925 <tr><td><a name="diff004 7" /></td></tr>826 <tr><td><a name="diff0040" /></td></tr> 926 827 <tr><td class="lineno" valign="top"></td><td class="lblock"> The 202 response is intentionally non<span class="delete">-</span>committal. Its purpose is to</td><td> </td><td class="rblock"> The 202 response is intentionally noncommittal. Its purpose is to</td><td class="lineno" valign="top"></td></tr> 927 828 <tr><td class="lineno" valign="top"></td><td class="left"> allow a server to accept a request for some other process (perhaps a</td><td> </td><td class="right"> allow a server to accept a request for some other process (perhaps a</td><td class="lineno" valign="top"></td></tr> … … 936 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> 937 838 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 938 <tr bgcolor="gray" ><td></td><th><a name="part-l2 7" /><small>skipping to change at</small><em> page 56, line 6</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 56, line 6</em></th><td></td></tr>839 <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 56, line 6</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 56, line 6</em></th><td></td></tr> 939 840 <tr><td class="lineno" valign="top"></td><td class="left"> this specification because HTTP tries to remain orthogonal to the</td><td> </td><td class="right"> this specification because HTTP tries to remain orthogonal to the</td><td class="lineno" valign="top"></td></tr> 940 841 <tr><td class="lineno" valign="top"></td><td class="left"> definition of its payloads. In practice, the representation is</td><td> </td><td class="right"> definition of its payloads. In practice, the representation is</td><td class="lineno" valign="top"></td></tr> … … 947 848 <tr><td class="lineno" valign="top"></td><td class="left"> Section 4.2.2 of [RFC7234]).</td><td> </td><td class="right"> Section 4.2.2 of [RFC7234]).</td><td class="lineno" valign="top"></td></tr> 948 849 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 949 <tr><td><a name="diff004 8" /></td></tr>850 <tr><td><a name="diff0041" /></td></tr> 950 851 <tr><td class="lineno" valign="top"></td><td class="lblock"> Note: The original proposal for 300 defined the URI header field</td><td> </td><td class="rblock"> Note: The original proposal for <span class="insert">the</span> 300 <span class="insert">response</span> defined the URI</td><td class="lineno" valign="top"></td></tr> 951 852 <tr><td class="lineno" valign="top"></td><td class="lblock"> as providing a list of alternative representations, such that it</td><td> </td><td class="rblock"> header field as providing a list of alternative representations,</td><td class="lineno" valign="top"></td></tr> … … 963 864 <tr><td class="lineno" valign="top"></td><td class="left"> resource has been assigned a new permanent URI and any future</td><td> </td><td class="right"> resource has been assigned a new permanent URI and any future</td><td class="lineno" valign="top"></td></tr> 964 865 <tr><td class="lineno" valign="top"></td><td class="left"> references to this resource ought to use one of the enclosed URIs.</td><td> </td><td class="right"> references to this resource ought to use one of the enclosed URIs.</td><td class="lineno" valign="top"></td></tr> 965 <tr><td><a name="diff004 9" /></td></tr>866 <tr><td><a name="diff0042" /></td></tr> 966 867 <tr><td class="lineno" valign="top"></td><td class="lblock"> Clients with link<span class="delete"> </span>editing capabilities ought to automatically re-link</td><td> </td><td class="rblock"> Clients with link<span class="insert">-</span>editing capabilities ought to automatically re-link</td><td class="lineno" valign="top"></td></tr> 967 868 <tr><td class="lineno" valign="top"></td><td class="left"> references to the effective request URI to one or more of the new</td><td> </td><td class="right"> references to the effective request URI to one or more of the new</td><td class="lineno" valign="top"></td></tr> … … 976 877 <tr><td class="lineno" valign="top"></td><td class="left"> Note: For historical reasons, a user agent MAY change the request</td><td> </td><td class="right"> Note: For historical reasons, a user agent MAY change the request</td><td class="lineno" valign="top"></td></tr> 977 878 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 978 <tr bgcolor="gray" ><td></td><th><a name="part-l2 8" /><small>skipping to change at</small><em> page 58, line 23</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 58, line 23</em></th><td></td></tr>879 <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 58, line 23</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 58, line 23</em></th><td></td></tr> 979 880 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 980 881 <tr><td class="lineno" valign="top"></td><td class="left"> The server SHOULD generate a Location header field in the response</td><td> </td><td class="right"> The server SHOULD generate a Location header field in the response</td><td class="lineno" valign="top"></td></tr> … … 987 888 <tr><td class="lineno" valign="top"></td><td class="left"> does not allow changing the request method from POST to GET. This</td><td> </td><td class="right"> does not allow changing the request method from POST to GET. This</td><td class="lineno" valign="top"></td></tr> 988 889 <tr><td class="lineno" valign="top"></td><td class="left"> specification defines no equivalent counterpart for 301 (Moved</td><td> </td><td class="right"> specification defines no equivalent counterpart for 301 (Moved</td><td class="lineno" valign="top"></td></tr> 989 <tr><td><a name="diff00 50" /></td></tr>890 <tr><td><a name="diff0043" /></td></tr> 990 891 <tr><td class="lineno" valign="top"></td><td class="lblock"> Permanently) ([RFC7238]<span class="delete">, however,</span> defines the status code 308</td><td> </td><td class="rblock"> Permanently) ([RFC7238]<span class="insert">; however, it</span> defines the status code 308</td><td class="lineno" valign="top"></td></tr> 991 892 <tr><td class="lineno" valign="top"></td><td class="left"> (Permanent Redirect) for this purpose).</td><td> </td><td class="right"> (Permanent Redirect) for this purpose).</td><td class="lineno" valign="top"></td></tr> … … 999 900 <tr><td class="lineno" valign="top"></td><td class="left"> condition. These status codes are applicable to any request method.</td><td> </td><td class="right"> condition. These status codes are applicable to any request method.</td><td class="lineno" valign="top"></td></tr> 1000 901 <tr><td class="lineno" valign="top"></td><td class="left"> User agents SHOULD display any included representation to the user.</td><td> </td><td class="right"> User agents SHOULD display any included representation to the user.</td><td class="lineno" valign="top"></td></tr> 1001 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1002 <tr><td class="lineno" valign="top"></td><td class="left">6.5.1. 400 Bad Request</td><td> </td><td class="right">6.5.1. 400 Bad Request</td><td class="lineno" valign="top"></td></tr> 1003 <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 <tr><td class="lineno" valign="top"></td><td class="left"> The 400 (Bad Request) status code indicates that the server cannot or</td><td> </td><td class="right"> The 400 (Bad Request) status code indicates that the server cannot or</td><td class="lineno" valign="top"></td></tr> 1005 <tr><td><a name="diff0051" /></td></tr> 1006 <tr><td class="lineno" valign="top"></td><td class="lblock"> will not process the request due to something <span class="delete">which</span> is perceived to</td><td> </td><td class="rblock"> will not process the request due to something <span class="insert">that</span> is perceived to be</td><td class="lineno" valign="top"></td></tr> 1007 <tr><td class="lineno" valign="top"></td><td class="lblock"> be a client error (e.g., malformed request syntax, invalid request</td><td> </td><td class="rblock"> a client error (e.g., malformed request syntax, invalid request</td><td class="lineno" valign="top"></td></tr> 1008 <tr><td class="lineno" valign="top"></td><td class="left"> message framing, or deceptive request routing).</td><td> </td><td class="right"> message framing, or deceptive request routing).</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">6.5.2. 402 Payment Required</td><td> </td><td class="right">6.5.2. 402 Payment Required</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"> The 402 (Payment Required) status code is reserved for future use.</td><td> </td><td class="right"> The 402 (Payment Required) status code is reserved for future use.</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">6.5.3. 403 Forbidden</td><td> </td><td class="right">6.5.3. 403 Forbidden</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"> The 403 (Forbidden) status code indicates that the server understood</td><td> </td><td class="right"> The 403 (Forbidden) status code indicates that the server understood</td><td class="lineno" valign="top"></td></tr> 1017 <tr><td class="lineno" valign="top"></td><td class="left"> the request but refuses to authorize it. A server that wishes to</td><td> </td><td class="right"> the request but refuses to authorize it. A server that wishes to</td><td class="lineno" valign="top"></td></tr> 1018 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1019 <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 66, line 9</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 66, line 9</em></th><td></td></tr> 902 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 903 <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 66, line 9</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 66, line 9</em></th><td></td></tr> 1020 904 <tr><td class="lineno" valign="top"></td><td class="left"> to be in UTC. A sender that generates HTTP-date values from a local</td><td> </td><td class="right"> to be in UTC. A sender that generates HTTP-date values from a local</td><td class="lineno" valign="top"></td></tr> 1021 905 <tr><td class="lineno" valign="top"></td><td class="left"> clock ought to use NTP ([RFC5905]) or some similar protocol to</td><td> </td><td class="right"> clock ought to use NTP ([RFC5905]) or some similar protocol to</td><td class="lineno" valign="top"></td></tr> … … 1028 912 <tr><td class="lineno" valign="top"></td><td class="left"> ; defined in Section 3.3 of [RFC5322]</td><td> </td><td class="right"> ; defined in Section 3.3 of [RFC5322]</td><td class="lineno" valign="top"></td></tr> 1029 913 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1030 <tr><td><a name="diff00 52" /></td></tr>914 <tr><td><a name="diff0044" /></td></tr> 1031 915 <tr><td class="lineno" valign="top"></td><td class="lblock"> day-name = %x4D.6F.6E ; "Mon", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock"> day-name = %x4D.6F.6E ; "Mon", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr> 1032 916 <tr><td class="lineno" valign="top"></td><td class="lblock"> / %x54.75.65 ; "Tue", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock"> / %x54.75.65 ; "Tue", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr> … … 1041 925 <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 926 <tr><td class="lineno" valign="top"></td><td class="left"> day = 2DIGIT</td><td> </td><td class="right"> day = 2DIGIT</td><td class="lineno" valign="top"></td></tr> 1043 <tr><td><a name="diff00 53" /></td></tr>927 <tr><td><a name="diff0045" /></td></tr> 1044 928 <tr><td class="lineno" valign="top"></td><td class="lblock"> month = %x4A.61.6E ; "Jan", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock"> month = %x4A.61.6E ; "Jan", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr> 1045 929 <tr><td class="lineno" valign="top"></td><td class="lblock"> / %x46.65.62 ; "Feb", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock"> / %x46.65.62 ; "Feb", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr> … … 1056 940 <tr><td class="lineno" valign="top"></td><td class="left"> year = 4DIGIT</td><td> </td><td class="right"> year = 4DIGIT</td><td class="lineno" valign="top"></td></tr> 1057 941 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1058 <tr><td><a name="diff00 54" /></td></tr>942 <tr><td><a name="diff0046" /></td></tr> 1059 943 <tr><td class="lineno" valign="top"></td><td class="lblock"> GMT = %x47.4D.54 ; "GMT", case<span class="delete">-</span>sensitive</td><td> </td><td class="rblock"> GMT = %x47.4D.54 ; "GMT", case<span class="insert"> </span>sensitive</td><td class="lineno" valign="top"></td></tr> 1060 944 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1073 957 <tr><td class="lineno" valign="top"></td><td class="left"> ; e.g., 02-Jun-82</td><td> </td><td class="right"> ; e.g., 02-Jun-82</td><td class="lineno" valign="top"></td></tr> 1074 958 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1075 <tr><td><a name="diff00 55" /></td></tr>959 <tr><td><a name="diff0047" /></td></tr> 1076 960 <tr><td class="lineno" valign="top"></td><td class="lblock"> day-name-l = %x4D.6F.6E.64.61.79 ; "Monday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock"> day-name-l = %x4D.6F.6E.64.61.79 ; "Monday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr> 1077 961 <tr><td class="lineno" valign="top"></td><td class="lblock"> / %x54.75.65.73.64.61.79 ; "Tuesday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock"> / %x54.75.65.73.64.61.79 ; "Tuesday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr> … … 1092 976 <tr><td class="lineno" valign="top"></td><td class="left"> constructs with the corresponding name ([RFC5322], Section 3.3).</td><td> </td><td class="right"> constructs with the corresponding name ([RFC5322], Section 3.3).</td><td class="lineno" valign="top"></td></tr> 1093 977 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1094 <tr bgcolor="gray" ><td></td><th><a name="part-l30" /><small>skipping to change at</small><em> page 69, line 5</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 69, line 5</em></th><td></td></tr> 1095 <tr><td class="lineno" valign="top"></td><td class="left"> The field value consists of a single URI-reference. When it has the</td><td> </td><td class="right"> The field value consists of a single URI-reference. When it has the</td><td class="lineno" valign="top"></td></tr> 1096 <tr><td class="lineno" valign="top"></td><td class="left"> form of a relative reference ([RFC3986], Section 4.2), the final</td><td> </td><td class="right"> form of a relative reference ([RFC3986], Section 4.2), the final</td><td class="lineno" valign="top"></td></tr> 1097 <tr><td class="lineno" valign="top"></td><td class="left"> value is computed by resolving it against the effective request URI</td><td> </td><td class="right"> value is computed by resolving it against the effective request URI</td><td class="lineno" valign="top"></td></tr> 1098 <tr><td class="lineno" valign="top"></td><td class="left"> ([RFC3986], Section 5).</td><td> </td><td class="right"> ([RFC3986], Section 5).</td><td class="lineno" valign="top"></td></tr> 1099 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1100 <tr><td class="lineno" valign="top"></td><td class="left"> For 201 (Created) responses, the Location value refers to the primary</td><td> </td><td class="right"> For 201 (Created) responses, the Location value refers to the primary</td><td class="lineno" valign="top"></td></tr> 1101 <tr><td class="lineno" valign="top"></td><td class="left"> resource created by the request. For 3xx (Redirection) responses,</td><td> </td><td class="right"> resource created by the request. For 3xx (Redirection) responses,</td><td class="lineno" valign="top"></td></tr> 1102 <tr><td class="lineno" valign="top"></td><td class="left"> the Location value refers to the preferred target resource for</td><td> </td><td class="right"> the Location value refers to the preferred target resource for</td><td class="lineno" valign="top"></td></tr> 1103 <tr><td class="lineno" valign="top"></td><td class="left"> automatically redirecting the request.</td><td> </td><td class="right"> automatically redirecting the request.</td><td class="lineno" valign="top"></td></tr> 1104 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1105 <tr><td><a name="diff0056" /></td></tr> 1106 <tr><td class="lineno" valign="top"></td><td class="lblock"> If the Location value provided in a 3xx (Redirection) does not have a</td><td> </td><td class="rblock"> If the Location value provided in a 3xx (Redirection) <span class="insert">response</span> does</td><td class="lineno" valign="top"></td></tr> 1107 <tr><td class="lineno" valign="top"></td><td class="lblock"> fragment component, a user agent MUST process the redirection as if</td><td> </td><td class="rblock"> not have a fragment component, a user agent MUST process the</td><td class="lineno" valign="top"></td></tr> 1108 <tr><td class="lineno" valign="top"></td><td class="lblock"> the value inherits the fragment component of the URI reference used</td><td> </td><td class="rblock"> redirection as if the value inherits the fragment component of the</td><td class="lineno" valign="top"></td></tr> 1109 <tr><td class="lineno" valign="top"></td><td class="lblock"> to generate the request target (i.e., the redirection inherits the</td><td> </td><td class="rblock"> URI reference used to generate the request target (i.e., the</td><td class="lineno" valign="top"></td></tr> 1110 <tr><td class="lineno" valign="top"></td><td class="lblock"> original reference's fragment, if any).</td><td> </td><td class="rblock"> redirection inherits the original reference's fragment, if any).</td><td class="lineno" valign="top"></td></tr> 1111 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1112 <tr><td class="lineno" valign="top"></td><td class="left"> For example, a GET request generated for the URI reference</td><td> </td><td class="right"> For example, a GET request generated for the URI reference</td><td class="lineno" valign="top"></td></tr> 1113 <tr><td class="lineno" valign="top"></td><td class="left"> "http://www.example.org/~tim" might result in a 303 (See Other)</td><td> </td><td class="right"> "http://www.example.org/~tim" might result in a 303 (See Other)</td><td class="lineno" valign="top"></td></tr> 1114 <tr><td class="lineno" valign="top"></td><td class="left"> response containing the header field:</td><td> </td><td class="right"> response containing the header field:</td><td class="lineno" valign="top"></td></tr> 1115 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1116 <tr><td class="lineno" valign="top"></td><td class="left"> Location: /People.html#tim</td><td> </td><td class="right"> Location: /People.html#tim</td><td class="lineno" valign="top"></td></tr> 1117 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1118 <tr><td class="lineno" valign="top"></td><td class="left"> which suggests that the user agent redirect to</td><td> </td><td class="right"> which suggests that the user agent redirect to</td><td class="lineno" valign="top"></td></tr> 1119 <tr><td class="lineno" valign="top"></td><td class="left"> "http://www.example.org/People.html#tim"</td><td> </td><td class="right"> "http://www.example.org/People.html#tim"</td><td class="lineno" valign="top"></td></tr> 1120 <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 class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1122 <tr bgcolor="gray" ><td></td><th><a name="part-l31" /><small>skipping to change at</small><em> page 70, line 30</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 70, line 30</em></th><td></td></tr> 978 <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 70, line 30</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 70, line 30</em></th><td></td></tr> 1123 979 <tr><td class="lineno" valign="top"></td><td class="left"> Retry-After: 120</td><td> </td><td class="right"> Retry-After: 120</td><td class="lineno" valign="top"></td></tr> 1124 980 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1131 987 <tr><td class="lineno" valign="top"></td><td class="left"> request target, might influence the origin server's process for</td><td> </td><td class="right"> request target, might influence the origin server's process for</td><td class="lineno" valign="top"></td></tr> 1132 988 <tr><td class="lineno" valign="top"></td><td class="left"> selecting and representing this response. The value consists of</td><td> </td><td class="right"> selecting and representing this response. The value consists of</td><td class="lineno" valign="top"></td></tr> 1133 <tr><td><a name="diff00 57" /></td></tr>989 <tr><td><a name="diff0048" /></td></tr> 1134 990 <tr><td class="lineno" valign="top"></td><td class="lblock"> either a single asterisk ("*") or a list of header field names (case<span class="delete">-</span></td><td> </td><td class="rblock"> either a single asterisk ("*") or a list of header field names (case</td><td class="lineno" valign="top"></td></tr> 1135 991 <tr><td class="lineno" valign="top"></td><td class="left"> insensitive).</td><td> </td><td class="right"> insensitive).</td><td class="lineno" valign="top"></td></tr> … … 1144 1000 <tr><td class="lineno" valign="top"></td><td class="left"> the request to the origin server. A proxy MUST NOT generate a Vary</td><td> </td><td class="right"> the request to the origin server. A proxy MUST NOT generate a Vary</td><td class="lineno" valign="top"></td></tr> 1145 1001 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1146 <tr bgcolor="gray" ><td></td><th><a name="part-l 32" /><small>skipping to change at</small><em> page 71, line 22</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 71, line 22</em></th><td></td></tr>1002 <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 71, line 22</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 71, line 22</em></th><td></td></tr> 1147 1003 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1148 1004 <tr><td class="lineno" valign="top"></td><td class="left"> An origin server might send Vary with a list of fields for two</td><td> </td><td class="right"> An origin server might send Vary with a list of fields for two</td><td class="lineno" valign="top"></td></tr> … … 1155 1011 <tr><td class="lineno" valign="top"></td><td class="left"> required to match a new request to the stored cache entry.</td><td> </td><td class="right"> required to match a new request to the stored cache entry.</td><td class="lineno" valign="top"></td></tr> 1156 1012 <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><a name="diff00 58" /></td></tr>1013 <tr><td><a name="diff0049" /></td></tr> 1158 1014 <tr><td class="lineno" valign="top"></td><td class="lblock"> 2. To inform user<span class="delete"> </span>agent recipients that this response is subject to</td><td> </td><td class="rblock"> 2. To inform user<span class="insert">-</span>agent recipients that this response is subject to</td><td class="lineno" valign="top"></td></tr> 1159 1015 <tr><td class="lineno" valign="top"></td><td class="left"> content negotiation (Section 5.3) and that a different</td><td> </td><td class="right"> content negotiation (Section 5.3) and that a different</td><td class="lineno" valign="top"></td></tr> … … 1168 1024 <tr><td class="lineno" valign="top"></td><td class="left"> configured to prevent cache transparency. For example, there is no</td><td> </td><td class="right"> configured to prevent cache transparency. For example, there is no</td><td class="lineno" valign="top"></td></tr> 1169 1025 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1170 <tr bgcolor="gray" ><td></td><th><a name="part-l3 3" /><small>skipping to change at</small><em> page 72, line 5</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 72, line 5</em></th><td></td></tr>1026 <tr bgcolor="gray" ><td></td><th><a name="part-l30" /><small>skipping to change at</small><em> page 72, line 5</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 72, line 5</em></th><td></td></tr> 1171 1027 <tr><td class="lineno" valign="top"></td><td class="left"> fields describe the selected representation chosen by the origin</td><td> </td><td class="right"> fields describe the selected representation chosen by the origin</td><td class="lineno" valign="top"></td></tr> 1172 1028 <tr><td class="lineno" valign="top"></td><td class="left"> server while handling the response. Note that, depending on the</td><td> </td><td class="right"> server while handling the response. Note that, depending on the</td><td class="lineno" valign="top"></td></tr> … … 1179 1035 <tr><td class="lineno" valign="top"></td><td class="left"> selected representation as a result of processing the request.</td><td> </td><td class="right"> selected representation as a result of processing the request.</td><td class="lineno" valign="top"></td></tr> 1180 1036 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1181 <tr><td><a name="diff005 9" /></td></tr>1037 <tr><td><a name="diff0050" /></td></tr> 1182 1038 <tr><td class="lineno" valign="top"></td><td class="lblock"> For example, an ETag header field in a 201 response communicates the</td><td> </td><td class="rblock"> For example, an ETag header field in a 201 <span class="insert">(Created)</span> response</td><td class="lineno" valign="top"></td></tr> 1183 1039 <tr><td class="lineno" valign="top"></td><td class="lblock"> entity-tag of the newly created resource's representation, so that it</td><td> </td><td class="rblock"> communicates the entity-tag of the newly created resource's</td><td class="lineno" valign="top"></td></tr> … … 1195 1051 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1196 1052 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1197 <tr bgcolor="gray" ><td></td><th><a name="part-l3 4" /><small>skipping to change at</small><em> page 74, line 6</em></th><th> </th><th><a name="part-r34" /><small>skipping to change at</small><em> page 74, line 6</em></th><td></td></tr>1053 <tr bgcolor="gray" ><td></td><th><a name="part-l31" /><small>skipping to change at</small><em> page 74, line 6</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 74, line 6</em></th><td></td></tr> 1198 1054 <tr><td class="lineno" valign="top"></td><td class="left"> An origin server SHOULD NOT generate a Server field containing</td><td> </td><td class="right"> An origin server SHOULD NOT generate a Server field containing</td><td class="lineno" valign="top"></td></tr> 1199 1055 <tr><td class="lineno" valign="top"></td><td class="left"> needlessly fine-grained detail and SHOULD limit the addition of</td><td> </td><td class="right"> needlessly fine-grained detail and SHOULD limit the addition of</td><td class="lineno" valign="top"></td></tr> … … 1206 1062 <tr><td class="lineno" valign="top"></td><td class="left">8.1. Method Registry</td><td> </td><td class="right">8.1. Method Registry</td><td class="lineno" valign="top"></td></tr> 1207 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> 1208 <tr><td><a name="diff00 60" /></td></tr>1064 <tr><td><a name="diff0051" /></td></tr> 1209 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> 1210 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> … … 1224 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> 1225 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> 1226 <tr><td><a name="diff00 61" /></td></tr>1082 <tr><td><a name="diff0052" /></td></tr> 1227 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> 1228 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> … … 1246 1102 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1247 1103 <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> 1248 <tr><td><a name="diff00 62" /></td></tr>1104 <tr><td><a name="diff0053" /></td></tr> 1249 1105 <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> 1250 1106 <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> … … 1265 1121 <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> 1266 1122 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1267 <tr><td><a name="diff00 63" /></td></tr>1123 <tr><td><a name="diff0054" /></td></tr> 1268 1124 <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> 1269 1125 <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> … … 1284 1140 <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> 1285 1141 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1286 <tr><td><a name="diff00 64" /></td></tr>1142 <tr><td><a name="diff0055" /></td></tr> 1287 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> 1288 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> … … 1290 1146 <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> 1291 1147 <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="diff0065" /></td></tr> 1293 <tr><td class="lineno" valign="top"></td><td class="lblock"> This <span class="delete">S</span>ection replaces the registration procedure for HTTP Status</td><td> </td><td class="rblock"> This <span class="insert">s</span>ection replaces the registration procedure for HTTP Status</td><td class="lineno" valign="top"></td></tr> 1148 <tr><td class="lineno" valign="top"></td><td class="left"> This section replaces the registration procedure for HTTP Status</td><td> </td><td class="right"> This section replaces the registration procedure for HTTP Status</td><td class="lineno" valign="top"></td></tr> 1294 1149 <tr><td class="lineno" valign="top"></td><td class="left"> Codes previously defined in Section 7.1 of [RFC2817].</td><td> </td><td class="right"> Codes previously defined in Section 7.1 of [RFC2817].</td><td class="lineno" valign="top"></td></tr> 1295 1150 <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 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> 1305 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> 1306 <tr><td><a name="diff00 66" /></td></tr>1161 <tr><td><a name="diff0056" /></td></tr> 1307 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> 1308 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> … … 1317 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> 1318 1173 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1319 <tr bgcolor="gray" ><td></td><th><a name="part-l3 5" /><small>skipping to change at</small><em> page 76, line 49</em></th><th> </th><th><a name="part-r35" /><small>skipping to change at</small><em> page 76, line 49</em></th><td></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> 1320 1175 <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> 1321 1176 <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> … … 1328 1183 <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> 1329 1184 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1330 <tr><td><a name="diff00 67" /></td></tr>1185 <tr><td><a name="diff0057" /></td></tr> 1331 1186 <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> 1332 1187 <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> … … 1342 1197 <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> 1343 1198 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1344 <tr bgcolor="gray" ><td></td><th><a name="part-l3 6" /><small>skipping to change at</small><em> page 77, line 48</em></th><th> </th><th><a name="part-r36" /><small>skipping to change at</small><em> page 77, line 48</em></th><td></td></tr>1199 <tr bgcolor="gray" ><td></td><th><a name="part-l33" /><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> 1345 1200 <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> 1346 1201 <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> … … 1353 1208 <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> 1354 1209 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1355 <tr><td><a name="diff00 68" /></td></tr>1210 <tr><td><a name="diff0058" /></td></tr> 1356 1211 <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> 1357 1212 <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> … … 1368 1223 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1369 1224 <tr><td class="lineno" valign="top"></td><td class="left"> Authors of specifications defining new fields are advised to keep the</td><td> </td><td class="right"> Authors of specifications defining new fields are advised to keep the</td><td class="lineno" valign="top"></td></tr> 1370 <tr><td><a name="diff0069" /></td></tr> 1371 <tr><td class="lineno" valign="top"></td><td class="lblock"> name as short as practical and <span class="delete">to not</span> prefix the name with "X-"</td><td> </td><td class="rblock"> name as short as practical and <span class="insert">not to</span> prefix the name with "X-"</td><td class="lineno" valign="top"></td></tr> 1225 <tr><td class="lineno" valign="top"></td><td class="left"> name as short as practical and not to prefix the name with "X-"</td><td> </td><td class="right"> name as short as practical and not to prefix the name with "X-"</td><td class="lineno" valign="top"></td></tr> 1372 1226 <tr><td class="lineno" valign="top"></td><td class="left"> unless the header field will never be used on the Internet. (The</td><td> </td><td class="right"> unless the header field will never be used on the Internet. (The</td><td class="lineno" valign="top"></td></tr> 1373 <tr><td><a name="diff0070" /></td></tr> 1374 <tr><td class="lineno" valign="top"></td><td class="lblock"> "<span class="delete">x</span>-" prefix idiom has been extensively misused in practice; it was</td><td> </td><td class="rblock"> "<span class="insert">X</span>-" prefix idiom has been extensively misused in practice; it was</td><td class="lineno" valign="top"></td></tr> 1227 <tr><td class="lineno" valign="top"></td><td class="left"> "X-" prefix idiom has been extensively misused in practice; it was</td><td> </td><td class="right"> "X-" prefix idiom has been extensively misused in practice; it was</td><td class="lineno" valign="top"></td></tr> 1375 1228 <tr><td class="lineno" valign="top"></td><td class="left"> intended to only be used as a mechanism for avoiding name collisions</td><td> </td><td class="right"> intended to only be used as a mechanism for avoiding name collisions</td><td class="lineno" valign="top"></td></tr> 1376 1229 <tr><td class="lineno" valign="top"></td><td class="left"> inside proprietary software or intranet processing, since the prefix</td><td> </td><td class="right"> inside proprietary software or intranet processing, since the prefix</td><td class="lineno" valign="top"></td></tr> 1377 1230 <tr><td class="lineno" valign="top"></td><td class="left"> would ensure that private names never collide with a newly registered</td><td> </td><td class="right"> would ensure that private names never collide with a newly registered</td><td class="lineno" valign="top"></td></tr> 1378 <tr><td><a name="diff0071" /></td></tr> 1379 <tr><td class="lineno" valign="top"></td><td class="lblock"> Internet name; see [BCP178] for further information)</td><td> </td><td class="rblock"> Internet name; see [BCP178] for further information)<span class="insert">.</span></td><td class="lineno" valign="top"></td></tr> 1231 <tr><td class="lineno" valign="top"></td><td class="left"> Internet name; see [BCP178] for further information).</td><td> </td><td class="right"> Internet name; see [BCP178] for further information).</td><td class="lineno" valign="top"></td></tr> 1380 1232 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1381 1233 <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> 1382 <tr><td><a name="diff00 72" /></td></tr>1234 <tr><td><a name="diff0059" /></td></tr> 1383 1235 <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> 1384 1236 <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> … … 1395 1247 <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> 1396 1248 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1397 <tr bgcolor="gray" ><td></td><th><a name="part-l3 7" /><small>skipping to change at</small><em> page 80, line 15</em></th><th> </th><th><a name="part-r37" /><small>skipping to change at</small><em> page 80, line 15</em></th><td></td></tr>1249 <tr bgcolor="gray" ><td></td><th><a name="part-l34" /><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> 1398 1250 <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> 1399 1251 <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> … … 1406 1258 <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> 1407 1259 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1408 <tr><td><a name="diff00 73" /></td></tr>1260 <tr><td><a name="diff0060" /></td></tr> 1409 1261 <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> 1410 1262 <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> … … 1419 1271 <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> 1420 1272 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1421 <tr bgcolor="gray" ><td></td><th><a name="part-l3 8" /><small>skipping to change at</small><em> page 80, line 48</em></th><th> </th><th><a name="part-r38" /><small>skipping to change at</small><em> page 80, line 48</em></th><td></td></tr>1273 <tr bgcolor="gray" ><td></td><th><a name="part-l35" /><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> 1422 1274 <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> 1423 1275 <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> … … 1430 1282 <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> 1431 1283 <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 <tr><td><a name="diff00 74" /></td></tr>1284 <tr><td><a name="diff0061" /></td></tr> 1433 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> 1434 1286 <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> … … 1438 1290 <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> 1439 1291 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1440 <tr><td><a name="diff00 75" /></td></tr>1292 <tr><td><a name="diff0062" /></td></tr> 1441 1293 <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> 1442 1294 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1452 1304 <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> 1453 1305 <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="diff00 76" /></td></tr>1306 <tr><td><a name="diff0063" /></td></tr> 1455 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> 1456 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> … … 1459 1311 <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> 1460 1312 <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 <tr><td><a name="diff00 77" /></td></tr>1313 <tr><td><a name="diff0064" /></td></tr> 1462 1314 <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> 1463 1315 <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> … … 1480 1332 <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> 1481 1333 <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> 1482 <tr><td><a name="diff00 78" /></td></tr>1334 <tr><td><a name="diff0065" /></td></tr> 1483 1335 <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> 1484 1336 <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> … … 1497 1349 <tr><td class="lineno" valign="top"></td><td class="left"> names, folders, or directories that have special significance to the</td><td> </td><td class="right"> names, folders, or directories that have special significance to the</td><td class="lineno" valign="top"></td></tr> 1498 1350 <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> 1499 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1351 <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-l36" /><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> 1500 1353 <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> 1501 1354 <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> 1502 <tr><td><a name="diff0079" /></td></tr> 1503 <tr><td class="lineno" valign="top"></td><td class="lblock"> current one, and use specially named paths or file names to send data</td><td> </td><td class="rblock"> current one, and <span class="insert">they</span> use specially named paths or file names to send</td><td class="lineno" valign="top"></td></tr> 1504 <tr><td class="lineno" valign="top"></td><td class="lblock"> to system devices. Similar naming conventions might exist within</td><td> </td><td class="rblock"> data to system devices. Similar naming conventions might exist</td><td class="lineno" valign="top"></td></tr> 1505 <tr><td class="lineno" valign="top"></td><td class="lblock"> other types of storage systems. Likewise, local storage systems have</td><td> </td><td class="rblock"> within other types of storage systems. Likewise, local storage</td><td class="lineno" valign="top"></td></tr> 1506 <tr><td class="lineno" valign="top"></td><td class="lblock"> an annoying tendency to prefer user-friendliness over security when</td><td> </td><td class="rblock"> systems have an annoying tendency to prefer user-friendliness over</td><td class="lineno" valign="top"></td></tr> 1507 <tr><td class="lineno" valign="top"></td><td class="lblock"> handling invalid or unexpected characters, recomposition of</td><td> </td><td class="rblock"> security when handling invalid or unexpected characters,</td><td class="lineno" valign="top"></td></tr> 1508 <tr><td class="lineno" valign="top"></td><td class="lblock"> decomposed characters, and case-normalization of case-insensitive</td><td> </td><td class="rblock"> recomposition of decomposed characters, and case-normalization of</td><td class="lineno" valign="top"></td></tr> 1509 <tr><td class="lineno" valign="top"></td><td class="lblock"> names.</td><td> </td><td class="rblock"> case-insensitive names.</td><td class="lineno" valign="top"></td></tr> 1510 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1511 <tr><td><a name="diff0080" /></td></tr> 1355 <tr><td class="lineno" valign="top"></td><td class="left"> current one, and they use specially named paths or file names to send</td><td> </td><td class="right"> current one, and they use specially named paths or file names to send</td><td class="lineno" valign="top"></td></tr> 1356 <tr><td class="lineno" valign="top"></td><td class="left"> data to system devices. Similar naming conventions might exist</td><td> </td><td class="right"> data to system devices. Similar naming conventions might exist</td><td class="lineno" valign="top"></td></tr> 1357 <tr><td class="lineno" valign="top"></td><td class="left"> within other types of storage systems. Likewise, local storage</td><td> </td><td class="right"> within other types of storage systems. Likewise, local storage</td><td class="lineno" valign="top"></td></tr> 1358 <tr><td class="lineno" valign="top"></td><td class="left"> systems have an annoying tendency to prefer user-friendliness over</td><td> </td><td class="right"> systems have an annoying tendency to prefer user-friendliness over</td><td class="lineno" valign="top"></td></tr> 1359 <tr><td class="lineno" valign="top"></td><td class="left"> security when handling invalid or unexpected characters,</td><td> </td><td class="right"> security when handling invalid or unexpected characters,</td><td class="lineno" valign="top"></td></tr> 1360 <tr><td class="lineno" valign="top"></td><td class="left"> recomposition of decomposed characters, and case-normalization of</td><td> </td><td class="right"> recomposition of decomposed characters, and case-normalization of</td><td class="lineno" valign="top"></td></tr> 1361 <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 <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="diff0066" /></td></tr> 1512 1364 <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> 1513 1365 <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> … … 1523 1375 <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> 1524 1376 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1525 <tr bgcolor="gray" ><td></td><th><a name="part-l3 9" /><small>skipping to change at</small><em> page 83, line 41</em></th><th> </th><th><a name="part-r39" /><small>skipping to change at</small><em> page 83, line 41</em></th><td></td></tr>1377 <tr bgcolor="gray" ><td></td><th><a name="part-l37" /><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> 1526 1378 <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> 1527 1379 <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> … … 1534 1386 <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> 1535 1387 <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> 1536 <tr><td><a name="diff00 81" /></td></tr>1388 <tr><td><a name="diff0067" /></td></tr> 1537 1389 <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> 1538 1390 <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> … … 1548 1400 <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> 1549 1401 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1550 <tr bgcolor="gray" ><td></td><th><a name="part-l 40" /><small>skipping to change at</small><em> page 86, line 15</em></th><th> </th><th><a name="part-r40" /><small>skipping to change at</small><em> page 86, line 15</em></th><td></td></tr>1402 <tr bgcolor="gray" ><td></td><th><a name="part-l38" /><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> 1551 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> 1552 1404 <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> … … 1559 1411 <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> 1560 1412 <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> 1561 <tr><td><a name="diff00 82" /></td></tr>1413 <tr><td><a name="diff0068" /></td></tr> 1562 1414 <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> 1563 1415 <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> 1564 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> 1565 1417 <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> 1566 <tr><td><a name="diff00 83" /></td></tr>1418 <tr><td><a name="diff0069" /></td></tr> 1567 1419 <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> 1568 1420 <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> … … 1571 1423 <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> 1572 1424 <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> 1573 <tr><td><a name="diff00 84" /></td></tr>1425 <tr><td><a name="diff0070" /></td></tr> 1574 1426 <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> 1575 1427 <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> … … 1577 1429 <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> 1578 1430 <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> 1579 <tr><td><a name="diff00 85" /></td></tr>1431 <tr><td><a name="diff0071" /></td></tr> 1580 1432 <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> 1581 1433 <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> 1582 1434 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1583 1435 <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> 1584 <tr><td><a name="diff00 86" /></td></tr>1436 <tr><td><a name="diff0072" /></td></tr> 1585 1437 <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> 1586 1438 <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>&l