![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 2652
- Timestamp:
- 07/05/14 12:48:29 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 13 edited
-
auth48/p1-messaging.unpg.txt (modified) (93 diffs)
-
auth48/p2-semantics.unpg.txt (modified) (112 diffs)
-
auth48/rfc7230.abdiff.txt (modified) (6 diffs)
-
auth48/rfc7230.diff.html (modified) (61 diffs)
-
auth48/rfc7231.abdiff.txt (modified) (10 diffs)
-
auth48/rfc7231.diff.html (modified) (92 diffs)
-
p1-messaging.html (modified) (8 diffs)
-
p1-messaging.xml (modified) (4 diffs)
-
p2-semantics.html (modified) (12 diffs)
-
p2-semantics.xml (modified) (9 diffs)
-
p5-range.html (modified) (5 diffs)
-
p6-cache.html (modified) (5 diffs)
-
p7-auth.html (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/auth48/p1-messaging.unpg.txt
r2651 r2652 6 6 Obsoletes: 2145, 2616 J. Reschke, Ed. 7 7 (if approved) greenbytes 8 Updates: 2817, 2818 (if approved) May 6, 20148 Updates: 2817, 2818 (if approved) May 7, 2014 9 9 Intended status: Standards Track 10 Expires: November 7, 201410 Expires: November 8, 2014 11 11 12 12 … … 53 53 54 54 55 Fielding & Reschke Expires November 7, 2014 [Page 1]55 Fielding & Reschke Expires November 8, 2014 [Page 1] 56 56 57 57 … … 62 62 material or to cite them other than as "work in progress." 63 63 64 This Internet-Draft will expire on November 7, 2014.64 This Internet-Draft will expire on November 8, 2014. 65 65 66 66 Copyright Notice … … 110 110 111 111 112 Fielding & Reschke Expires November 7, 2014 [Page 2]112 Fielding & Reschke Expires November 8, 2014 [Page 2] 113 113 114 114 … … 167 167 168 168 169 Fielding & Reschke Expires November 7, 2014 [Page 3]169 Fielding & Reschke Expires November 8, 2014 [Page 3] 170 170 171 171 … … 224 224 225 225 226 Fielding & Reschke Expires November 7, 2014 [Page 4]226 Fielding & Reschke Expires November 8, 2014 [Page 4] 227 227 228 228 … … 281 281 282 282 283 Fielding & Reschke Expires November 7, 2014 [Page 5]283 Fielding & Reschke Expires November 8, 2014 [Page 5] 284 284 285 285 … … 338 338 339 339 340 Fielding & Reschke Expires November 7, 2014 [Page 6]340 Fielding & Reschke Expires November 8, 2014 [Page 6] 341 341 342 342 … … 395 395 396 396 397 Fielding & Reschke Expires November 7, 2014 [Page 7]397 Fielding & Reschke Expires November 8, 2014 [Page 7] 398 398 399 399 … … 452 452 453 453 454 Fielding & Reschke Expires November 7, 2014 [Page 8]454 Fielding & Reschke Expires November 8, 2014 [Page 8] 455 455 456 456 … … 509 509 510 510 511 Fielding & Reschke Expires November 7, 2014 [Page 9]511 Fielding & Reschke Expires November 8, 2014 [Page 9] 512 512 513 513 … … 566 566 567 567 568 Fielding & Reschke Expires November 7, 2014 [Page 10]568 Fielding & Reschke Expires November 8, 2014 [Page 10] 569 569 570 570 … … 623 623 624 624 625 Fielding & Reschke Expires November 7, 2014 [Page 11]625 Fielding & Reschke Expires November 8, 2014 [Page 11] 626 626 627 627 … … 680 680 681 681 682 Fielding & Reschke Expires November 7, 2014 [Page 12]682 Fielding & Reschke Expires November 8, 2014 [Page 12] 683 683 684 684 … … 737 737 738 738 739 Fielding & Reschke Expires November 7, 2014 [Page 13]739 Fielding & Reschke Expires November 8, 2014 [Page 13] 740 740 741 741 … … 794 794 795 795 796 Fielding & Reschke Expires November 7, 2014 [Page 14]796 Fielding & Reschke Expires November 8, 2014 [Page 14] 797 797 798 798 … … 851 851 852 852 853 Fielding & Reschke Expires November 7, 2014 [Page 15]853 Fielding & Reschke Expires November 8, 2014 [Page 15] 854 854 855 855 … … 908 908 909 909 910 Fielding & Reschke Expires November 7, 2014 [Page 16]910 Fielding & Reschke Expires November 8, 2014 [Page 16] 911 911 912 912 … … 965 965 966 966 967 Fielding & Reschke Expires November 7, 2014 [Page 17]967 Fielding & Reschke Expires November 8, 2014 [Page 17] 968 968 969 969 … … 1022 1022 1023 1023 1024 Fielding & Reschke Expires November 7, 2014 [Page 18]1024 Fielding & Reschke Expires November 8, 2014 [Page 18] 1025 1025 1026 1026 … … 1079 1079 1080 1080 1081 Fielding & Reschke Expires November 7, 2014 [Page 19]1081 Fielding & Reschke Expires November 8, 2014 [Page 19] 1082 1082 1083 1083 … … 1136 1136 1137 1137 1138 Fielding & Reschke Expires November 7, 2014 [Page 20]1138 Fielding & Reschke Expires November 8, 2014 [Page 20] 1139 1139 1140 1140 … … 1193 1193 1194 1194 1195 Fielding & Reschke Expires November 7, 2014 [Page 21]1195 Fielding & Reschke Expires November 8, 2014 [Page 21] 1196 1196 1197 1197 … … 1250 1250 1251 1251 1252 Fielding & Reschke Expires November 7, 2014 [Page 22]1252 Fielding & Reschke Expires November 8, 2014 [Page 22] 1253 1253 1254 1254 … … 1307 1307 1308 1308 1309 Fielding & Reschke Expires November 7, 2014 [Page 23]1309 Fielding & Reschke Expires November 8, 2014 [Page 23] 1310 1310 1311 1311 … … 1364 1364 1365 1365 1366 Fielding & Reschke Expires November 7, 2014 [Page 24]1366 Fielding & Reschke Expires November 8, 2014 [Page 24] 1367 1367 1368 1368 … … 1421 1421 1422 1422 1423 Fielding & Reschke Expires November 7, 2014 [Page 25]1423 Fielding & Reschke Expires November 8, 2014 [Page 25] 1424 1424 1425 1425 … … 1478 1478 1479 1479 1480 Fielding & Reschke Expires November 7, 2014 [Page 26]1480 Fielding & Reschke Expires November 8, 2014 [Page 26] 1481 1481 1482 1482 … … 1535 1535 1536 1536 1537 Fielding & Reschke Expires November 7, 2014 [Page 27]1537 Fielding & Reschke Expires November 8, 2014 [Page 27] 1538 1538 1539 1539 … … 1592 1592 1593 1593 1594 Fielding & Reschke Expires November 7, 2014 [Page 28]1594 Fielding & Reschke Expires November 8, 2014 [Page 28] 1595 1595 1596 1596 … … 1649 1649 1650 1650 1651 Fielding & Reschke Expires November 7, 2014 [Page 29]1651 Fielding & Reschke Expires November 8, 2014 [Page 29] 1652 1652 1653 1653 … … 1706 1706 1707 1707 1708 Fielding & Reschke Expires November 7, 2014 [Page 30]1708 Fielding & Reschke Expires November 8, 2014 [Page 30] 1709 1709 1710 1710 … … 1763 1763 1764 1764 1765 Fielding & Reschke Expires November 7, 2014 [Page 31]1765 Fielding & Reschke Expires November 8, 2014 [Page 31] 1766 1766 1767 1767 … … 1820 1820 1821 1821 1822 Fielding & Reschke Expires November 7, 2014 [Page 32]1822 Fielding & Reschke Expires November 8, 2014 [Page 32] 1823 1823 1824 1824 … … 1877 1877 1878 1878 1879 Fielding & Reschke Expires November 7, 2014 [Page 33]1879 Fielding & Reschke Expires November 8, 2014 [Page 33] 1880 1880 1881 1881 … … 1934 1934 1935 1935 1936 Fielding & Reschke Expires November 7, 2014 [Page 34]1936 Fielding & Reschke Expires November 8, 2014 [Page 34] 1937 1937 1938 1938 … … 1991 1991 1992 1992 1993 Fielding & Reschke Expires November 7, 2014 [Page 35]1993 Fielding & Reschke Expires November 8, 2014 [Page 35] 1994 1994 1995 1995 … … 2048 2048 2049 2049 2050 Fielding & Reschke Expires November 7, 2014 [Page 36]2050 Fielding & Reschke Expires November 8, 2014 [Page 36] 2051 2051 2052 2052 … … 2105 2105 2106 2106 2107 Fielding & Reschke Expires November 7, 2014 [Page 37]2107 Fielding & Reschke Expires November 8, 2014 [Page 37] 2108 2108 2109 2109 … … 2162 2162 2163 2163 2164 Fielding & Reschke Expires November 7, 2014 [Page 38]2164 Fielding & Reschke Expires November 8, 2014 [Page 38] 2165 2165 2166 2166 … … 2219 2219 2220 2220 2221 Fielding & Reschke Expires November 7, 2014 [Page 39]2221 Fielding & Reschke Expires November 8, 2014 [Page 39] 2222 2222 2223 2223 … … 2276 2276 2277 2277 2278 Fielding & Reschke Expires November 7, 2014 [Page 40]2278 Fielding & Reschke Expires November 8, 2014 [Page 40] 2279 2279 2280 2280 … … 2333 2333 2334 2334 2335 Fielding & Reschke Expires November 7, 2014 [Page 41]2335 Fielding & Reschke Expires November 8, 2014 [Page 41] 2336 2336 2337 2337 … … 2390 2390 2391 2391 2392 Fielding & Reschke Expires November 7, 2014 [Page 42]2392 Fielding & Reschke Expires November 8, 2014 [Page 42] 2393 2393 2394 2394 … … 2447 2447 2448 2448 2449 Fielding & Reschke Expires November 7, 2014 [Page 43]2449 Fielding & Reschke Expires November 8, 2014 [Page 43] 2450 2450 2451 2451 … … 2504 2504 2505 2505 2506 Fielding & Reschke Expires November 7, 2014 [Page 44]2506 Fielding & Reschke Expires November 8, 2014 [Page 44] 2507 2507 2508 2508 … … 2561 2561 2562 2562 2563 Fielding & Reschke Expires November 7, 2014 [Page 45]2563 Fielding & Reschke Expires November 8, 2014 [Page 45] 2564 2564 2565 2565 … … 2618 2618 2619 2619 2620 Fielding & Reschke Expires November 7, 2014 [Page 46]2620 Fielding & Reschke Expires November 8, 2014 [Page 46] 2621 2621 2622 2622 … … 2675 2675 2676 2676 2677 Fielding & Reschke Expires November 7, 2014 [Page 47]2677 Fielding & Reschke Expires November 8, 2014 [Page 47] 2678 2678 2679 2679 … … 2732 2732 2733 2733 2734 Fielding & Reschke Expires November 7, 2014 [Page 48]2734 Fielding & Reschke Expires November 8, 2014 [Page 48] 2735 2735 2736 2736 … … 2789 2789 2790 2790 2791 Fielding & Reschke Expires November 7, 2014 [Page 49]2791 Fielding & Reschke Expires November 8, 2014 [Page 49] 2792 2792 2793 2793 … … 2846 2846 2847 2847 2848 Fielding & Reschke Expires November 7, 2014 [Page 50]2848 Fielding & Reschke Expires November 8, 2014 [Page 50] 2849 2849 2850 2850 … … 2903 2903 2904 2904 2905 Fielding & Reschke Expires November 7, 2014 [Page 51]2905 Fielding & Reschke Expires November 8, 2014 [Page 51] 2906 2906 2907 2907 … … 2960 2960 2961 2961 2962 Fielding & Reschke Expires November 7, 2014 [Page 52]2962 Fielding & Reschke Expires November 8, 2014 [Page 52] 2963 2963 2964 2964 … … 3017 3017 3018 3018 3019 Fielding & Reschke Expires November 7, 2014 [Page 53]3019 Fielding & Reschke Expires November 8, 2014 [Page 53] 3020 3020 3021 3021 … … 3074 3074 3075 3075 3076 Fielding & Reschke Expires November 7, 2014 [Page 54]3076 Fielding & Reschke Expires November 8, 2014 [Page 54] 3077 3077 3078 3078 … … 3094 3094 3095 3095 A server SHOULD sustain persistent connections, when possible, and 3096 allow the underlying transport's flow 3096 allow the underlying transport's flow-control mechanisms to resolve 3097 3097 temporary overloads, rather than terminate connections with the 3098 3098 expectation that clients will retry. The latter technique can … … 3131 3131 3132 3132 3133 Fielding & Reschke Expires November 7, 2014 [Page 55]3133 Fielding & Reschke Expires November 8, 2014 [Page 55] 3134 3134 3135 3135 … … 3146 3146 a significant risk that the client will not be able to read the last 3147 3147 HTTP response. If the server receives additional data from the 3148 client on a fully -closed connection, such as another request that was3148 client on a fully closed connection, such as another request that was 3149 3149 sent by the client before receiving the server's response, the 3150 3150 server's TCP stack will send a reset packet to the client; … … 3188 3188 3189 3189 3190 Fielding & Reschke Expires November 7, 2014 [Page 56]3190 Fielding & Reschke Expires November 8, 2014 [Page 56] 3191 3191 3192 3192 … … 3245 3245 3246 3246 3247 Fielding & Reschke Expires November 7, 2014 [Page 57]3247 Fielding & Reschke Expires November 8, 2014 [Page 57] 3248 3248 3249 3249 … … 3302 3302 3303 3303 3304 Fielding & Reschke Expires November 7, 2014 [Page 58]3304 Fielding & Reschke Expires November 8, 2014 [Page 58] 3305 3305 3306 3306 … … 3359 3359 3360 3360 3361 Fielding & Reschke Expires November 7, 2014 [Page 59]3361 Fielding & Reschke Expires November 8, 2014 [Page 59] 3362 3362 3363 3363 … … 3416 3416 3417 3417 3418 Fielding & Reschke Expires November 7, 2014 [Page 60]3418 Fielding & Reschke Expires November 8, 2014 [Page 60] 3419 3419 3420 3420 … … 3473 3473 3474 3474 3475 Fielding & Reschke Expires November 7, 2014 [Page 61]3475 Fielding & Reschke Expires November 8, 2014 [Page 61] 3476 3476 3477 3477 … … 3530 3530 3531 3531 3532 Fielding & Reschke Expires November 7, 2014 [Page 62]3532 Fielding & Reschke Expires November 8, 2014 [Page 62] 3533 3533 3534 3534 … … 3538 3538 Encoding considerations: HTTP messages enclosed by this type are in 3539 3539 "binary" format; use of an appropriate Content-Transfer-Encoding 3540 is required when transmitted via E-mail.3540 is required when transmitted via email. 3541 3541 3542 3542 Security considerations: see Section 9 … … 3587 3587 3588 3588 3589 Fielding & Reschke Expires November 7, 2014 [Page 63]3589 Fielding & Reschke Expires November 8, 2014 [Page 63] 3590 3590 3591 3591 … … 3644 3644 3645 3645 3646 Fielding & Reschke Expires November 7, 2014 [Page 64]3646 Fielding & Reschke Expires November 8, 2014 [Page 64] 3647 3647 3648 3648 … … 3701 3701 3702 3702 3703 Fielding & Reschke Expires November 7, 2014 [Page 65]3703 Fielding & Reschke Expires November 8, 2014 [Page 65] 3704 3704 3705 3705 … … 3758 3758 3759 3759 3760 Fielding & Reschke Expires November 7, 2014 [Page 66]3760 Fielding & Reschke Expires November 8, 2014 [Page 66] 3761 3761 3762 3762 … … 3815 3815 3816 3816 3817 Fielding & Reschke Expires November 7, 2014 [Page 67]3817 Fielding & Reschke Expires November 8, 2014 [Page 67] 3818 3818 3819 3819 … … 3872 3872 3873 3873 3874 Fielding & Reschke Expires November 7, 2014 [Page 68]3874 Fielding & Reschke Expires November 8, 2014 [Page 68] 3875 3875 3876 3876 … … 3929 3929 3930 3930 3931 Fielding & Reschke Expires November 7, 2014 [Page 69]3931 Fielding & Reschke Expires November 8, 2014 [Page 69] 3932 3932 3933 3933 … … 3986 3986 3987 3987 3988 Fielding & Reschke Expires November 7, 2014 [Page 70]3988 Fielding & Reschke Expires November 8, 2014 [Page 70] 3989 3989 3990 3990 … … 4043 4043 4044 4044 4045 Fielding & Reschke Expires November 7, 2014 [Page 71]4045 Fielding & Reschke Expires November 8, 2014 [Page 71] 4046 4046 4047 4047 … … 4100 4100 4101 4101 4102 Fielding & Reschke Expires November 7, 2014 [Page 72]4102 Fielding & Reschke Expires November 8, 2014 [Page 72] 4103 4103 4104 4104 … … 4157 4157 4158 4158 4159 Fielding & Reschke Expires November 7, 2014 [Page 73]4159 Fielding & Reschke Expires November 8, 2014 [Page 73] 4160 4160 4161 4161 … … 4214 4214 4215 4215 4216 Fielding & Reschke Expires November 7, 2014 [Page 74]4216 Fielding & Reschke Expires November 8, 2014 [Page 74] 4217 4217 4218 4218 … … 4271 4271 4272 4272 4273 Fielding & Reschke Expires November 7, 2014 [Page 75]4273 Fielding & Reschke Expires November 8, 2014 [Page 75] 4274 4274 4275 4275 … … 4297 4297 effects of hierarchical proxies, caching, the need for persistent 4298 4298 connections, or name-based virtual hosts. The proliferation of 4299 incompletely -implemented applications calling themselves "HTTP/1.0"4299 incompletely implemented applications calling themselves "HTTP/1.0" 4300 4300 further necessitated a protocol version change in order for two 4301 4301 communicating applications to determine each other's true … … 4328 4328 4329 4329 4330 Fielding & Reschke Expires November 7, 2014 [Page 76]4330 Fielding & Reschke Expires November 8, 2014 [Page 76] 4331 4331 4332 4332 … … 4385 4385 4386 4386 4387 Fielding & Reschke Expires November 7, 2014 [Page 77]4387 Fielding & Reschke Expires November 8, 2014 [Page 77] 4388 4388 4389 4389 … … 4442 4442 4443 4443 4444 Fielding & Reschke Expires November 7, 2014 [Page 78]4444 Fielding & Reschke Expires November 8, 2014 [Page 78] 4445 4445 4446 4446 … … 4499 4499 4500 4500 4501 Fielding & Reschke Expires November 7, 2014 [Page 79]4501 Fielding & Reschke Expires November 8, 2014 [Page 79] 4502 4502 4503 4503 … … 4556 4556 4557 4557 4558 Fielding & Reschke Expires November 7, 2014 [Page 80]4558 Fielding & Reschke Expires November 8, 2014 [Page 80] 4559 4559 4560 4560 … … 4613 4613 4614 4614 4615 Fielding & Reschke Expires November 7, 2014 [Page 81]4615 Fielding & Reschke Expires November 8, 2014 [Page 81] 4616 4616 4617 4617 … … 4670 4670 4671 4671 4672 Fielding & Reschke Expires November 7, 2014 [Page 82]4672 Fielding & Reschke Expires November 8, 2014 [Page 82] 4673 4673 4674 4674 … … 4727 4727 4728 4728 4729 Fielding & Reschke Expires November 7, 2014 [Page 83]4729 Fielding & Reschke Expires November 8, 2014 [Page 83] 4730 4730 4731 4731 … … 4784 4784 4785 4785 4786 Fielding & Reschke Expires November 7, 2014 [Page 84]4786 Fielding & Reschke Expires November 8, 2014 [Page 84] 4787 4787 4788 4788 … … 4841 4841 4842 4842 4843 Fielding & Reschke Expires November 7, 2014 [Page 85]4843 Fielding & Reschke Expires November 8, 2014 [Page 85] 4844 4844 4845 4845 … … 4898 4898 4899 4899 4900 Fielding & Reschke Expires November 7, 2014 [Page 86]4900 Fielding & Reschke Expires November 8, 2014 [Page 86] 4901 4901 4902 4902 … … 4955 4955 4956 4956 4957 Fielding & Reschke Expires November 7, 2014 [Page 87]4958 4959 4957 Fielding & Reschke Expires November 8, 2014 [Page 87] 4958 4959 -
draft-ietf-httpbis/latest/auth48/p2-semantics.unpg.txt
r2651 r2652 6 6 Obsoletes: 2616 (if approved) J. Reschke, Ed. 7 7 Updates: 2817 (if approved) greenbytes 8 Intended status: Standards Track May 6, 20149 Expires: November 7, 20148 Intended status: Standards Track May 7, 2014 9 Expires: November 8, 2014 10 10 11 11 … … 53 53 54 54 55 Fielding & Reschke Expires November 7, 2014 [Page 1]55 Fielding & Reschke Expires November 8, 2014 [Page 1] 56 56 57 57 … … 61 61 material or to cite them other than as "work in progress." 62 62 63 This Internet-Draft will expire on November 7, 2014.63 This Internet-Draft will expire on November 8, 2014. 64 64 65 65 Copyright Notice … … 110 110 111 111 112 Fielding & Reschke Expires November 7, 2014 [Page 2]112 Fielding & Reschke Expires November 8, 2014 [Page 2] 113 113 114 114 … … 167 167 168 168 169 Fielding & Reschke Expires November 7, 2014 [Page 3]169 Fielding & Reschke Expires November 8, 2014 [Page 3] 170 170 171 171 … … 224 224 225 225 226 Fielding & Reschke Expires November 7, 2014 [Page 4]226 Fielding & Reschke Expires November 8, 2014 [Page 4] 227 227 228 228 … … 281 281 282 282 283 Fielding & Reschke Expires November 7, 2014 [Page 5]283 Fielding & Reschke Expires November 8, 2014 [Page 5] 284 284 285 285 … … 338 338 339 339 340 Fielding & Reschke Expires November 7, 2014 [Page 6]340 Fielding & Reschke Expires November 8, 2014 [Page 6] 341 341 342 342 … … 395 395 396 396 397 Fielding & Reschke Expires November 7, 2014 [Page 7]397 Fielding & Reschke Expires November 8, 2014 [Page 7] 398 398 399 399 … … 452 452 453 453 454 Fielding & Reschke Expires November 7, 2014 [Page 8]454 Fielding & Reschke Expires November 8, 2014 [Page 8] 455 455 456 456 … … 509 509 510 510 511 Fielding & Reschke Expires November 7, 2014 [Page 9]511 Fielding & Reschke Expires November 8, 2014 [Page 9] 512 512 513 513 … … 566 566 567 567 568 Fielding & Reschke Expires November 7, 2014 [Page 10]568 Fielding & Reschke Expires November 8, 2014 [Page 10] 569 569 570 570 … … 623 623 624 624 625 Fielding & Reschke Expires November 7, 2014 [Page 11]625 Fielding & Reschke Expires November 8, 2014 [Page 11] 626 626 627 627 … … 680 680 681 681 682 Fielding & Reschke Expires November 7, 2014 [Page 12]682 Fielding & Reschke Expires November 8, 2014 [Page 12] 683 683 684 684 … … 737 737 738 738 739 Fielding & Reschke Expires November 7, 2014 [Page 13]739 Fielding & Reschke Expires November 8, 2014 [Page 13] 740 740 741 741 … … 794 794 795 795 796 Fielding & Reschke Expires November 7, 2014 [Page 14]796 Fielding & Reschke Expires November 8, 2014 [Page 14] 797 797 798 798 … … 851 851 852 852 853 Fielding & Reschke Expires November 7, 2014 [Page 15]853 Fielding & Reschke Expires November 8, 2014 [Page 15] 854 854 855 855 … … 908 908 909 909 910 Fielding & Reschke Expires November 7, 2014 [Page 16]910 Fielding & Reschke Expires November 8, 2014 [Page 16] 911 911 912 912 … … 965 965 966 966 967 Fielding & Reschke Expires November 7, 2014 [Page 17]967 Fielding & Reschke Expires November 8, 2014 [Page 17] 968 968 969 969 … … 1022 1022 1023 1023 1024 Fielding & Reschke Expires November 7, 2014 [Page 18]1024 Fielding & Reschke Expires November 8, 2014 [Page 18] 1025 1025 1026 1026 … … 1079 1079 1080 1080 1081 Fielding & Reschke Expires November 7, 2014 [Page 19]1081 Fielding & Reschke Expires November 8, 2014 [Page 19] 1082 1082 1083 1083 … … 1117 1117 1118 1118 Reactive negotiation is advantageous when the response would vary 1119 over commonly -used dimensions (such as type, language, or encoding),1119 over commonly used dimensions (such as type, language, or encoding), 1120 1120 when the origin server is unable to determine a user agent's 1121 1121 capabilities from examining the request, and generally when public … … 1136 1136 1137 1137 1138 Fielding & Reschke Expires November 7, 2014 [Page 20]1138 Fielding & Reschke Expires November 8, 2014 [Page 20] 1139 1139 1140 1140 … … 1193 1193 1194 1194 1195 Fielding & Reschke Expires November 7, 2014 [Page 21]1195 Fielding & Reschke Expires November 8, 2014 [Page 21] 1196 1196 1197 1197 … … 1250 1250 1251 1251 1252 Fielding & Reschke Expires November 7, 2014 [Page 22]1252 Fielding & Reschke Expires November 8, 2014 [Page 22] 1253 1253 1254 1254 … … 1258 1258 This definition of safe methods does not prevent an implementation 1259 1259 from including behavior that is potentially harmful, not entirely 1260 read-only, or which causes side -effects while invoking a safe method.1260 read-only, or which causes side effects while invoking a safe method. 1261 1261 What is important, however, is that the client did not request that 1262 1262 additional behavior and cannot be held accountable for it. For … … 1265 1265 that is considered safe even though the log storage might become full 1266 1266 and crash the server. Likewise, a safe request initiated by 1267 selecting an advertisement on the Web will often have the side -effect1267 selecting an advertisement on the Web will often have the side effect 1268 1268 of charging an advertising account. 1269 1269 … … 1290 1290 resource is to perform an unsafe action, then the resource owner MUST 1291 1291 disable or disallow that action when it is accessed using a safe 1292 request method. Failure to do so will result in unfortunate side -1292 request method. Failure to do so will result in unfortunate side 1293 1293 effects when automated processes perform a GET on every URI reference 1294 1294 for the sake of link maintenance, pre-fetching, building a search … … 1307 1307 1308 1308 1309 Fielding & Reschke Expires November 7, 2014 [Page 23]1309 Fielding & Reschke Expires November 8, 2014 [Page 23] 1310 1310 1311 1311 … … 1315 1315 what has been requested by the user; a server is free to log each 1316 1316 request separately, retain a revision control history, or implement 1317 other non-idempotent side -effects for each idempotent request.1317 other non-idempotent side effects for each idempotent request. 1318 1318 1319 1319 Idempotent methods are distinguished because the request can be … … 1364 1364 1365 1365 1366 Fielding & Reschke Expires November 7, 2014 [Page 24]1366 Fielding & Reschke Expires November 8, 2014 [Page 24] 1367 1367 1368 1368 … … 1421 1421 1422 1422 1423 Fielding & Reschke Expires November 7, 2014 [Page 25]1423 Fielding & Reschke Expires November 8, 2014 [Page 25] 1424 1424 1425 1425 … … 1478 1478 1479 1479 1480 Fielding & Reschke Expires November 7, 2014 [Page 26]1480 Fielding & Reschke Expires November 8, 2014 [Page 26] 1481 1481 1482 1482 … … 1535 1535 1536 1536 1537 Fielding & Reschke Expires November 7, 2014 [Page 27]1537 Fielding & Reschke Expires November 8, 2014 [Page 27] 1538 1538 1539 1539 … … 1580 1580 regarding whether or not to redirect the request. 1581 1581 1582 A PUT request applied to the target resource can have side -effects on1582 A PUT request applied to the target resource can have side effects on 1583 1583 other resources. For example, an article might have a URI for 1584 1584 identifying "the current version" (a resource) that is separate from … … 1592 1592 1593 1593 1594 Fielding & Reschke Expires November 7, 2014 [Page 28]1594 Fielding & Reschke Expires November 8, 2014 [Page 28] 1595 1595 1596 1596 … … 1649 1649 1650 1650 1651 Fielding & Reschke Expires November 7, 2014 [Page 29]1651 Fielding & Reschke Expires November 8, 2014 [Page 29] 1652 1652 1653 1653 … … 1706 1706 1707 1707 1708 Fielding & Reschke Expires November 7, 2014 [Page 30]1708 Fielding & Reschke Expires November 8, 2014 [Page 30] 1709 1709 1710 1710 … … 1763 1763 1764 1764 1765 Fielding & Reschke Expires November 7, 2014 [Page 31]1765 Fielding & Reschke Expires November 8, 2014 [Page 31] 1766 1766 1767 1767 … … 1820 1820 1821 1821 1822 Fielding & Reschke Expires November 7, 2014 [Page 32]1822 Fielding & Reschke Expires November 8, 2014 [Page 32] 1823 1823 1824 1824 … … 1877 1877 1878 1878 1879 Fielding & Reschke Expires November 7, 2014 [Page 33]1879 Fielding & Reschke Expires November 8, 2014 [Page 33] 1880 1880 1881 1881 … … 1934 1934 1935 1935 1936 Fielding & Reschke Expires November 7, 2014 [Page 34]1936 Fielding & Reschke Expires November 8, 2014 [Page 34] 1937 1937 1938 1938 … … 1991 1991 1992 1992 1993 Fielding & Reschke Expires November 7, 2014 [Page 35]1993 Fielding & Reschke Expires November 8, 2014 [Page 35] 1994 1994 1995 1995 … … 2048 2048 2049 2049 2050 Fielding & Reschke Expires November 7, 2014 [Page 36]2050 Fielding & Reschke Expires November 8, 2014 [Page 36] 2051 2051 2052 2052 … … 2105 2105 2106 2106 2107 Fielding & Reschke Expires November 7, 2014 [Page 37]2107 Fielding & Reschke Expires November 8, 2014 [Page 37] 2108 2108 2109 2109 … … 2162 2162 2163 2163 2164 Fielding & Reschke Expires November 7, 2014 [Page 38]2164 Fielding & Reschke Expires November 8, 2014 [Page 38] 2165 2165 2166 2166 … … 2219 2219 2220 2220 2221 Fielding & Reschke Expires November 7, 2014 [Page 39]2221 Fielding & Reschke Expires November 8, 2014 [Page 39] 2222 2222 2223 2223 … … 2276 2276 2277 2277 2278 Fielding & Reschke Expires November 7, 2014 [Page 40]2278 Fielding & Reschke Expires November 8, 2014 [Page 40] 2279 2279 2280 2280 … … 2333 2333 2334 2334 2335 Fielding & Reschke Expires November 7, 2014 [Page 41]2335 Fielding & Reschke Expires November 8, 2014 [Page 41] 2336 2336 2337 2337 … … 2390 2390 2391 2391 2392 Fielding & Reschke Expires November 7, 2014 [Page 42]2392 Fielding & Reschke Expires November 8, 2014 [Page 42] 2393 2393 2394 2394 … … 2447 2447 2448 2448 2449 Fielding & Reschke Expires November 7, 2014 [Page 43]2449 Fielding & Reschke Expires November 8, 2014 [Page 43] 2450 2450 2451 2451 … … 2504 2504 2505 2505 2506 Fielding & Reschke Expires November 7, 2014 [Page 44]2506 Fielding & Reschke Expires November 8, 2014 [Page 44] 2507 2507 2508 2508 … … 2554 2554 Some intermediaries have been known to indiscriminately remove 2555 2555 Referer header fields from outgoing requests. This has the 2556 unfortunate side -effect of interfering with protection against CSRF2556 unfortunate side effect of interfering with protection against CSRF 2557 2557 attacks, which can be far more harmful to their users. 2558 2558 Intermediaries and user agent extensions that wish to limit … … 2561 2561 2562 2562 2563 Fielding & Reschke Expires November 7, 2014 [Page 45]2563 Fielding & Reschke Expires November 8, 2014 [Page 45] 2564 2564 2565 2565 … … 2598 2598 A sender SHOULD limit generated product identifiers to what is 2599 2599 necessary to identify the product; a sender MUST NOT generate 2600 advertising or other non -essential information within the product2600 advertising or other nonessential information within the product 2601 2601 identifier. A sender SHOULD NOT generate information in product- 2602 2602 version that is not a version identifier (i.e., successive versions … … 2618 2618 2619 2619 2620 Fielding & Reschke Expires November 7, 2014 [Page 46]2620 Fielding & Reschke Expires November 8, 2014 [Page 46] 2621 2621 2622 2622 … … 2675 2675 2676 2676 2677 Fielding & Reschke Expires November 7, 2014 [Page 47]2677 Fielding & Reschke Expires November 8, 2014 [Page 47] 2678 2678 2679 2679 … … 2732 2732 2733 2733 2734 Fielding & Reschke Expires November 7, 2014 [Page 48]2734 Fielding & Reschke Expires November 8, 2014 [Page 48] 2735 2735 2736 2736 … … 2789 2789 2790 2790 2791 Fielding & Reschke Expires November 7, 2014 [Page 49]2791 Fielding & Reschke Expires November 8, 2014 [Page 49] 2792 2792 2793 2793 … … 2846 2846 2847 2847 2848 Fielding & Reschke Expires November 7, 2014 [Page 50]2848 Fielding & Reschke Expires November 8, 2014 [Page 50] 2849 2849 2850 2850 … … 2903 2903 2904 2904 2905 Fielding & Reschke Expires November 7, 2014 [Page 51]2905 Fielding & Reschke Expires November 8, 2014 [Page 51] 2906 2906 2907 2907 … … 2931 2931 operation. 2932 2932 2933 The 202 response is intentionally non -committal. Its purpose is to2933 The 202 response is intentionally noncommittal. Its purpose is to 2934 2934 allow a server to accept a request for some other process (perhaps a 2935 2935 batch-oriented process that is only run once per day) without … … 2960 2960 2961 2961 2962 Fielding & Reschke Expires November 7, 2014 [Page 52]2962 Fielding & Reschke Expires November 8, 2014 [Page 52] 2963 2963 2964 2964 … … 3017 3017 3018 3018 3019 Fielding & Reschke Expires November 7, 2014 [Page 53]3019 Fielding & Reschke Expires November 8, 2014 [Page 53] 3020 3020 3021 3021 … … 3074 3074 3075 3075 3076 Fielding & Reschke Expires November 7, 2014 [Page 54]3076 Fielding & Reschke Expires November 8, 2014 [Page 54] 3077 3077 3078 3078 … … 3131 3131 3132 3132 3133 Fielding & Reschke Expires November 7, 2014 [Page 55]3133 Fielding & Reschke Expires November 8, 2014 [Page 55] 3134 3134 3135 3135 … … 3188 3188 3189 3189 3190 Fielding & Reschke Expires November 7, 2014 [Page 56]3190 Fielding & Reschke Expires November 8, 2014 [Page 56] 3191 3191 3192 3192 … … 3245 3245 3246 3246 3247 Fielding & Reschke Expires November 7, 2014 [Page 57]3247 Fielding & Reschke Expires November 8, 2014 [Page 57] 3248 3248 3249 3249 … … 3302 3302 3303 3303 3304 Fielding & Reschke Expires November 7, 2014 [Page 58]3304 Fielding & Reschke Expires November 8, 2014 [Page 58] 3305 3305 3306 3306 … … 3359 3359 3360 3360 3361 Fielding & Reschke Expires November 7, 2014 [Page 59]3361 Fielding & Reschke Expires November 8, 2014 [Page 59] 3362 3362 3363 3363 … … 3416 3416 3417 3417 3418 Fielding & Reschke Expires November 7, 2014 [Page 60]3418 Fielding & Reschke Expires November 8, 2014 [Page 60] 3419 3419 3420 3420 … … 3473 3473 3474 3474 3475 Fielding & Reschke Expires November 7, 2014 [Page 61]3475 Fielding & Reschke Expires November 8, 2014 [Page 61] 3476 3476 3477 3477 … … 3530 3530 3531 3531 3532 Fielding & Reschke Expires November 7, 2014 [Page 62]3532 Fielding & Reschke Expires November 8, 2014 [Page 62] 3533 3533 3534 3534 … … 3587 3587 3588 3588 3589 Fielding & Reschke Expires November 7, 2014 [Page 63]3589 Fielding & Reschke Expires November 8, 2014 [Page 63] 3590 3590 3591 3591 … … 3644 3644 3645 3645 3646 Fielding & Reschke Expires November 7, 2014 [Page 64]3646 Fielding & Reschke Expires November 8, 2014 [Page 64] 3647 3647 3648 3648 … … 3701 3701 3702 3702 3703 Fielding & Reschke Expires November 7, 2014 [Page 65]3703 Fielding & Reschke Expires November 8, 2014 [Page 65] 3704 3704 3705 3705 … … 3758 3758 3759 3759 3760 Fielding & Reschke Expires November 7, 2014 [Page 66]3760 Fielding & Reschke Expires November 8, 2014 [Page 66] 3761 3761 3762 3762 … … 3815 3815 3816 3816 3817 Fielding & Reschke Expires November 7, 2014 [Page 67]3817 Fielding & Reschke Expires November 8, 2014 [Page 67] 3818 3818 3819 3819 … … 3872 3872 3873 3873 3874 Fielding & Reschke Expires November 7, 2014 [Page 68]3874 Fielding & Reschke Expires November 8, 2014 [Page 68] 3875 3875 3876 3876 … … 3929 3929 3930 3930 3931 Fielding & Reschke Expires November 7, 2014 [Page 69]3931 Fielding & Reschke Expires November 8, 2014 [Page 69] 3932 3932 3933 3933 … … 3986 3986 3987 3987 3988 Fielding & Reschke Expires November 7, 2014 [Page 70]3988 Fielding & Reschke Expires November 8, 2014 [Page 70] 3989 3989 3990 3990 … … 4043 4043 4044 4044 4045 Fielding & Reschke Expires November 7, 2014 [Page 71]4045 Fielding & Reschke Expires November 8, 2014 [Page 71] 4046 4046 4047 4047 … … 4100 4100 4101 4101 4102 Fielding & Reschke Expires November 7, 2014 [Page 72]4102 Fielding & Reschke Expires November 8, 2014 [Page 72] 4103 4103 4104 4104 … … 4157 4157 4158 4158 4159 Fielding & Reschke Expires November 7, 2014 [Page 73]4159 Fielding & Reschke Expires November 8, 2014 [Page 73] 4160 4160 4161 4161 … … 4214 4214 4215 4215 4216 Fielding & Reschke Expires November 7, 2014 [Page 74]4216 Fielding & Reschke Expires November 8, 2014 [Page 74] 4217 4217 4218 4218 … … 4271 4271 4272 4272 4273 Fielding & Reschke Expires November 7, 2014 [Page 75]4273 Fielding & Reschke Expires November 8, 2014 [Page 75] 4274 4274 4275 4275 … … 4328 4328 4329 4329 4330 Fielding & Reschke Expires November 7, 2014 [Page 76]4330 Fielding & Reschke Expires November 8, 2014 [Page 76] 4331 4331 4332 4332 … … 4385 4385 4386 4386 4387 Fielding & Reschke Expires November 7, 2014 [Page 77]4387 Fielding & Reschke Expires November 8, 2014 [Page 77] 4388 4388 4389 4389 … … 4442 4442 4443 4443 4444 Fielding & Reschke Expires November 7, 2014 [Page 78]4444 Fielding & Reschke Expires November 8, 2014 [Page 78] 4445 4445 4446 4446 … … 4499 4499 4500 4500 4501 Fielding & Reschke Expires November 7, 2014 [Page 79]4501 Fielding & Reschke Expires November 8, 2014 [Page 79] 4502 4502 4503 4503 … … 4556 4556 4557 4557 4558 Fielding & Reschke Expires November 7, 2014 [Page 80]4558 Fielding & Reschke Expires November 8, 2014 [Page 80] 4559 4559 4560 4560 … … 4613 4613 4614 4614 4615 Fielding & Reschke Expires November 7, 2014 [Page 81]4615 Fielding & Reschke Expires November 8, 2014 [Page 81] 4616 4616 4617 4617 … … 4670 4670 4671 4671 4672 Fielding & Reschke Expires November 7, 2014 [Page 82]4672 Fielding & Reschke Expires November 8, 2014 [Page 82] 4673 4673 4674 4674 … … 4727 4727 4728 4728 4729 Fielding & Reschke Expires November 7, 2014 [Page 83]4729 Fielding & Reschke Expires November 8, 2014 [Page 83] 4730 4730 4731 4731 … … 4784 4784 4785 4785 4786 Fielding & Reschke Expires November 7, 2014 [Page 84]4786 Fielding & Reschke Expires November 8, 2014 [Page 84] 4787 4787 4788 4788 … … 4841 4841 4842 4842 4843 Fielding & Reschke Expires November 7, 2014 [Page 85]4843 Fielding & Reschke Expires November 8, 2014 [Page 85] 4844 4844 4845 4845 … … 4898 4898 4899 4899 4900 Fielding & Reschke Expires November 7, 2014 [Page 86]4900 Fielding & Reschke Expires November 8, 2014 [Page 86] 4901 4901 4902 4902 … … 4955 4955 4956 4956 4957 Fielding & Reschke Expires November 7, 2014 [Page 87]4957 Fielding & Reschke Expires November 8, 2014 [Page 87] 4958 4958 4959 4959 … … 5012 5012 5013 5013 5014 Fielding & Reschke Expires November 7, 2014 [Page 88]5014 Fielding & Reschke Expires November 8, 2014 [Page 88] 5015 5015 5016 5016 … … 5069 5069 5070 5070 5071 Fielding & Reschke Expires November 7, 2014 [Page 89]5071 Fielding & Reschke Expires November 8, 2014 [Page 89] 5072 5072 5073 5073 … … 5126 5126 5127 5127 5128 Fielding & Reschke Expires November 7, 2014 [Page 90]5128 Fielding & Reschke Expires November 8, 2014 [Page 90] 5129 5129 5130 5130 … … 5183 5183 5184 5184 5185 Fielding & Reschke Expires November 7, 2014 [Page 91]5185 Fielding & Reschke Expires November 8, 2014 [Page 91] 5186 5186 5187 5187 … … 5240 5240 5241 5241 5242 Fielding & Reschke Expires November 7, 2014 [Page 92]5242 Fielding & Reschke Expires November 8, 2014 [Page 92] 5243 5243 5244 5244 … … 5297 5297 5298 5298 5299 Fielding & Reschke Expires November 7, 2014 [Page 93]5299 Fielding & Reschke Expires November 8, 2014 [Page 93] 5300 5300 5301 5301 … … 5354 5354 5355 5355 5356 Fielding & Reschke Expires November 7, 2014 [Page 94]5356 Fielding & Reschke Expires November 8, 2014 [Page 94] 5357 5357 5358 5358 … … 5411 5411 5412 5412 5413 Fielding & Reschke Expires November 7, 2014 [Page 95]5413 Fielding & Reschke Expires November 8, 2014 [Page 95] 5414 5414 5415 5415 … … 5468 5468 5469 5469 5470 Fielding & Reschke Expires November 7, 2014 [Page 96]5470 Fielding & Reschke Expires November 8, 2014 [Page 96] 5471 5471 5472 5472 … … 5525 5525 5526 5526 5527 Fielding & Reschke Expires November 7, 2014 [Page 97]5527 Fielding & Reschke Expires November 8, 2014 [Page 97] 5528 5528 5529 5529 … … 5582 5582 5583 5583 5584 Fielding & Reschke Expires November 7, 2014 [Page 98]5584 Fielding & Reschke Expires November 8, 2014 [Page 98] 5585 5585 5586 5586 … … 5639 5639 5640 5640 5641 Fielding & Reschke Expires November 7, 2014 [Page 99]5641 Fielding & Reschke Expires November 8, 2014 [Page 99] 5642 5642 5643 5643 … … 5696 5696 5697 5697 5698 Fielding & Reschke Expires November 7, 2014 [Page 100]5698 Fielding & Reschke Expires November 8, 2014 [Page 100] 5699 5699 5700 5700 … … 5753 5753 5754 5754 5755 Fielding & Reschke Expires November 7, 2014 [Page 101]5756 5757 5755 Fielding & Reschke Expires November 8, 2014 [Page 101] 5756 5757 -
draft-ietf-httpbis/latest/auth48/rfc7230.abdiff.txt
r2651 r2652 7 7 Obsoletes: 2145, 2616 J. Reschke, Ed. 8 8 (if approved) greenbytes 9 Updates: 2817, 2818 (if approved) May 6, 20149 Updates: 2817, 2818 (if approved) May 7, 2014 10 10 Intended status: Standards Track 11 Expires: November 7, 201411 Expires: November 8, 2014 12 12 13 13 NEW: … … 92 92 OLD: 93 93 94 This Internet-Draft will expire on November 7, 2014.94 This Internet-Draft will expire on November 8, 2014. 95 95 96 96 NEW: … … 866 866 867 867 868 Section 6.5., paragraph 4:869 OLD:870 871 A server SHOULD sustain persistent connections, when possible, and872 allow the underlying transport's flow control mechanisms to resolve873 temporary overloads, rather than terminate connections with the874 expectation that clients will retry. The latter technique can875 exacerbate network congestion.876 877 NEW:878 879 A server SHOULD sustain persistent connections, when possible, and880 allow the underlying transport's flow-control mechanisms to resolve881 temporary overloads, rather than terminate connections with the882 expectation that clients will retry. The latter technique can883 exacerbate network congestion.884 885 886 868 Section 6.5., paragraph 6: 887 869 OLD: … … 962 944 requests had been sent on the connection, the client SHOULD NOT 963 945 assume that they will be processed by the server. 964 965 966 Section 6.5., paragraph 12:967 OLD:968 969 If a server performs an immediate close of a TCP connection, there is970 a significant risk that the client will not be able to read the last971 HTTP response. If the server receives additional data from the972 client on a fully-closed connection, such as another request that was973 sent by the client before receiving the server's response, the974 server's TCP stack will send a reset packet to the client;975 unfortunately, the reset packet might erase the client's976 unacknowledged input buffers before they can be read and interpreted977 by the client's HTTP parser.978 979 NEW:980 981 If a server performs an immediate close of a TCP connection, there is982 a significant risk that the client will not be able to read the last983 HTTP response. If the server receives additional data from the984 client on a fully closed connection, such as another request that was985 sent by the client before receiving the server's response, the986 server's TCP stack will send a reset packet to the client;987 unfortunately, the reset packet might erase the client's988 unacknowledged input buffers before they can be read and interpreted989 by the client's HTTP parser.990 946 991 947 … … 1108 1064 Person and email address to contact for further information: 1109 1065 See Authors' Addresses Section. 1110 1111 1112 Section 8.3.2., paragraph 8:1113 OLD:1114 1115 Encoding considerations: HTTP messages enclosed by this type are in1116 "binary" format; use of an appropriate Content-Transfer-Encoding1117 is required when transmitted via E-mail.1118 1119 NEW:1120 1121 Encoding considerations: HTTP messages enclosed by this type are in1122 "binary" format; use of an appropriate Content-Transfer-Encoding1123 is required when transmitted via email.1124 1066 1125 1067 … … 1393 1335 [RFC793] Postel, J., "Transmission Control Protocol", STD 7, 1394 1336 RFC 793, September 1981. 1395 1396 1397 Appendix A., paragraph 1:1398 OLD:1399 1400 HTTP has been in use since 1990. The first version, later referred1401 to as HTTP/0.9, was a simple protocol for hypertext data transfer1402 across the Internet, using only a single request method (GET) and no1403 metadata. HTTP/1.0, as defined by [RFC1945], added a range of1404 request methods and MIME-like messaging, allowing for metadata to be1405 transferred and modifiers placed on the request/response semantics.1406 However, HTTP/1.0 did not sufficiently take into consideration the1407 effects of hierarchical proxies, caching, the need for persistent1408 connections, or name-based virtual hosts. The proliferation of1409 incompletely-implemented applications calling themselves "HTTP/1.0"1410 further necessitated a protocol version change in order for two1411 communicating applications to determine each other's true1412 capabilities.1413 1414 NEW:1415 1416 HTTP has been in use since 1990. The first version, later referred1417 to as HTTP/0.9, was a simple protocol for hypertext data transfer1418 across the Internet, using only a single request method (GET) and no1419 metadata. HTTP/1.0, as defined by [RFC1945], added a range of1420 request methods and MIME-like messaging, allowing for metadata to be1421 transferred and modifiers placed on the request/response semantics.1422 However, HTTP/1.0 did not sufficiently take into consideration the1423 effects of hierarchical proxies, caching, the need for persistent1424 connections, or name-based virtual hosts. The proliferation of1425 incompletely implemented applications calling themselves "HTTP/1.0"1426 further necessitated a protocol version change in order for two1427 communicating applications to determine each other's true1428 capabilities.1429 1337 1430 1338 -
draft-ietf-httpbis/latest/auth48/rfc7230.diff.html
r2651 r2652 44 44 <tr><td><a name="diff0002" /></td></tr> 45 45 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">(if approved) greenbytes</span></td><td> </td><td class="rblock">Updates: 2817, 2818 <span class="insert">greenbytes</span></td><td class="lineno" valign="top"></td></tr> 46 <tr><td class="lineno" valign="top"></td><td class="lblock">Updates: 2817, 2818 <span class="delete">(if approved) May 6, 2014</span></td><td> </td><td class="rblock"><span class="insert">Category:</span> Standards Track <span class="insert">May</span> 2014</td><td class="lineno" valign="top"></td></tr>46 <tr><td class="lineno" valign="top"></td><td class="lblock">Updates: 2817, 2818 <span class="delete">(if approved) May 7, 2014</span></td><td> </td><td class="rblock"><span class="insert">Category:</span> Standards Track <span class="insert">May</span> 2014</td><td class="lineno" valign="top"></td></tr> 47 47 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Intended status:</span> Standards Track</td><td> </td><td class="rblock"><span class="insert">ISSN: 2070-1721</span></td><td class="lineno" valign="top"></td></tr> 48 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Expires: November 7,</span> 2014</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>48 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Expires: November 8,</span> 2014</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> 49 49 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 50 50 <tr><td class="lineno" valign="top"></td><td class="left"> Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</td><td> </td><td class="right"> Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</td><td class="lineno" valign="top"></td></tr> … … 96 96 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 97 97 <tr><td><a name="diff0007" /></td></tr> 98 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">This Internet-Draft will expire</span> on <span class="delete">November 7, 2014.</span></td><td> </td><td class="rblock"> <span class="insert">Information about the current status of this document, any errata,</span></td><td class="lineno" valign="top"></td></tr>98 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">This Internet-Draft will expire</span> on <span class="delete">November 8, 2014.</span></td><td> </td><td class="rblock"> <span class="insert">Information about the current status of this document, any errata,</span></td><td class="lineno" valign="top"></td></tr> 99 99 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> and how to provide feedback</span> on <span class="insert">it may be obtained at</span></td><td class="lineno" valign="top"></td></tr> 100 100 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> http://www.rfc-editor.org/info/rfc7230.</span></td><td class="lineno" valign="top"></td></tr> … … 759 759 <tr><td class="lineno" valign="top"></td><td class="left"> reuse the same connection for a subsequent request.</td><td> </td><td class="right"> reuse the same connection for a subsequent request.</td><td class="lineno" valign="top"></td></tr> 760 760 <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-l24" /><small>skipping to change at</small><em> page 55, line 19</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 55, line 19</em></th><td></td></tr> 762 <tr><td class="lineno" valign="top"></td><td class="left"> enables allocated system resources to be reclaimed.</td><td> </td><td class="right"> enables allocated system resources to be reclaimed.</td><td class="lineno" valign="top"></td></tr> 763 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 764 <tr><td class="lineno" valign="top"></td><td class="left"> A client, server, or proxy MAY close the transport connection at any</td><td> </td><td class="right"> A client, server, or proxy MAY close the transport connection at any</td><td class="lineno" valign="top"></td></tr> 765 <tr><td class="lineno" valign="top"></td><td class="left"> time. For example, a client might have started to send a new request</td><td> </td><td class="right"> time. For example, a client might have started to send a new request</td><td class="lineno" valign="top"></td></tr> 766 <tr><td class="lineno" valign="top"></td><td class="left"> at the same time that the server has decided to close the "idle"</td><td> </td><td class="right"> at the same time that the server has decided to close the "idle"</td><td class="lineno" valign="top"></td></tr> 767 <tr><td class="lineno" valign="top"></td><td class="left"> connection. From the server's point of view, the connection is being</td><td> </td><td class="right"> connection. From the server's point of view, the connection is being</td><td class="lineno" valign="top"></td></tr> 768 <tr><td class="lineno" valign="top"></td><td class="left"> closed while it was idle, but from the client's point of view, a</td><td> </td><td class="right"> closed while it was idle, but from the client's point of view, a</td><td class="lineno" valign="top"></td></tr> 769 <tr><td class="lineno" valign="top"></td><td class="left"> request is in progress.</td><td> </td><td class="right"> request is in progress.</td><td class="lineno" valign="top"></td></tr> 770 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 771 <tr><td class="lineno" valign="top"></td><td class="left"> A server SHOULD sustain persistent connections, when possible, and</td><td> </td><td class="right"> A server SHOULD sustain persistent connections, when possible, and</td><td class="lineno" valign="top"></td></tr> 772 <tr><td><a name="diff0042" /></td></tr> 773 <tr><td class="lineno" valign="top"></td><td class="lblock"> allow the underlying transport's flow<span class="delete"> </span>control mechanisms to resolve</td><td> </td><td class="rblock"> allow the underlying transport's flow<span class="insert">-</span>control mechanisms to resolve</td><td class="lineno" valign="top"></td></tr> 774 <tr><td class="lineno" valign="top"></td><td class="left"> temporary overloads, rather than terminate connections with the</td><td> </td><td class="right"> temporary overloads, rather than terminate connections with the</td><td class="lineno" valign="top"></td></tr> 761 <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 55, line 31</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 55, line 31</em></th><td></td></tr> 775 762 <tr><td class="lineno" valign="top"></td><td class="left"> expectation that clients will retry. The latter technique can</td><td> </td><td class="right"> expectation that clients will retry. The latter technique can</td><td class="lineno" valign="top"></td></tr> 776 763 <tr><td class="lineno" valign="top"></td><td class="left"> exacerbate network congestion.</td><td> </td><td class="right"> exacerbate network congestion.</td><td class="lineno" valign="top"></td></tr> … … 783 770 <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> 784 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> 785 <tr><td><a name="diff004 3" /></td></tr>772 <tr><td><a name="diff0042" /></td></tr> 786 773 <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> 787 774 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 790 777 <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> 791 778 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 792 <tr><td><a name="diff004 4" /></td></tr>779 <tr><td><a name="diff0043" /></td></tr> 793 780 <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> 794 781 <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> … … 796 783 <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> 797 784 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 798 <tr><td><a name="diff004 5" /></td></tr>785 <tr><td><a name="diff0044" /></td></tr> 799 786 <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> 800 787 <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> … … 804 791 <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> 805 792 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 806 <tr><td><a name="diff004 6" /></td></tr>793 <tr><td><a name="diff0045" /></td></tr> 807 794 <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> 808 795 <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> … … 810 797 <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> 811 798 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 812 <tr><td><a name="diff004 7" /></td></tr>799 <tr><td><a name="diff0046" /></td></tr> 813 800 <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> 814 801 <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> … … 820 807 <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> 821 808 <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> 822 <tr><td><a name="diff0048" /></td></tr> 823 <tr><td class="lineno" valign="top"></td><td class="lblock"> client on a fully<span class="delete">-</span>closed connection, such as another request that was</td><td> </td><td class="rblock"> client on a fully<span class="insert"> </span>closed connection, such as another request that was</td><td class="lineno" valign="top"></td></tr> 809 <tr><td class="lineno" valign="top"></td><td class="left"> client on a fully closed connection, such as another request that was</td><td> </td><td class="right"> client on a fully closed connection, such as another request that was</td><td class="lineno" valign="top"></td></tr> 824 810 <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> 825 <tr><td class="lineno" valign="top"></td><td class="left"> server's TCP stack will send a reset packet to the client;</td><td> </td><td class="right"> server's TCP stack will send a reset packet to the client;</td><td class="lineno" valign="top"></td></tr>826 <tr><td class="lineno" valign="top"></td><td class="left"> unfortunately, the reset packet might erase the client's</td><td> </td><td class="right"> unfortunately, the reset packet might erase the client's</td><td class="lineno" valign="top"></td></tr>827 <tr><td class="lineno" valign="top"></td><td class="left"> unacknowledged input buffers before they can be read and interpreted</td><td> </td><td class="right"> unacknowledged input buffers before they can be read and interpreted</td><td class="lineno" valign="top"></td></tr>828 <tr><td class="lineno" valign="top"></td><td class="left"> by the client's HTTP parser.</td><td> </td><td class="right"> by the client's HTTP parser.</td><td class="lineno" valign="top"></td></tr>829 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>830 <tr><td class="lineno" valign="top"></td><td class="left"> To avoid the TCP reset problem, servers typically close a connection</td><td> </td><td class="right"> To avoid the TCP reset problem, servers typically close a connection</td><td class="lineno" valign="top"></td></tr>831 <tr><td class="lineno" valign="top"></td><td class="left"> in stages. First, the server performs a half-close by closing only</td><td> </td><td class="right"> in stages. First, the server performs a half-close by closing only</td><td class="lineno" valign="top"></td></tr>832 <tr><td class="lineno" valign="top"></td><td class="left"> the write side of the read/write connection. The server then</td><td> </td><td class="right"> the write side of the read/write connection. The server then</td><td class="lineno" valign="top"></td></tr>833 <tr><td class="lineno" valign="top"></td><td class="left"> continues to read from the connection until it receives a</td><td> </td><td class="right"> continues to read from the connection until it receives a</td><td class="lineno" valign="top"></td></tr>834 811 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 835 812 <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 57, line 31</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 57, line 31</em></th><td></td></tr> … … 844 821 <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> 845 822 <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> 846 <tr><td><a name="diff004 9" /></td></tr>823 <tr><td><a name="diff0047" /></td></tr> 847 824 <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> 848 825 <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> … … 873 850 <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> 874 851 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 875 <tr><td><a name="diff00 50" /></td></tr>852 <tr><td><a name="diff0048" /></td></tr> 876 853 <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> 877 854 <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> … … 895 872 <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> 896 873 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 897 <tr><td><a name="diff00 51" /></td></tr>874 <tr><td><a name="diff0049" /></td></tr> 898 875 <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> 899 876 <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> 900 877 <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> 901 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> 902 <tr><td><a name="diff005 2" /></td></tr>879 <tr><td><a name="diff0050" /></td></tr> 903 880 <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> 904 881 <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> … … 918 895 <tr><td class="lineno" valign="top"></td><td class="left"> +-------------------+----------+----------+---------------+</td><td> </td><td class="right"> +-------------------+----------+----------+---------------+</td><td class="lineno" valign="top"></td></tr> 919 896 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 920 <tr><td><a name="diff005 3" /></td></tr>897 <tr><td><a name="diff0051" /></td></tr> 921 898 <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> 922 899 <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> … … 938 915 <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> 939 916 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 940 <tr><td><a name="diff005 4" /></td></tr>917 <tr><td><a name="diff0052" /></td></tr> 941 918 <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> 942 919 <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> … … 956 933 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 957 934 <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> 958 <tr><td><a name="diff005 5" /></td></tr>935 <tr><td><a name="diff0053" /></td></tr> 959 936 <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> 960 937 <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> … … 980 957 <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> 981 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> 982 <tr><td><a name="diff005 6" /></td></tr>959 <tr><td><a name="diff0054" /></td></tr> 983 960 <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> 984 961 <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> … … 994 971 <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> 995 972 <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-l28" /><small>skipping to change at</small><em> page 63, line 7</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 63, line 7</em></th><td></td></tr> 997 <tr><td class="lineno" valign="top"></td><td class="left"> version: The HTTP-version number of the enclosed messages (e.g.,</td><td> </td><td class="right"> version: The HTTP-version number of the enclosed messages (e.g.,</td><td class="lineno" valign="top"></td></tr> 998 <tr><td class="lineno" valign="top"></td><td class="left"> "1.1"). If not present, the version can be determined from the</td><td> </td><td class="right"> "1.1"). If not present, the version can be determined from the</td><td class="lineno" valign="top"></td></tr> 999 <tr><td class="lineno" valign="top"></td><td class="left"> first line of the body.</td><td> </td><td class="right"> first line of the body.</td><td class="lineno" valign="top"></td></tr> 1000 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1001 <tr><td class="lineno" valign="top"></td><td class="left"> msgtype: The message type -- "request" or "response". If not</td><td> </td><td class="right"> msgtype: The message type -- "request" or "response". If not</td><td class="lineno" valign="top"></td></tr> 1002 <tr><td class="lineno" valign="top"></td><td class="left"> present, the type can be determined from the first line of the</td><td> </td><td class="right"> present, the type can be determined from the first line of the</td><td class="lineno" valign="top"></td></tr> 1003 <tr><td class="lineno" valign="top"></td><td class="left"> body.</td><td> </td><td class="right"> body.</td><td class="lineno" valign="top"></td></tr> 1004 <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 <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> 1006 <tr><td class="lineno" valign="top"></td><td class="left"> "binary" format; use of an appropriate Content-Transfer-Encoding</td><td> </td><td class="right"> "binary" format; use of an appropriate Content-Transfer-Encoding</td><td class="lineno" valign="top"></td></tr> 1007 <tr><td><a name="diff0057" /></td></tr> 1008 <tr><td class="lineno" valign="top"></td><td class="lblock"> is required when transmitted via <span class="delete">E-</span>mail.</td><td> </td><td class="rblock"> is required when transmitted via <span class="insert">e</span>mail.</td><td class="lineno" valign="top"></td></tr> 1009 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1010 <tr><td class="lineno" valign="top"></td><td class="left"> Security considerations: see Section 9</td><td> </td><td class="right"> Security considerations: see Section 9</td><td class="lineno" valign="top"></td></tr> 1011 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1012 <tr><td class="lineno" valign="top"></td><td class="left"> Interoperability considerations: N/A</td><td> </td><td class="right"> Interoperability considerations: N/A</td><td class="lineno" valign="top"></td></tr> 1013 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1014 <tr><td class="lineno" valign="top"></td><td class="left"> Published specification: This specification (see Section 8.3.2).</td><td> </td><td class="right"> Published specification: This specification (see Section 8.3.2).</td><td class="lineno" valign="top"></td></tr> 1015 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1016 <tr><td class="lineno" valign="top"></td><td class="left"> Applications that use this media type: N/A</td><td> </td><td class="right"> Applications that use this media type: N/A</td><td class="lineno" valign="top"></td></tr> 1017 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1018 <tr><td class="lineno" valign="top"></td><td class="left"> Fragment identifier considerations: N/A</td><td> </td><td class="right"> Fragment identifier considerations: N/A</td><td class="lineno" valign="top"></td></tr> 1019 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1020 <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 63, line 29</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 63, line 29</em></th><td></td></tr> 973 <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 63, line 29</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 63, line 29</em></th><td></td></tr> 1021 974 <tr><td class="lineno" valign="top"></td><td class="left"> Additional information:</td><td> </td><td class="right"> Additional information:</td><td class="lineno" valign="top"></td></tr> 1022 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> … … 1029 982 <tr><td class="lineno" valign="top"></td><td class="left"> Macintosh file type code(s): N/A</td><td> </td><td class="right"> Macintosh file type code(s): N/A</td><td class="lineno" valign="top"></td></tr> 1030 983 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1031 <tr><td><a name="diff005 8" /></td></tr>984 <tr><td><a name="diff0055" /></td></tr> 1032 985 <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> 1033 986 <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> … … 1043 996 <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> 1044 997 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1045 <tr><td><a name="diff005 9" /></td></tr>998 <tr><td><a name="diff0056" /></td></tr> 1046 999 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Transfer <span class="delete">Coding Registry</span> defines the namespace for transfer</td><td> </td><td class="rblock"> The <span class="insert">"HTTP</span> Transfer <span class="insert">Coding" registry</span> defines the namespace for</td><td class="lineno" valign="top"></td></tr> 1047 1000 <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> … … 1057 1010 <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> 1058 1011 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1059 <tr bgcolor="gray" ><td></td><th><a name="part-l 30" /><small>skipping to change at</small><em> page 64, line 22</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 64, line 22</em></th><td></td></tr>1012 <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 64, line 22</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 64, line 22</em></th><td></td></tr> 1060 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> 1061 1014 <tr><td class="lineno" valign="top"></td><td class="left"> Values to be added to this namespace require IETF Review (see Section</td><td> </td><td class="right"> Values to be added to this namespace require IETF Review (see Section</td><td class="lineno" valign="top"></td></tr> … … 1068 1021 <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> 1069 1022 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1070 <tr><td><a name="diff00 60" /></td></tr>1023 <tr><td><a name="diff0057" /></td></tr> 1071 1024 <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> 1072 1025 <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> … … 1087 1040 <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> 1088 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> 1089 <tr><td><a name="diff00 61" /></td></tr>1042 <tr><td><a name="diff0058" /></td></tr> 1090 1043 <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> 1091 1044 <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> 1092 1045 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1093 <tr><td><a name="diff00 62" /></td></tr>1046 <tr><td><a name="diff0059" /></td></tr> 1094 1047 <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> 1095 1048 <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> … … 1109 1062 <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> 1110 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> 1111 <tr><td><a name="diff006 3" /></td></tr>1064 <tr><td><a name="diff0060" /></td></tr> 1112 1065 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Upgrade Token <span class="delete">Registry</span> defines the namespace for <span class="delete">protocol-</span></td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Upgrade Token <span class="insert">Registry"</span></td><td class="lineno" valign="top"></td></tr> 1113 1066 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> name</span> tokens used to identify protocols in the Upgrade header field.</td><td> </td><td class="rblock"> defines the namespace for <span class="insert">protocol-name</span> tokens used to identify</td><td class="lineno" valign="top"></td></tr> … … 1124 1077 <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> 1125 1078 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1126 <tr bgcolor="gray" ><td></td><th><a name="part-l3 1" /><small>skipping to change at</small><em> page 66, line 10</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 66, line 10</em></th><td></td></tr>1079 <tr bgcolor="gray" ><td></td><th><a name="part-l30" /><small>skipping to change at</small><em> page 66, line 10</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 66, line 10</em></th><td></td></tr> 1127 1080 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1128 1081 <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> … … 1135 1088 <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> 1136 1089 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1137 <tr><td><a name="diff006 4" /></td></tr>1090 <tr><td><a name="diff0061" /></td></tr> 1138 1091 <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> 1139 1092 <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> … … 1149 1102 <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> 1150 1103 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1151 <tr bgcolor="gray" ><td></td><th><a name="part-l3 2" /><small>skipping to change at</small><em> page 67, line 13</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 67, line 13</em></th><td></td></tr>1104 <tr bgcolor="gray" ><td></td><th><a name="part-l31" /><small>skipping to change at</small><em> page 67, line 13</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 67, line 13</em></th><td></td></tr> 1152 1105 <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> 1153 1106 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1160 1113 <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> 1161 1114 <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> 1162 <tr><td><a name="diff006 5" /></td></tr>1115 <tr><td><a name="diff0062" /></td></tr> 1163 1116 <tr><td class="lineno" valign="top"></td><td class="lblock"> mappings; DNS Security Extensions (DNSSEC<span class="delete">, [RFC4033]) are</span> one way to</td><td> </td><td class="rblock"> mappings; DNS Security Extensions (DNSSEC<span class="insert">) ([RFC4033]) is</span> one way to</td><td class="lineno" valign="top"></td></tr> 1164 1117 <tr><td class="lineno" valign="top"></td><td class="left"> improve authenticity.</td><td> </td><td class="right"> improve authenticity.</td><td class="lineno" valign="top"></td></tr> … … 1178 1131 <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> 1179 1132 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1180 <tr><td><a name="diff006 6" /></td></tr>1133 <tr><td><a name="diff0063" /></td></tr> 1181 1134 <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> 1182 1135 <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> … … 1192 1145 <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> 1193 1146 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1194 <tr bgcolor="gray" ><td></td><th><a name="part-l3 3" /><small>skipping to change at</small><em> page 70, line 9</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 70, line 9</em></th><td></td></tr>1147 <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 70, line 9</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 70, line 9</em></th><td></td></tr> 1195 1148 <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> 1196 1149 <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> … … 1203 1156 <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> 1204 1157 <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> 1205 <tr><td><a name="diff006 7" /></td></tr>1158 <tr><td><a name="diff0064" /></td></tr> 1206 1159 <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> 1207 1160 <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> … … 1216 1169 <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> 1217 1170 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1218 <tr bgcolor="gray" ><td></td><th><a name="part-l3 4" /><small>skipping to change at</small><em> page 72, line 50</em></th><th> </th><th><a name="part-r34" /><small>skipping to change at</small><em> page 72, line 50</em></th><td></td></tr>1171 <tr bgcolor="gray" ><td></td><th><a name="part-l33" /><small>skipping to change at</small><em> page 72, line 50</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 72, line 50</em></th><td></td></tr> 1219 1172 <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> 1220 1173 <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> … … 1227 1180 <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> 1228 1181 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1229 <tr><td><a name="diff006 8" /></td></tr>1182 <tr><td><a name="diff0065" /></td></tr> 1230 1183 <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> 1231 1184 <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> … … 1242 1195 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1243 1196 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1244 <tr bgcolor="gray" ><td></td><th><a name="part-l3 5" /><small>skipping to change at</small><em> page 73, line 28</em></th><th> </th><th><a name="part-r35" /><small>skipping to change at</small><em> page 73, line 25</em></th><td></td></tr>1197 <tr bgcolor="gray" ><td></td><th><a name="part-l34" /><small>skipping to change at</small><em> page 73, line 28</em></th><th> </th><th><a name="part-r34" /><small>skipping to change at</small><em> page 73, line 25</em></th><td></td></tr> 1245 1198 <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> 1246 1199 <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> … … 1253 1206 <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> 1254 1207 <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> 1255 <tr><td><a name="diff006 9" /></td></tr>1208 <tr><td><a name="diff0066" /></td></tr> 1256 1209 <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> 1257 1210 <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> … … 1259 1212 <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> 1260 1213 <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> 1261 <tr><td><a name="diff00 70" /></td></tr>1214 <tr><td><a name="diff0067" /></td></tr> 1262 1215 <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> 1263 1216 <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> … … 1265 1218 <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> 1266 1219 <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> 1267 <tr><td><a name="diff00 71" /></td></tr>1220 <tr><td><a name="diff0068" /></td></tr> 1268 1221 <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> 1269 1222 <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> … … 1271 1224 <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> 1272 1225 <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> 1273 <tr><td><a name="diff00 72" /></td></tr>1226 <tr><td><a name="diff0069" /></td></tr> 1274 1227 <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> 1275 1228 <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> … … 1277 1230 <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> 1278 1231 <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> 1279 <tr><td><a name="diff007 3" /></td></tr>1232 <tr><td><a name="diff0070" /></td></tr> 1280 1233 <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> 1281 1234 <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> … … 1293 1246 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1294 1247 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1295 <tr bgcolor="gray" ><td></td><th><a name="part-l36" /><small>skipping to change at</small><em> page 76, line 25</em></th><th> </th><th><a name="part-r36" /><small>skipping to change at</small><em> page 76, line 22</em></th><td></td></tr> 1296 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1297 <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> 1298 <tr><td class="lineno" valign="top"></td><td class="left"> to as HTTP/0.9, was a simple protocol for hypertext data transfer</td><td> </td><td class="right"> to as HTTP/0.9, was a simple protocol for hypertext data transfer</td><td class="lineno" valign="top"></td></tr> 1299 <tr><td class="lineno" valign="top"></td><td class="left"> across the Internet, using only a single request method (GET) and no</td><td> </td><td class="right"> across the Internet, using only a single request method (GET) and no</td><td class="lineno" valign="top"></td></tr> 1300 <tr><td class="lineno" valign="top"></td><td class="left"> metadata. HTTP/1.0, as defined by [RFC1945], added a range of</td><td> </td><td class="right"> metadata. HTTP/1.0, as defined by [RFC1945], added a range of</td><td class="lineno" valign="top"></td></tr> 1301 <tr><td class="lineno" valign="top"></td><td class="left"> request methods and MIME-like messaging, allowing for metadata to be</td><td> </td><td class="right"> request methods and MIME-like messaging, allowing for metadata to be</td><td class="lineno" valign="top"></td></tr> 1302 <tr><td class="lineno" valign="top"></td><td class="left"> transferred and modifiers placed on the request/response semantics.</td><td> </td><td class="right"> transferred and modifiers placed on the request/response semantics.</td><td class="lineno" valign="top"></td></tr> 1303 <tr><td class="lineno" valign="top"></td><td class="left"> However, HTTP/1.0 did not sufficiently take into consideration the</td><td> </td><td class="right"> However, HTTP/1.0 did not sufficiently take into consideration the</td><td class="lineno" valign="top"></td></tr> 1304 <tr><td class="lineno" valign="top"></td><td class="left"> effects of hierarchical proxies, caching, the need for persistent</td><td> </td><td class="right"> effects of hierarchical proxies, caching, the need for persistent</td><td class="lineno" valign="top"></td></tr> 1305 <tr><td class="lineno" valign="top"></td><td class="left"> connections, or name-based virtual hosts. The proliferation of</td><td> </td><td class="right"> connections, or name-based virtual hosts. The proliferation of</td><td class="lineno" valign="top"></td></tr> 1306 <tr><td><a name="diff0074" /></td></tr> 1307 <tr><td class="lineno" valign="top"></td><td class="lblock"> incompletely<span class="delete">-</span>implemented applications calling themselves "HTTP/1.0"</td><td> </td><td class="rblock"> incompletely<span class="insert"> </span>implemented applications calling themselves "HTTP/1.0"</td><td class="lineno" valign="top"></td></tr> 1308 <tr><td class="lineno" valign="top"></td><td class="left"> further necessitated a protocol version change in order for two</td><td> </td><td class="right"> further necessitated a protocol version change in order for two</td><td class="lineno" valign="top"></td></tr> 1309 <tr><td class="lineno" valign="top"></td><td class="left"> communicating applications to determine each other's true</td><td> </td><td class="right"> communicating applications to determine each other's true</td><td class="lineno" valign="top"></td></tr> 1310 <tr><td class="lineno" valign="top"></td><td class="left"> capabilities.</td><td> </td><td class="right"> capabilities.</td><td class="lineno" valign="top"></td></tr> 1311 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1312 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent</td><td> </td><td class="right"> HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent</td><td class="lineno" valign="top"></td></tr> 1313 <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> 1314 <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> 1315 <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> 1316 <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> 1317 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1318 <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-l37" /><small>skipping to change at</small><em> page 77, line 10</em></th><th> </th><th><a name="part-r37" /><small>skipping to change at</small><em> page 77, line 5</em></th><td></td></tr> 1248 <tr bgcolor="gray" ><td></td><th><a name="part-l35" /><small>skipping to change at</small><em> page 77, line 10</em></th><th> </th><th><a name="part-r35" /><small>skipping to change at</small><em> page 77, line 5</em></th><td></td></tr> 1320 1249 <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> 1321 1250 <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> … … 1328 1257 <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> 1329 1258 <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="diff007 5" /></td></tr>1259 <tr><td><a name="diff0071" /></td></tr> 1331 1260 <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> 1332 1261 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1341 1270 <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> 1342 1271 <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 8" /><small>skipping to change at</small><em> page 78, line 20</em></th><th> </th><th><a name="part-r38" /><small>skipping to change at</small><em> page 78, line 14</em></th><td></td></tr>1272 <tr bgcolor="gray" ><td></td><th><a name="part-l36" /><small>skipping to change at</small><em> page 78, line 20</em></th><th> </th><th><a name="part-r36" /><small>skipping to change at</small><em> page 78, line 14</em></th><td></td></tr> 1344 1273 <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> 1345 1274 <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 1281 <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> 1353 1282 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1354 <tr><td><a name="diff007 6" /></td></tr>1283 <tr><td><a name="diff0072" /></td></tr> 1355 1284 <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> 1356 1285 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1357 <tr><td><a name="diff007 7" /></td></tr>1286 <tr><td><a name="diff0073" /></td></tr> 1358 1287 <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> 1359 1288 <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> 1360 1289 <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> 1361 <tr><td><a name="diff007 8" /></td></tr>1290 <tr><td><a name="diff0074" /></td></tr> 1362 1291 <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> 1363 1292 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1364 1293 <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> 1365 1294 <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> 1366 <tr><td><a name="diff007 9" /></td></tr>1295 <tr><td><a name="diff0075" /></td></tr> 1367 1296 <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> 1368 1297 <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 1298 <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> 1370 <tr><td><a name="diff00 80" /></td></tr>1299 <tr><td><a name="diff0076" /></td></tr> 1371 1300 <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> 1372 1301 <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> … … 1376 1305 <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> 1377 1306 <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> 1378 <tr><td><a name="diff00 81" /></td></tr>1307 <tr><td><a name="diff0077" /></td></tr> 1379 1308 <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> 1380 1309 <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 1310 <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> 1382 1311 <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> 1383 <tr><td><a name="diff00 82" /></td></tr>1312 <tr><td><a name="diff0078" /></td></tr> 1384 1313 <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> 1385 1314 <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> … … 1387 1316 <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> 1388 1317 <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> 1389 <tr><td><a name="diff00 83" /></td></tr>1318 <tr><td><a name="diff0079" /></td></tr> 1390 1319 <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> 1391 1320 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1392 1321 <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> 1393 <tr><td><a name="diff008 4" /></td></tr>1322 <tr><td><a name="diff0080" /></td></tr> 1394 1323 <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> 1395 1324 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"> </td><td class="lineno" valign="top"></td></tr> … … 1397 1326 <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> 1398 1327 <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> 1399 <tr><td><a name="diff008 5" /></td></tr>1328 <tr><td><a name="diff0081" /></td></tr> 1400 1329 <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> 1401 1330 <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> … … 1403 1332 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1404 1333 <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> 1405 <tr><td><a name="diff008 6" /></td></tr>1334 <tr><td><a name="diff0082" /></td></tr> 1406 1335 <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> 1407 1336 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1411 1340 <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> 1412 1341 <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> 1413 <tr><td><a name="diff008 7" /></td></tr>1342 <tr><td><a name="diff0083" /></td></tr> 1414 1343 <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> 1415 1344 <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> 1416 1345 <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><a name="diff008 8" /></td></tr>1346 <tr><td><a name="diff0084" /></td></tr> 1418 1347 <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> 1419 1348 <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> 1420 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> 1421 1350 <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> 1422 <tr><td><a name="diff008 9" /></td></tr>1351 <tr><td><a name="diff0085" /></td></tr> 1423 1352 <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> 1424 1353 <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> 1425 1354 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1426 <tr><td><a name="diff00 90" /></td></tr>1355 <tr><td><a name="diff0086" /></td></tr> 1427 1356 <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> 1428 1357 <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> … … 1430 1359 <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> 1431 1360 <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> 1432 <tr><td><a name="diff00 91" /></td></tr>1361 <tr><td><a name="diff0087" /></td></tr> 1433 1362 <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> 1434 1363 <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> 1435 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> 1436 <tr><td><a name="diff00 92" /></td></tr>1365 <tr><td><a name="diff0088" /></td></tr> 1437 1366 <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> 1438 1367 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1439 <tr><td><a name="diff00 93" /></td></tr>1368 <tr><td><a name="diff0089" /></td></tr> 1440 1369 <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> 1441 1370 <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> … … 1444 1373 <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> 1445 1374 <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> 1446 <tr><td><a name="diff009 4" /></td></tr>1375 <tr><td><a name="diff0090" /></td></tr> 1447 1376 <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> 1448 1377 <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 1381 <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> 1453 1382 <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> 1454 <tr><td><a name="diff009 5" /></td></tr>1383 <tr><td><a name="diff0091" /></td></tr> 1455 1384 <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> 1456 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> 1457 1386 <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> 1458 1387 <tr><td class="lineno" valign="top"></td><td class="left"> other than 101 (this was incorporated from [RFC2817]). Furthermore,</td><td> </td><td class="right"> other than 101 (this was incorporated from [RFC2817]). Furthermore,</td><td class="lineno" valign="top"></td></tr> 1459 <tr><td><a name="diff009 6" /></td></tr>1388 <tr><td><a name="diff0092" /></td></tr> 1460 1389 <tr><td class="lineno" valign="top"></td><td class="lblock"> the ordering in the field value is now significant<span class="delete">. (Section 6.7)</span></td><td> </td><td class="rblock"> the ordering in the field value is now significant<span class="insert"> (Section 6.7).</span></td><td class="lineno" valign="top"></td></tr> 1461 1390 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1462 1391 <tr><td class="lineno" valign="top"></td><td class="left"> Empty list elements in list productions (e.g., a list header field</td><td> </td><td class="right"> Empty list elements in list productions (e.g., a list header field</td><td class="lineno" valign="top"></td></tr> 1463 <tr><td><a name="diff009 7" /></td></tr>1392 <tr><td><a name="diff0093" /></td></tr> 1464 1393 <tr><td class="lineno" valign="top"></td><td class="lblock"> containing ", ,") have been deprecated<span class="delete">. (Section 7)</span></td><td> </td><td class="rblock"> containing ", ,") have been deprecated<span class="insert"> (Section 7).</span></td><td class="lineno" valign="top"></td></tr> 1465 1394 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1466 1395 <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> 1467 <tr><td><a name="diff009 8" /></td></tr>1396 <tr><td><a name="diff0094" /></td></tr> 1468 1397 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section 8.4)</td><td> </td><td class="rblock"> (Section 8.4)<span class="insert">.</span></td><td class="lineno" valign="top"></td></tr> 1469 1398 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1470 <tr><td><a name="diff009 9" /></td></tr>1399 <tr><td><a name="diff0095" /></td></tr> 1471 1400 <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> 1472 1401 <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> 1473 1402 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1474 <tr><td><a name="diff0 100" /></td></tr>1403 <tr><td><a name="diff0096" /></td></tr> 1475 1404 <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> 1476 1405 <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> … … 1478 1407 <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> 1479 1408 <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> 1480 <tr><td><a name="diff0 101" /></td></tr>1409 <tr><td><a name="diff0097" /></td></tr> 1481 1410 <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> 1482 1411 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1491 1420 <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> 1492 1421 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1493 <tr bgcolor="gray" ><td></td><th><a name="part-l3 9" /><small>skipping to change at</small><em> page 83, line 25</em></th><th> </th><th><a name="part-r39" /><small>skipping to change at</small><em> page 83, line 20</em></th><td></td></tr>1422 <tr bgcolor="gray" ><td></td><th><a name="part-l37" /><small>skipping to change at</small><em> page 83, line 25</em></th><th> </th><th><a name="part-r37" /><small>skipping to change at</small><em> page 83, line 20</em></th><td></td></tr> 1494 1423 <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> 1495 1424 <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> … … 1502 1431 <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> 1503 1432 <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> 1504 <tr><td><a name="diff0 102" /></td></tr>1433 <tr><td><a name="diff0098" /></td></tr> 1505 1434 <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> 1506 1435 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1515 1444 <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> 1516 1445 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1517 <tr bgcolor="gray" ><td></td><th><a name="part-l 40" /><small>skipping to change at</small><em> page 84, line 20</em></th><th> </th><th><a name="part-r40" /><small>skipping to change at</small><em> page 84, line 14</em></th><td></td></tr>1446 <tr bgcolor="gray" ><td></td><th><a name="part-l38" /><small>skipping to change at</small><em> page 84, line 20</em></th><th> </th><th><a name="part-r38" /><small>skipping to change at</small><em> page 84, line 14</em></th><td></td></tr> 1518 1447 <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> 1519 1448 <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> … … 1526 1455 <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> 1527 1456 <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> 1528 <tr><td><a name="diff0 103" /></td></tr>1457 <tr><td><a name="diff0099" /></td></tr> 1529 1458 <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> 1530 1459 <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> 1531 <tr><td><a name="diff010 4" /></td></tr>1460 <tr><td><a name="diff0100" /></td></tr> 1532 1461 <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> 1533 1462 <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> … … 1542 1471 <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> 1543 1472 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1544 <tr bgcolor="gray" ><td></td><th><a name="part-l 41" /><small>skipping to change at</small><em> page 85, line 34</em></th><th> </th><th><a name="part-r41" /><small>skipping to change at</small><em> page 85, line 28</em></th><td></td></tr>1473 <tr bgcolor="gray" ><td></td><th><a name="part-l39" /><small>skipping to change at</small><em> page 85, line 34</em></th><th> </th><th><a name="part-r39" /><small>skipping to change at</small><em> page 85, line 28</em></th><td></td></tr> 1545 1474 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1546 1475 <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> … … 1553 1482 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1554 1483 <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> 1555 <tr><td><a name="diff010 5" /></td></tr>1484 <tr><td><a name="diff0101" /></td></tr> 1556 1485 <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> 1557 1486 <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> … … 1572 1501 <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> 1573 1502 <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> 1574 <tr><td><a name="diff010 6" /></td></tr>1503 <tr><td><a name="diff0102" /></td></tr> 1575 1504 <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> 1576 1505 <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 1514 <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> 1586 1515 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1587 <tr bgcolor="gray" ><td></td><th><a name="part-l4 2" /><small>skipping to change at</small><em> page 86, line 35</em></th><th> </th><th><a name="part-r42" /><small>skipping to change at</small><em> page 86, line 30</em></th><td></td></tr>1516 <tr bgcolor="gray" ><td></td><th><a name="part-l40" /><small>skipping to change at</small><em> page 86, line 35</em></th><th> </th><th><a name="part-r40" /><small>skipping to change at</small><em> page 86, line 30</em></th><td></td></tr> 1588 1517 <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> 1589 1518 <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> … … 1596 1525 <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> 1597 1526 <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> 1598 <tr><td><a name="diff010 7" /></td></tr>1527 <tr><td><a name="diff0103" /></td></tr> 1599 1528 <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> 1600 1529 <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> … … 1610 1539 1611 1540 <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr> 1612 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 10 7change blocks. </a></th></tr>1613 <tr class="stats"><td></td><th><i>1 80 lines changed or deleted</i></th><th><i> </i></th><th><i>157lines changed or added</i></th><td></td></tr>1541 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 103 change blocks. </a></th></tr> 1542 <tr class="stats"><td></td><th><i>176 lines changed or deleted</i></th><th><i> </i></th><th><i>153 lines changed or added</i></th><td></td></tr> 1614 1543 <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> 1615 1544 </table> -
draft-ietf-httpbis/latest/auth48/rfc7231.abdiff.txt
r2651 r2652 7 7 Obsoletes: 2616 (if approved) J. Reschke, Ed. 8 8 Updates: 2817 (if approved) greenbytes 9 Intended status: Standards Track May 6, 201410 Expires: November 7, 20149 Intended status: Standards Track May 7, 2014 10 Expires: November 8, 2014 11 11 12 12 NEW: … … 91 91 OLD: 92 92 93 This Internet-Draft will expire on November 7, 2014.93 This Internet-Draft will expire on November 8, 2014. 94 94 95 95 NEW: … … 545 545 546 546 547 Section 406, paragraph 1:548 OLD:549 550 Reactive negotiation is advantageous when the response would vary551 over commonly-used dimensions (such as type, language, or encoding),552 when the origin server is unable to determine a user agent's553 capabilities from examining the request, and generally when public554 caches are used to distribute server load and reduce network usage.555 556 NEW:557 558 Reactive negotiation is advantageous when the response would vary559 over commonly used dimensions (such as type, language, or encoding),560 when the origin server is unable to determine a user agent's561 capabilities from examining the request, and generally when public562 caches are used to distribute server load and reduce network usage.563 564 565 547 Section 4.1., paragraph 4: 566 548 OLD: … … 626 608 This definition of safe methods does not prevent an implementation 627 609 from including behavior that is potentially harmful, not entirely 628 read-only, or which causes side -effects while invoking a safe method.610 read-only, or which causes side effects while invoking a safe method. 629 611 What is important, however, is that the client did not request that 630 612 additional behavior and cannot be held accountable for it. For … … 633 615 that is considered safe even though the log storage might become full 634 616 and crash the server. Likewise, a safe request initiated by 635 selecting an advertisement on the Web will often have the side -effect617 selecting an advertisement on the Web will often have the side effect 636 618 of charging an advertising account. 637 619 … … 651 633 652 634 653 Section 4.2.1., paragraph 6:654 OLD:655 656 When a resource is constructed such that parameters within the657 effective request URI have the effect of selecting an action, it is658 the resource owner's responsibility to ensure that the action is659 consistent with the request method semantics. For example, it is660 common for Web-based content editing software to use actions within661 query parameters, such as "page?do=delete". If the purpose of such a662 resource is to perform an unsafe action, then the resource owner MUST663 disable or disallow that action when it is accessed using a safe664 request method. Failure to do so will result in unfortunate side-665 effects when automated processes perform a GET on every URI reference666 for the sake of link maintenance, pre-fetching, building a search667 index, etc.668 669 NEW:670 671 When a resource is constructed such that parameters within the672 effective request URI have the effect of selecting an action, it is673 the resource owner's responsibility to ensure that the action is674 consistent with the request method semantics. For example, it is675 common for Web-based content editing software to use actions within676 query parameters, such as "page?do=delete". If the purpose of such a677 resource is to perform an unsafe action, then the resource owner MUST678 disable or disallow that action when it is accessed using a safe679 request method. Failure to do so will result in unfortunate side680 effects when automated processes perform a GET on every URI reference681 for the sake of link maintenance, pre-fetching, building a search682 index, etc.683 684 685 Section 4.2.2., paragraph 2:686 OLD:687 688 Like the definition of safe, the idempotent property only applies to689 what has been requested by the user; a server is free to log each690 request separately, retain a revision control history, or implement691 other non-idempotent side-effects for each idempotent request.692 693 NEW:694 695 Like the definition of safe, the idempotent property only applies to696 what has been requested by the user; a server is free to log each697 request separately, retain a revision control history, or implement698 other non-idempotent side effects for each idempotent request.699 700 701 635 Section 4.3.3., paragraph 6: 702 636 OLD: … … 716 650 being 206 (Partial Content), 304 (Not Modified), and 416 (Range Not 717 651 Satisfiable)). 718 719 720 Section 4.3.4., paragraph 13:721 OLD:722 723 A PUT request applied to the target resource can have side-effects on724 other resources. For example, an article might have a URI for725 identifying "the current version" (a resource) that is separate from726 the URIs identifying each particular version (different resources727 that at one point shared the same state as the current version728 resource). A successful PUT request on "the current version" URI729 might therefore create a new version resource in addition to changing730 the state of the target resource, and might also cause links to be731 added between the related resources.732 733 NEW:734 735 A PUT request applied to the target resource can have side effects on736 other resources. For example, an article might have a URI for737 identifying "the current version" (a resource) that is separate from738 the URIs identifying each particular version (different resources739 that at one point shared the same state as the current version740 resource). A successful PUT request on "the current version" URI741 might therefore create a new version resource in addition to changing742 the state of the target resource, and might also cause links to be743 added between the related resources.744 652 745 653 … … 863 771 864 772 865 Section 5.5.2., paragraph 8:866 OLD:867 868 Some intermediaries have been known to indiscriminately remove869 Referer header fields from outgoing requests. This has the870 unfortunate side-effect of interfering with protection against CSRF871 attacks, which can be far more harmful to their users.872 Intermediaries and user agent extensions that wish to limit873 information disclosure in Referer ought to restrict their changes to874 specific edits, such as replacing internal domain names with875 pseudonyms or truncating the query and/or path components. An876 intermediary SHOULD NOT modify or delete the Referer header field877 when the field value shares the same scheme and host as the request878 target.879 880 NEW:881 882 Some intermediaries have been known to indiscriminately remove883 Referer header fields from outgoing requests. This has the884 unfortunate side effect of interfering with protection against CSRF885 attacks, which can be far more harmful to their users.886 Intermediaries and user agent extensions that wish to limit887 information disclosure in Referer ought to restrict their changes to888 specific edits, such as replacing internal domain names with889 pseudonyms or truncating the query and/or path components. An890 intermediary SHOULD NOT modify or delete the Referer header field891 when the field value shares the same scheme and host as the request892 target.893 894 895 773 Section 5.5.3., paragraph 1: 896 774 OLD: … … 937 815 938 816 939 Section 5.5.3., paragraph 5:940 OLD:941 942 A sender SHOULD limit generated product identifiers to what is943 necessary to identify the product; a sender MUST NOT generate944 advertising or other non-essential information within the product945 identifier. A sender SHOULD NOT generate information in product-946 version that is not a version identifier (i.e., successive versions947 of the same product name ought only to differ in the product-version948 portion of the product identifier).949 950 NEW:951 952 A sender SHOULD limit generated product identifiers to what is953 necessary to identify the product; a sender MUST NOT generate954 advertising or other nonessential information within the product955 identifier. A sender SHOULD NOT generate information in product-956 version that is not a version identifier (i.e., successive versions957 of the same product name ought only to differ in the product-version958 portion of the product identifier).959 960 961 817 Section 5.5.3., paragraph 9: 962 818 OLD: … … 1017 873 explicit cache controls [RFC7234]; all other status codes are not 1018 874 cacheable by default. 1019 1020 1021 Section 6.3.3., paragraph 2:1022 OLD:1023 1024 The 202 response is intentionally non-committal. Its purpose is to1025 allow a server to accept a request for some other process (perhaps a1026 batch-oriented process that is only run once per day) without1027 requiring that the user agent's connection to the server persist1028 until the process is completed. The representation sent with this1029 response ought to describe the request's current status and point to1030 (or embed) a status monitor that can provide the user with an1031 estimate of when the request will be fulfilled.1032 1033 NEW:1034 1035 The 202 response is intentionally noncommittal. Its purpose is to1036 allow a server to accept a request for some other process (perhaps a1037 batch-oriented process that is only run once per day) without1038 requiring that the user agent's connection to the server persist1039 until the process is completed. The representation sent with this1040 response ought to describe the request's current status and point to1041 (or embed) a status monitor that can provide the user with an1042 estimate of when the request will be fulfilled.1043 875 1044 876 -
draft-ietf-httpbis/latest/auth48/rfc7231.diff.html
r2651 r2652 43 43 <tr><td class="lineno" valign="top"></td><td class="lblock">Obsoletes: 2616 <span class="delete">(if approved)</span> J. Reschke, Ed.</td><td> </td><td class="rblock">Obsoletes: 2616 J. Reschke, Ed.</td><td class="lineno" valign="top"></td></tr> 44 44 <tr><td class="lineno" valign="top"></td><td class="lblock">Updates: 2817 <span class="delete">(if approved)</span> greenbytes</td><td> </td><td class="rblock">Updates: 2817 greenbytes</td><td class="lineno" valign="top"></td></tr> 45 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Intended status:</span> Standards Track May <span class="delete"> 6, 2014</span></td><td> </td><td class="rblock"><span class="insert">Category:</span> Standards Track May 2014</td><td class="lineno" valign="top"></td></tr>46 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Expires: November 7,</span> 2014</td><td> </td><td class="rblock"><span class="insert">ISSN: 2070-1721</span></td><td class="lineno" valign="top"></td></tr>45 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Intended status:</span> Standards Track May <span class="delete">7, 2014</span></td><td> </td><td class="rblock"><span class="insert">Category:</span> Standards Track May 2014</td><td class="lineno" valign="top"></td></tr> 46 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Expires: November 8,</span> 2014</td><td> </td><td class="rblock"><span class="insert">ISSN: 2070-1721</span></td><td class="lineno" valign="top"></td></tr> 47 47 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 48 48 <tr><td class="lineno" valign="top"></td><td class="left"> Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td><td> </td><td class="right"> Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td><td class="lineno" valign="top"></td></tr> … … 94 94 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 95 95 <tr><td><a name="diff0006" /></td></tr> 96 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">This Internet-Draft will expire</span> on <span class="delete">November 7, 2014.</span></td><td> </td><td class="rblock"> <span class="insert">Information about the current status of this document, any errata,</span></td><td class="lineno" valign="top"></td></tr>96 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">This Internet-Draft will expire</span> on <span class="delete">November 8, 2014.</span></td><td> </td><td class="rblock"> <span class="insert">Information about the current status of this document, any errata,</span></td><td class="lineno" valign="top"></td></tr> 97 97 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> and how to provide feedback</span> on <span class="insert">it may be obtained at</span></td><td class="lineno" valign="top"></td></tr> 98 98 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> http://www.rfc-editor.org/info/rfc7231.</span></td><td class="lineno" valign="top"></td></tr> … … 330 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> 331 331 <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-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> 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> 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> 335 <tr><td class="lineno" valign="top"></td><td class="left"> than the list of alternatives, and thereby indicate that reactive</td><td> </td><td class="right"> than the list of alternatives, and thereby indicate that reactive</td><td class="lineno" valign="top"></td></tr> 336 <tr><td class="lineno" valign="top"></td><td class="left"> negotiation by the user agent is preferred. For example, the</td><td> </td><td class="right"> negotiation by the user agent is preferred. For example, the</td><td class="lineno" valign="top"></td></tr> 337 <tr><td class="lineno" valign="top"></td><td class="left"> alternatives listed in responses with the 300 (Multiple Choices) and</td><td> </td><td class="right"> alternatives listed in responses with the 300 (Multiple Choices) and</td><td class="lineno" valign="top"></td></tr> 338 <tr><td class="lineno" valign="top"></td><td class="left"> 406 (Not Acceptable) status codes include information about the</td><td> </td><td class="right"> 406 (Not Acceptable) status codes include information about the</td><td class="lineno" valign="top"></td></tr> 339 <tr><td class="lineno" valign="top"></td><td class="left"> available representations so that the user or user agent can react by</td><td> </td><td class="right"> available representations so that the user or user agent can react by</td><td class="lineno" valign="top"></td></tr> 340 <tr><td class="lineno" valign="top"></td><td class="left"> making a selection.</td><td> </td><td class="right"> making a selection.</td><td class="lineno" valign="top"></td></tr> 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> 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> 343 <tr><td><a name="diff0017" /></td></tr> 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> 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> 346 <tr><td class="lineno" valign="top"></td><td class="left"> capabilities from examining the request, and generally when public</td><td> </td><td class="right"> capabilities from examining the request, and generally when public</td><td class="lineno" valign="top"></td></tr> 347 <tr><td class="lineno" valign="top"></td><td class="left"> caches are used to distribute server load and reduce network usage.</td><td> </td><td class="right"> caches are used to distribute server load and reduce network usage.</td><td class="lineno" valign="top"></td></tr> 348 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 349 <tr><td class="lineno" valign="top"></td><td class="left"> Reactive negotiation suffers from the disadvantages of transmitting a</td><td> </td><td class="right"> Reactive negotiation suffers from the disadvantages of transmitting a</td><td class="lineno" valign="top"></td></tr> 350 <tr><td class="lineno" valign="top"></td><td class="left"> list of alternatives to the user agent, which degrades user-perceived</td><td> </td><td class="right"> list of alternatives to the user agent, which degrades user-perceived</td><td class="lineno" valign="top"></td></tr> 351 <tr><td class="lineno" valign="top"></td><td class="left"> latency if transmitted in the header section, and needing a second</td><td> </td><td class="right"> latency if transmitted in the header section, and needing a second</td><td class="lineno" valign="top"></td></tr> 352 <tr><td class="lineno" valign="top"></td><td class="left"> request to obtain an alternate representation. Furthermore, this</td><td> </td><td class="right"> request to obtain an alternate representation. Furthermore, this</td><td class="lineno" valign="top"></td></tr> 353 <tr><td class="lineno" valign="top"></td><td class="left"> specification does not define a mechanism for supporting automatic</td><td> </td><td class="right"> specification does not define a mechanism for supporting automatic</td><td class="lineno" valign="top"></td></tr> 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> 355 <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-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> 332 <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 21, line 26</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 21, line 26</em></th><td></td></tr> 357 333 <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> 358 334 <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> … … 365 341 <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> 366 342 <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> 367 <tr><td><a name="diff001 8" /></td></tr>343 <tr><td><a name="diff0017" /></td></tr> 368 344 <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> 369 345 <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> … … 371 347 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 372 348 <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> 373 <tr><td><a name="diff001 9" /></td></tr>349 <tr><td><a name="diff0018" /></td></tr> 374 350 <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> 375 351 <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> … … 384 360 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 385 361 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 386 <tr bgcolor="gray" ><td></td><th><a name="part-l1 1" /><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>362 <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 22, line 31</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 22, line 31</em></th><td></td></tr> 387 363 <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> 388 364 <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> … … 395 371 <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> 396 372 <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> 397 <tr><td><a name="diff00 20" /></td></tr>373 <tr><td><a name="diff0019" /></td></tr> 398 374 <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> 399 375 <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> … … 409 385 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 410 386 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 411 <tr bgcolor="gray" ><td></td><th><a name="part-l1 2" /><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>387 <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 23, line 5</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 23, line 5</em></th><td></td></tr> 412 388 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 413 389 <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> … … 420 396 <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> 421 397 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 422 <tr><td><a name="diff002 1" /></td></tr>398 <tr><td><a name="diff0020" /></td></tr> 423 399 <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> 424 400 <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> 425 <tr><td class="lineno" valign="top"></td><td class="lblock"> read-only, or <span class="delete">which</span> causes <span class="delete">side-effects</span> while invoking a safe method.</td><td> </td><td class="rblock"> entirely read-only, or <span class="insert">that</span> causes <span class="insert">side effects</span>while invoking a safe</td><td class="lineno" valign="top"></td></tr>401 <tr><td class="lineno" valign="top"></td><td class="lblock"> read-only, or <span class="delete">which</span> causes side effects while invoking a safe method.</td><td> </td><td class="rblock"> entirely read-only, or <span class="insert">that</span> causes side effects while invoking a safe</td><td class="lineno" valign="top"></td></tr> 426 402 <tr><td class="lineno" valign="top"></td><td class="lblock"> What is important, however, is that the client did not request that</td><td> </td><td class="rblock"> method. What is important, however, is that the client did not</td><td class="lineno" valign="top"></td></tr> 427 403 <tr><td class="lineno" valign="top"></td><td class="lblock"> additional behavior and cannot be held accountable for it. For</td><td> </td><td class="rblock"> request that additional behavior and cannot be held accountable for</td><td class="lineno" valign="top"></td></tr> … … 430 406 <tr><td class="lineno" valign="top"></td><td class="lblock"> that is considered safe even though the log storage might become full</td><td> </td><td class="rblock"> method, and that is considered safe even though the log storage might</td><td class="lineno" valign="top"></td></tr> 431 407 <tr><td class="lineno" valign="top"></td><td class="lblock"> and crash the server. Likewise, a safe request initiated by</td><td> </td><td class="rblock"> become full and crash the server. Likewise, a safe request initiated</td><td class="lineno" valign="top"></td></tr> 432 <tr><td class="lineno" valign="top"></td><td class="lblock"> selecting an advertisement on the Web will often have the <span class="delete">side-effect</span></td><td> </td><td class="rblock"> by selecting an advertisement on the Web will often have the <span class="insert">side</span></td><td class="lineno" valign="top"></td></tr>433 <tr><td class="lineno" valign="top"></td><td class="lblock"> of charging an advertising account.</td><td> </td><td class="rblock"> <span class="insert"> effect</span>of charging an advertising account.</td><td class="lineno" valign="top"></td></tr>408 <tr><td class="lineno" valign="top"></td><td class="lblock"> selecting an advertisement on the Web will often have the side effect</td><td> </td><td class="rblock"> by selecting an advertisement on the Web will often have the side</td><td class="lineno" valign="top"></td></tr> 409 <tr><td class="lineno" valign="top"></td><td class="lblock"> of charging an advertising account.</td><td> </td><td class="rblock"> effect of charging an advertising account.</td><td class="lineno" valign="top"></td></tr> 434 410 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 435 411 <tr><td class="lineno" valign="top"></td><td class="left"> Of the request methods defined by this specification, the GET, HEAD,</td><td> </td><td class="right"> Of the request methods defined by this specification, the GET, HEAD,</td><td class="lineno" valign="top"></td></tr> … … 443 419 <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> 444 420 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></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> 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> 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> 448 <tr><td class="lineno" valign="top"></td><td class="left"> When a resource is constructed such that parameters within the</td><td> </td><td class="right"> When a resource is constructed such that parameters within the</td><td class="lineno" valign="top"></td></tr> 449 <tr><td class="lineno" valign="top"></td><td class="left"> effective request URI have the effect of selecting an action, it is</td><td> </td><td class="right"> effective request URI have the effect of selecting an action, it is</td><td class="lineno" valign="top"></td></tr> 450 <tr><td class="lineno" valign="top"></td><td class="left"> the resource owner's responsibility to ensure that the action is</td><td> </td><td class="right"> the resource owner's responsibility to ensure that the action is</td><td class="lineno" valign="top"></td></tr> 451 <tr><td class="lineno" valign="top"></td><td class="left"> consistent with the request method semantics. For example, it is</td><td> </td><td class="right"> consistent with the request method semantics. For example, it is</td><td class="lineno" valign="top"></td></tr> 452 <tr><td class="lineno" valign="top"></td><td class="left"> common for Web-based content editing software to use actions within</td><td> </td><td class="right"> common for Web-based content editing software to use actions within</td><td class="lineno" valign="top"></td></tr> 453 <tr><td class="lineno" valign="top"></td><td class="left"> query parameters, such as "page?do=delete". If the purpose of such a</td><td> </td><td class="right"> query parameters, such as "page?do=delete". If the purpose of such a</td><td class="lineno" valign="top"></td></tr> 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> 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> 456 <tr><td><a name="diff0022" /></td></tr> 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> 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> 459 <tr><td class="lineno" valign="top"></td><td class="left"> for the sake of link maintenance, pre-fetching, building a search</td><td> </td><td class="right"> for the sake of link maintenance, pre-fetching, building a search</td><td class="lineno" valign="top"></td></tr> 460 <tr><td class="lineno" valign="top"></td><td class="left"> index, etc.</td><td> </td><td class="right"> index, etc.</td><td class="lineno" valign="top"></td></tr> 461 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 462 <tr><td class="lineno" valign="top"></td><td class="left">4.2.2. Idempotent Methods</td><td> </td><td class="right">4.2.2. Idempotent Methods</td><td class="lineno" valign="top"></td></tr> 463 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 464 <tr><td class="lineno" valign="top"></td><td class="left"> A request method is considered "idempotent" if the intended effect on</td><td> </td><td class="right"> A request method is considered "idempotent" if the intended effect on</td><td class="lineno" valign="top"></td></tr> 465 <tr><td class="lineno" valign="top"></td><td class="left"> the server of multiple identical requests with that method is the</td><td> </td><td class="right"> the server of multiple identical requests with that method is the</td><td class="lineno" valign="top"></td></tr> 466 <tr><td class="lineno" valign="top"></td><td class="left"> same as the effect for a single such request. Of the request methods</td><td> </td><td class="right"> same as the effect for a single such request. Of the request methods</td><td class="lineno" valign="top"></td></tr> 467 <tr><td class="lineno" valign="top"></td><td class="left"> defined by this specification, PUT, DELETE, and safe request methods</td><td> </td><td class="right"> defined by this specification, PUT, DELETE, and safe request methods</td><td class="lineno" valign="top"></td></tr> 468 <tr><td class="lineno" valign="top"></td><td class="left"> are idempotent.</td><td> </td><td class="right"> are idempotent.</td><td class="lineno" valign="top"></td></tr> 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> 470 <tr><td class="lineno" valign="top"></td><td class="left"> Like the definition of safe, the idempotent property only applies to</td><td> </td><td class="right"> Like the definition of safe, the idempotent property only applies to</td><td class="lineno" valign="top"></td></tr> 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> 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> 473 <tr><td><a name="diff0023" /></td></tr> 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> 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> 476 <tr><td class="lineno" valign="top"></td><td class="left"> Idempotent methods are distinguished because the request can be</td><td> </td><td class="right"> Idempotent methods are distinguished because the request can be</td><td class="lineno" valign="top"></td></tr> 477 <tr><td class="lineno" valign="top"></td><td class="left"> repeated automatically if a communication failure occurs before the</td><td> </td><td class="right"> repeated automatically if a communication failure occurs before the</td><td class="lineno" valign="top"></td></tr> 478 <tr><td class="lineno" valign="top"></td><td class="left"> client is able to read the server's response. For example, if a</td><td> </td><td class="right"> client is able to read the server's response. For example, if a</td><td class="lineno" valign="top"></td></tr> 479 <tr><td class="lineno" valign="top"></td><td class="left"> client sends a PUT request and the underlying connection is closed</td><td> </td><td class="right"> client sends a PUT request and the underlying connection is closed</td><td class="lineno" valign="top"></td></tr> 480 <tr><td class="lineno" valign="top"></td><td class="left"> before any response is received, then the client can establish a new</td><td> </td><td class="right"> before any response is received, then the client can establish a new</td><td class="lineno" valign="top"></td></tr> 481 <tr><td class="lineno" valign="top"></td><td class="left"> connection and retry the idempotent request. It knows that repeating</td><td> </td><td class="right"> connection and retry the idempotent request. It knows that repeating</td><td class="lineno" valign="top"></td></tr> 482 <tr><td class="lineno" valign="top"></td><td class="left"> the request will have the same intended effect, even if the original</td><td> </td><td class="right"> the request will have the same intended effect, even if the original</td><td class="lineno" valign="top"></td></tr> 483 <tr><td class="lineno" valign="top"></td><td class="left"> request succeeded, though the response might differ.</td><td> </td><td class="right"> request succeeded, though the response might differ.</td><td class="lineno" valign="top"></td></tr> 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> 485 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></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> 421 <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 26, line 14</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 26, line 14</em></th><td></td></tr> 487 422 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 488 423 <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> … … 495 430 <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> 496 431 <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> 497 <tr><td><a name="diff002 4" /></td></tr>432 <tr><td><a name="diff0021" /></td></tr> 498 433 <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> 499 434 <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> … … 509 444 <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> 510 445 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></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> 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> 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> 514 <tr><td class="lineno" valign="top"></td><td class="left"> request, SHOULD be implemented using the POST method rather than PUT.</td><td> </td><td class="right"> request, SHOULD be implemented using the POST method rather than PUT.</td><td class="lineno" valign="top"></td></tr> 515 <tr><td class="lineno" valign="top"></td><td class="left"> If the origin server will not make the requested PUT state change to</td><td> </td><td class="right"> If the origin server will not make the requested PUT state change to</td><td class="lineno" valign="top"></td></tr> 516 <tr><td class="lineno" valign="top"></td><td class="left"> the target resource and instead wishes to have it applied to a</td><td> </td><td class="right"> the target resource and instead wishes to have it applied to a</td><td class="lineno" valign="top"></td></tr> 517 <tr><td class="lineno" valign="top"></td><td class="left"> different resource, such as when the resource has been moved to a</td><td> </td><td class="right"> different resource, such as when the resource has been moved to a</td><td class="lineno" valign="top"></td></tr> 518 <tr><td class="lineno" valign="top"></td><td class="left"> different URI, then the origin server MUST send an appropriate 3xx</td><td> </td><td class="right"> different URI, then the origin server MUST send an appropriate 3xx</td><td class="lineno" valign="top"></td></tr> 519 <tr><td class="lineno" valign="top"></td><td class="left"> (Redirection) response; the user agent MAY then make its own decision</td><td> </td><td class="right"> (Redirection) response; the user agent MAY then make its own decision</td><td class="lineno" valign="top"></td></tr> 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> 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> 522 <tr><td><a name="diff0025" /></td></tr> 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> 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> 525 <tr><td class="lineno" valign="top"></td><td class="left"> identifying "the current version" (a resource) that is separate from</td><td> </td><td class="right"> identifying "the current version" (a resource) that is separate from</td><td class="lineno" valign="top"></td></tr> 526 <tr><td class="lineno" valign="top"></td><td class="left"> the URIs identifying each particular version (different resources</td><td> </td><td class="right"> the URIs identifying each particular version (different resources</td><td class="lineno" valign="top"></td></tr> 527 <tr><td class="lineno" valign="top"></td><td class="left"> that at one point shared the same state as the current version</td><td> </td><td class="right"> that at one point shared the same state as the current version</td><td class="lineno" valign="top"></td></tr> 528 <tr><td class="lineno" valign="top"></td><td class="left"> resource). A successful PUT request on "the current version" URI</td><td> </td><td class="right"> resource). A successful PUT request on "the current version" URI</td><td class="lineno" valign="top"></td></tr> 529 <tr><td class="lineno" valign="top"></td><td class="left"> might therefore create a new version resource in addition to changing</td><td> </td><td class="right"> might therefore create a new version resource in addition to changing</td><td class="lineno" valign="top"></td></tr> 530 <tr><td class="lineno" valign="top"></td><td class="left"> the state of the target resource, and might also cause links to be</td><td> </td><td class="right"> the state of the target resource, and might also cause links to be</td><td class="lineno" valign="top"></td></tr> 531 <tr><td class="lineno" valign="top"></td><td class="left"> added between the related resources.</td><td> </td><td class="right"> added between the related resources.</td><td class="lineno" valign="top"></td></tr> 532 <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 <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> 534 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></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> 446 <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 30, line 31</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 30, line 33</em></th><td></td></tr> 536 447 <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> 537 448 <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> … … 544 455 <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> 545 456 <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> 546 <tr><td><a name="diff002 6" /></td></tr>457 <tr><td><a name="diff0022" /></td></tr> 547 458 <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> 548 459 <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> … … 558 469 <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> 559 470 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 560 <tr bgcolor="gray" ><td></td><th><a name="part-l1 7" /><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>471 <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 34, line 14</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 34, line 14</em></th><td></td></tr> 561 472 <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 473 <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> … … 569 480 <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> 570 481 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 571 <tr><td><a name="diff002 7" /></td></tr>482 <tr><td><a name="diff0023" /></td></tr> 572 483 <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> 573 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> … … 582 493 <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> 583 494 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 584 <tr bgcolor="gray" ><td></td><th><a name="part-l1 8" /><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>495 <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 36, line 12</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 36, line 12</em></th><td></td></tr> 585 496 <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> 586 497 <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> … … 593 504 <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> 594 505 <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> 595 <tr><td><a name="diff002 8" /></td></tr>506 <tr><td><a name="diff0024" /></td></tr> 596 507 <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> 597 508 <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> … … 612 523 <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> 613 524 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 614 <tr bgcolor="gray" ><td></td><th><a name="part-l1 9" /><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>525 <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 39, line 12</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 39, line 12</em></th><td></td></tr> 615 526 <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> 616 527 <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> … … 623 534 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 624 535 <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> 625 <tr><td><a name="diff002 9" /></td></tr>536 <tr><td><a name="diff0025" /></td></tr> 626 537 <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> 627 538 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 636 547 <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> 637 548 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 638 <tr bgcolor="gray" ><td></td><th><a name="part-l 20" /><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>549 <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 44, line 30</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 44, line 30</em></th><td></td></tr> 639 550 <tr><td class="lineno" valign="top"></td><td class="left"> +-------------------+---------------+</td><td> </td><td class="right"> +-------------------+---------------+</td><td class="lineno" valign="top"></td></tr> 640 551 <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> … … 647 558 <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> 648 559 <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> 649 <tr><td><a name="diff00 30" /></td></tr>560 <tr><td><a name="diff0026" /></td></tr> 650 561 <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> 651 562 <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> … … 660 571 <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 572 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 662 <tr bgcolor="gray" ><td></td><th><a name="part-l 21" /><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>573 <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 45, line 31</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 45, line 31</em></th><td></td></tr> 663 574 <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> 664 575 <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> … … 671 582 <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> 672 583 <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> 673 <tr><td><a name="diff00 31" /></td></tr>584 <tr><td><a name="diff0027" /></td></tr> 674 585 <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> 675 586 <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> … … 683 594 <tr><td class="lineno" valign="top"></td><td class="left"> Referer header field when the referring resource is a local "file" or</td><td> </td><td class="right"> Referer header field when the referring resource is a local "file" or</td><td class="lineno" valign="top"></td></tr> 684 595 <tr><td class="lineno" valign="top"></td><td class="left"> "data" URI. A user agent MUST NOT send a Referer header field in an</td><td> </td><td class="right"> "data" URI. A user agent MUST NOT send a Referer header field in an</td><td class="lineno" valign="top"></td></tr> 685 <tr><td class="lineno" valign="top"></td><td class="left"> unsecured HTTP request if the referring page was received with a</td><td> </td><td class="right"> unsecured HTTP request if the referring page was received with a</td><td class="lineno" valign="top"></td></tr> 686 <tr><td class="lineno" valign="top"></td><td class="left"> secure protocol. See Section 9.4 for additional security</td><td> </td><td class="right"> secure protocol. See Section 9.4 for additional security</td><td class="lineno" valign="top"></td></tr> 687 <tr><td class="lineno" valign="top"></td><td class="left"> considerations.</td><td> </td><td class="right"> considerations.</td><td class="lineno" valign="top"></td></tr> 688 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 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> 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> 691 <tr><td><a name="diff0032" /></td></tr> 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> 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> 694 <tr><td class="lineno" valign="top"></td><td class="left"> Intermediaries and user agent extensions that wish to limit</td><td> </td><td class="right"> Intermediaries and user agent extensions that wish to limit</td><td class="lineno" valign="top"></td></tr> 695 <tr><td class="lineno" valign="top"></td><td class="left"> information disclosure in Referer ought to restrict their changes to</td><td> </td><td class="right"> information disclosure in Referer ought to restrict their changes to</td><td class="lineno" valign="top"></td></tr> 696 <tr><td class="lineno" valign="top"></td><td class="left"> specific edits, such as replacing internal domain names with</td><td> </td><td class="right"> specific edits, such as replacing internal domain names with</td><td class="lineno" valign="top"></td></tr> 596 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 597 <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 46, line 15</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 46, line 15</em></th><td></td></tr> 697 598 <tr><td class="lineno" valign="top"></td><td class="left"> pseudonyms or truncating the query and/or path components. An</td><td> </td><td class="right"> pseudonyms or truncating the query and/or path components. An</td><td class="lineno" valign="top"></td></tr> 698 599 <tr><td class="lineno" valign="top"></td><td class="left"> intermediary SHOULD NOT modify or delete the Referer header field</td><td> </td><td class="right"> intermediary SHOULD NOT modify or delete the Referer header field</td><td class="lineno" valign="top"></td></tr> … … 705 606 <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> 706 607 <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> 707 <tr><td><a name="diff00 33" /></td></tr>608 <tr><td><a name="diff0028" /></td></tr> 708 609 <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> 709 610 <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> … … 715 616 <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> 716 617 <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> 717 <tr><td><a name="diff00 34" /></td></tr>618 <tr><td><a name="diff0029" /></td></tr> 718 619 <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> 719 620 <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> 720 621 <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> 721 <tr><td><a name="diff003 5" /></td></tr>622 <tr><td><a name="diff0030" /></td></tr> 722 623 <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> 723 624 <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> … … 728 629 <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> 729 630 <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> 730 <tr><td><a name="diff0036" /></td></tr> 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> 631 <tr><td class="lineno" valign="top"></td><td class="left"> advertising or other nonessential information within the product</td><td> </td><td class="right"> advertising or other nonessential information within the product</td><td class="lineno" valign="top"></td></tr> 732 632 <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> 733 633 <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> 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> 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> 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> 737 <tr><td class="lineno" valign="top"></td><td class="left"> Example:</td><td> </td><td class="right"> Example:</td><td class="lineno" valign="top"></td></tr> 738 <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 <tr><td class="lineno" valign="top"></td><td class="left"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3</td><td> </td><td class="right"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3</td><td class="lineno" valign="top"></td></tr> 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> 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> 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> 634 <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-l20" /><small>skipping to change at</small><em> page 47, line 9</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 47, line 9</em></th><td></td></tr> 744 636 <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> 745 637 <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> … … 752 644 <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> 753 645 <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> 754 <tr><td><a name="diff003 7" /></td></tr>646 <tr><td><a name="diff0031" /></td></tr> 755 647 <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> 756 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> … … 770 662 <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> 771 663 <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> 772 <tr><td><a name="diff003 8" /></td></tr>664 <tr><td><a name="diff0032" /></td></tr> 773 665 <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> 774 666 <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> … … 785 677 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 786 678 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 787 <tr bgcolor="gray" ><td></td><th><a name="part-l2 3" /><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>679 <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><small>skipping to change at</small><em> page 48, line 14</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 48, line 14</em></th><td></td></tr> 788 680 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 789 681 <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> … … 796 688 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 797 689 <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> 798 <tr><td><a name="diff003 9" /></td></tr>690 <tr><td><a name="diff0033" /></td></tr> 799 691 <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> 800 692 <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> … … 813 705 <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> 814 706 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></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> 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> 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> 818 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 819 <tr><td class="lineno" valign="top"></td><td class="left"> The 202 (Accepted) status code indicates that the request has been</td><td> </td><td class="right"> The 202 (Accepted) status code indicates that the request has been</td><td class="lineno" valign="top"></td></tr> 820 <tr><td class="lineno" valign="top"></td><td class="left"> accepted for processing, but the processing has not been completed.</td><td> </td><td class="right"> accepted for processing, but the processing has not been completed.</td><td class="lineno" valign="top"></td></tr> 821 <tr><td class="lineno" valign="top"></td><td class="left"> The request might or might not eventually be acted upon, as it might</td><td> </td><td class="right"> The request might or might not eventually be acted upon, as it might</td><td class="lineno" valign="top"></td></tr> 822 <tr><td class="lineno" valign="top"></td><td class="left"> be disallowed when processing actually takes place. There is no</td><td> </td><td class="right"> be disallowed when processing actually takes place. There is no</td><td class="lineno" valign="top"></td></tr> 823 <tr><td class="lineno" valign="top"></td><td class="left"> facility in HTTP for re-sending a status code from an asynchronous</td><td> </td><td class="right"> facility in HTTP for re-sending a status code from an asynchronous</td><td class="lineno" valign="top"></td></tr> 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> 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> 826 <tr><td><a name="diff0040" /></td></tr> 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> 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> 829 <tr><td class="lineno" valign="top"></td><td class="left"> batch-oriented process that is only run once per day) without</td><td> </td><td class="right"> batch-oriented process that is only run once per day) without</td><td class="lineno" valign="top"></td></tr> 830 <tr><td class="lineno" valign="top"></td><td class="left"> requiring that the user agent's connection to the server persist</td><td> </td><td class="right"> requiring that the user agent's connection to the server persist</td><td class="lineno" valign="top"></td></tr> 831 <tr><td class="lineno" valign="top"></td><td class="left"> until the process is completed. The representation sent with this</td><td> </td><td class="right"> until the process is completed. The representation sent with this</td><td class="lineno" valign="top"></td></tr> 832 <tr><td class="lineno" valign="top"></td><td class="left"> response ought to describe the request's current status and point to</td><td> </td><td class="right"> response ought to describe the request's current status and point to</td><td class="lineno" valign="top"></td></tr> 833 <tr><td class="lineno" valign="top"></td><td class="left"> (or embed) a status monitor that can provide the user with an</td><td> </td><td class="right"> (or embed) a status monitor that can provide the user with an</td><td class="lineno" valign="top"></td></tr> 834 <tr><td class="lineno" valign="top"></td><td class="left"> estimate of when the request will be fulfilled.</td><td> </td><td class="right"> estimate of when the request will be fulfilled.</td><td class="lineno" valign="top"></td></tr> 835 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 836 <tr><td class="lineno" valign="top"></td><td class="left">6.3.4. 203 Non-Authoritative Information</td><td> </td><td class="right">6.3.4. 203 Non-Authoritative Information</td><td class="lineno" valign="top"></td></tr> 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> 838 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></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> 707 <tr bgcolor="gray" ><td></td><th><a name="part-l22" /><small>skipping to change at</small><em> page 56, line 6</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 56, line 6</em></th><td></td></tr> 840 708 <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> 841 709 <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> … … 848 716 <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> 849 717 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 850 <tr><td><a name="diff00 41" /></td></tr>718 <tr><td><a name="diff0034" /></td></tr> 851 719 <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> 852 720 <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> … … 864 732 <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> 865 733 <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> 866 <tr><td><a name="diff00 42" /></td></tr>734 <tr><td><a name="diff0035" /></td></tr> 867 735 <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> 868 736 <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> … … 877 745 <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> 878 746 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 879 <tr bgcolor="gray" ><td></td><th><a name="part-l2 6" /><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>747 <tr bgcolor="gray" ><td></td><th><a name="part-l23" /><small>skipping to change at</small><em> page 58, line 23</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 58, line 23</em></th><td></td></tr> 880 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> 881 749 <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> … … 888 756 <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> 889 757 <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> 890 <tr><td><a name="diff00 43" /></td></tr>758 <tr><td><a name="diff0036" /></td></tr> 891 759 <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> 892 760 <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> … … 901 769 <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> 902 770 <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-l2 7" /><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>771 <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 66, line 9</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 66, line 9</em></th><td></td></tr> 904 772 <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> 905 773 <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> … … 912 780 <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> 913 781 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 914 <tr><td><a name="diff00 44" /></td></tr>782 <tr><td><a name="diff0037" /></td></tr> 915 783 <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> 916 784 <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> … … 925 793 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 926 794 <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> 927 <tr><td><a name="diff00 45" /></td></tr>795 <tr><td><a name="diff0038" /></td></tr> 928 796 <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> 929 797 <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> … … 940 808 <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> 941 809 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 942 <tr><td><a name="diff00 46" /></td></tr>810 <tr><td><a name="diff0039" /></td></tr> 943 811 <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> 944 812 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 957 825 <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> 958 826 <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="diff004 7" /></td></tr>827 <tr><td><a name="diff0040" /></td></tr> 960 828 <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> 961 829 <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> … … 976 844 <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> 977 845 <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 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>846 <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 70, line 30</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 70, line 30</em></th><td></td></tr> 979 847 <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> 980 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> … … 987 855 <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> 988 856 <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> 989 <tr><td><a name="diff004 8" /></td></tr>857 <tr><td><a name="diff0041" /></td></tr> 990 858 <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> 991 859 <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> … … 1000 868 <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> 1001 869 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1002 <tr bgcolor="gray" ><td></td><th><a name="part-l2 9" /><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>870 <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 71, line 22</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 71, line 22</em></th><td></td></tr> 1003 871 <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 872 <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> … … 1011 879 <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> 1012 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> 1013 <tr><td><a name="diff004 9" /></td></tr>881 <tr><td><a name="diff0042" /></td></tr> 1014 882 <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> 1015 883 <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> … … 1024 892 <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> 1025 893 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1026 <tr bgcolor="gray" ><td></td><th><a name="part-l 30" /><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>894 <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 72, line 5</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 72, line 5</em></th><td></td></tr> 1027 895 <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> 1028 896 <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> … … 1035 903 <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> 1036 904 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1037 <tr><td><a name="diff00 50" /></td></tr>905 <tr><td><a name="diff0043" /></td></tr> 1038 906 <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> 1039 907 <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> … … 1051 919 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1052 920 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1053 <tr bgcolor="gray" ><td></td><th><a name="part-l 31" /><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>921 <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 74, line 6</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 74, line 6</em></th><td></td></tr> 1054 922 <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> 1055 923 <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> … … 1062 930 <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> 1063 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> 1064 <tr><td><a name="diff00 51" /></td></tr>932 <tr><td><a name="diff0044" /></td></tr> 1065 933 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Method <span class="delete">Registry</span> defines the namespace for the request method</td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Method <span class="insert">Registry"</span> defines the</td><td class="lineno" valign="top"></td></tr> 1066 934 <tr><td class="lineno" valign="top"></td><td class="lblock"> token (Section 4). The <span class="delete">method registry will be</span> created and</td><td> </td><td class="rblock"> namespace for the request method token (Section 4). The <span class="insert">"HTTP Method</span></td><td class="lineno" valign="top"></td></tr> … … 1077 945 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1078 946 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1079 <tr bgcolor="gray" ><td></td><th><a name="part-l 32" /><small>skipping to change at</small><em> page 74, line 44</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 74, line 44</em></th><td></td></tr>947 <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 74, line 44</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 74, line 44</em></th><td></td></tr> 1080 948 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1081 949 <tr><td class="lineno" valign="top"></td><td class="left"> Since message parsing (Section 3.3 of [RFC7230]) needs to be</td><td> </td><td class="right"> Since message parsing (Section 3.3 of [RFC7230]) needs to be</td><td class="lineno" valign="top"></td></tr> … … 1088 956 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1089 957 <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> 1090 <tr><td><a name="diff00 52" /></td></tr>958 <tr><td><a name="diff0045" /></td></tr> 1091 959 <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> 1092 960 <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> … … 1107 975 <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> 1108 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> 1109 <tr><td><a name="diff00 53" /></td></tr>977 <tr><td><a name="diff0046" /></td></tr> 1110 978 <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> 1111 979 <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> … … 1126 994 <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> 1127 995 <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 54" /></td></tr>996 <tr><td><a name="diff0047" /></td></tr> 1129 997 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Status Code <span class="delete">Registry</span> defines the namespace for the response</td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Status Code <span class="insert">Registry"</span> defines</td><td class="lineno" valign="top"></td></tr> 1130 998 <tr><td class="lineno" valign="top"></td><td class="lblock"> status-code token (Section 6). The <span class="delete">status code</span> registry is</td><td> </td><td class="rblock"> the namespace for the response status-code token (Section 6). The</td><td class="lineno" valign="top"></td></tr> … … 1142 1010 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1143 1011 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1144 <tr bgcolor="gray" ><td></td><th><a name="part-l3 3" /><small>skipping to change at</small><em> page 76, line 49</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 76, line 49</em></th><td></td></tr>1012 <tr bgcolor="gray" ><td></td><th><a name="part-l30" /><small>skipping to change at</small><em> page 76, line 49</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 76, line 49</em></th><td></td></tr> 1145 1013 <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> 1146 1014 <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> … … 1153 1021 <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> 1154 1022 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1155 <tr><td><a name="diff00 55" /></td></tr>1023 <tr><td><a name="diff0048" /></td></tr> 1156 1024 <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> 1157 1025 <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> … … 1167 1035 <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> 1168 1036 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1169 <tr bgcolor="gray" ><td></td><th><a name="part-l3 4" /><small>skipping to change at</small><em> page 77, line 48</em></th><th> </th><th><a name="part-r34" /><small>skipping to change at</small><em> page 77, line 48</em></th><td></td></tr>1037 <tr bgcolor="gray" ><td></td><th><a name="part-l31" /><small>skipping to change at</small><em> page 77, line 48</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 77, line 48</em></th><td></td></tr> 1170 1038 <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> 1171 1039 <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> … … 1178 1046 <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> 1179 1047 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1180 <tr><td><a name="diff00 56" /></td></tr>1048 <tr><td><a name="diff0049" /></td></tr> 1181 1049 <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> 1182 1050 <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> … … 1202 1070 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1203 1071 <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> 1204 <tr><td><a name="diff005 7" /></td></tr>1072 <tr><td><a name="diff0050" /></td></tr> 1205 1073 <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> 1206 1074 <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> … … 1217 1085 <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> 1218 1086 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1219 <tr bgcolor="gray" ><td></td><th><a name="part-l3 5" /><small>skipping to change at</small><em> page 80, line 15</em></th><th> </th><th><a name="part-r35" /><small>skipping to change at</small><em> page 80, line 15</em></th><td></td></tr>1087 <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 80, line 15</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 80, line 15</em></th><td></td></tr> 1220 1088 <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> 1221 1089 <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> … … 1228 1096 <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> 1229 1097 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1230 <tr><td><a name="diff005 8" /></td></tr>1098 <tr><td><a name="diff0051" /></td></tr> 1231 1099 <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> 1232 1100 <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> … … 1241 1109 <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> 1242 1110 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1243 <tr bgcolor="gray" ><td></td><th><a name="part-l3 6" /><small>skipping to change at</small><em> page 80, line 48</em></th><th> </th><th><a name="part-r36" /><small>skipping to change at</small><em> page 80, line 48</em></th><td></td></tr>1111 <tr bgcolor="gray" ><td></td><th><a name="part-l33" /><small>skipping to change at</small><em> page 80, line 48</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 80, line 48</em></th><td></td></tr> 1244 1112 <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> 1245 1113 <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> … … 1252 1120 <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> 1253 1121 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1254 <tr><td><a name="diff005 9" /></td></tr>1122 <tr><td><a name="diff0052" /></td></tr> 1255 1123 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Content Coding <span class="delete">Registry</span> defines the namespace for content</td><td> </td><td class="rblock"> The <span class="insert">"HTTP</span> Content Coding <span class="insert">Registry"</span> defines the namespace for content</td><td class="lineno" valign="top"></td></tr> 1256 1124 <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> … … 1260 1128 <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> 1261 1129 <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="diff00 60" /></td></tr>1130 <tr><td><a name="diff0053" /></td></tr> 1263 1131 <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> 1264 1132 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1275 1143 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1276 1144 <tr><td class="lineno" valign="top"></td><td class="left"> Values to be added to this namespace require IETF Review (see Section</td><td> </td><td class="right"> Values to be added to this namespace require IETF Review (see Section</td><td class="lineno" valign="top"></td></tr> 1277 <tr><td><a name="diff00 61" /></td></tr>1145 <tr><td><a name="diff0054" /></td></tr> 1278 1146 <tr><td class="lineno" valign="top"></td><td class="lblock"> 4.1 of [RFC5226])<span class="delete">,</span> and MUST conform to the purpose of content coding</td><td> </td><td class="rblock"> 4.1 of [RFC5226]) and MUST conform to the purpose of content coding</td><td class="lineno" valign="top"></td></tr> 1279 1147 <tr><td class="lineno" valign="top"></td><td class="left"> defined in this section.</td><td> </td><td class="right"> defined in this section.</td><td class="lineno" valign="top"></td></tr> … … 1281 1149 <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> 1282 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> 1283 <tr><td><a name="diff00 62" /></td></tr>1151 <tr><td><a name="diff0055" /></td></tr> 1284 1152 <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> 1285 1153 <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> … … 1302 1170 <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> 1303 1171 <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> 1304 <tr><td><a name="diff00 63" /></td></tr>1172 <tr><td><a name="diff0056" /></td></tr> 1305 1173 <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> 1306 1174 <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> … … 1320 1188 <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> 1321 1189 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1322 <tr bgcolor="gray" ><td></td><th><a name="part-l3 7" /><small>skipping to change at</small><em> page 82, line 25</em></th><th> </th><th><a name="part-r37" /><small>skipping to change at</small><em> page 82, line 25</em></th><td></td></tr>1190 <tr bgcolor="gray" ><td></td><th><a name="part-l34" /><small>skipping to change at</small><em> page 82, line 25</em></th><th> </th><th><a name="part-r34" /><small>skipping to change at</small><em> page 82, line 25</em></th><td></td></tr> 1323 1191 <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> 1324 1192 <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> … … 1331 1199 <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> 1332 1200 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1333 <tr><td><a name="diff00 64" /></td></tr>1201 <tr><td><a name="diff0057" /></td></tr> 1334 1202 <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> 1335 1203 <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> … … 1345 1213 <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> 1346 1214 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1347 <tr bgcolor="gray" ><td></td><th><a name="part-l3 8" /><small>skipping to change at</small><em> page 83, line 41</em></th><th> </th><th><a name="part-r38" /><small>skipping to change at</small><em> page 83, line 41</em></th><td></td></tr>1215 <tr bgcolor="gray" ><td></td><th><a name="part-l35" /><small>skipping to change at</small><em> page 83, line 41</em></th><th> </th><th><a name="part-r35" /><small>skipping to change at</small><em> page 83, line 41</em></th><td></td></tr> 1348 1216 <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> 1349 1217 <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> … … 1356 1224 <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> 1357 1225 <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> 1358 <tr><td><a name="diff00 65" /></td></tr>1226 <tr><td><a name="diff0058" /></td></tr> 1359 1227 <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> 1360 1228 <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> … … 1370 1238 <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> 1371 1239 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1372 <tr bgcolor="gray" ><td></td><th><a name="part-l3 9" /><small>skipping to change at</small><em> page 86, line 15</em></th><th> </th><th><a name="part-r39" /><small>skipping to change at</small><em> page 86, line 15</em></th><td></td></tr>1240 <tr bgcolor="gray" ><td></td><th><a name="part-l36" /><small>skipping to change at</small><em> page 86, line 15</em></th><th> </th><th><a name="part-r36" /><small>skipping to change at</small><em> page 86, line 15</em></th><td></td></tr> 1373 1241 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1374 1242 <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> … … 1381 1249 <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> 1382 1250 <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> 1383 <tr><td><a name="diff00 66" /></td></tr>1251 <tr><td><a name="diff0059" /></td></tr> 1384 1252 <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> 1385 1253 <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> 1386 1254 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1387 1255 <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> 1388 <tr><td><a name="diff006 7" /></td></tr>1256 <tr><td><a name="diff0060" /></td></tr> 1389 1257 <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> 1390 1258 <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> … … 1393 1261 <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> 1394 1262 <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> 1395 <tr><td><a name="diff006 8" /></td></tr>1263 <tr><td><a name="diff0061" /></td></tr> 1396 1264 <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> 1397 1265 <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> … … 1399 1267 <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> 1400 1268 <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> 1401 <tr><td><a name="diff006 9" /></td></tr>1269 <tr><td><a name="diff0062" /></td></tr> 1402 1270 <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> 1403 1271 <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> 1404 1272 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1405 1273 <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> 1406 <tr><td><a name="diff00 70" /></td></tr>1274 <tr><td><a name="diff0063" /></td></tr> 1407 1275 <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> 1408 1276 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p7-auth-latest (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> … … 1419 1287 <tr><td class="lineno" valign="top"></td><td class="left"> Application Protocols", BCP 178, RFC 6648, June 2012.</td><td> </td><td class="right"> Application Protocols", BCP 178, RFC 6648, June 2012.</td><td class="lineno" valign="top"></td></tr> 1420 1288 <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-l 40" /><small>skipping to change at</small><em> page 88, line 32</em></th><th> </th><th><a name="part-r40" /><small>skipping to change at</small><em> page 88, line 26</em></th><td></td></tr>1289 <tr bgcolor="gray" ><td></td><th><a name="part-l37" /><small>skipping to change at</small><em> page 88, line 32</em></th><th> </th><th><a name="part-r37" /><small>skipping to change at</small><em> page 88, line 26</em></th><td></td></tr> 1422 1290 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010.</td><td> </td><td class="right"> [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010.</td><td class="lineno" valign="top"></td></tr> 1423 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> … … 1430 1298 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1431 1299 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7238] Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td> </td><td class="right"> [RFC7238] Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td class="lineno" valign="top"></td></tr> 1432 <tr><td><a name="diff00 71" /></td></tr>1300 <tr><td><a name="diff0064" /></td></tr> 1433 1301 <tr><td class="lineno" valign="top"></td><td class="lblock"> Status Code 308 (Permanent Redirect)",</td><td> </td><td class="rblock"> Status Code 308 (Permanent Redirect)", <span class="insert">RFC 7238, May 2014.</span></td><td class="lineno" valign="top"></td></tr> 1434 1302 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-reschke-http-status-308-07 (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> … … 1445 1313 <tr><td class="lineno" valign="top"></td><td class="left"> that differ from MIME. These differences were carefully chosen to</td><td> </td><td class="right"> that differ from MIME. These differences were carefully chosen to</td><td class="lineno" valign="top"></td></tr> 1446 1314 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1447 <tr bgcolor="gray" ><td></td><th><a name="part-l 41" /><small>skipping to change at</small><em> page 90, line 27</em></th><th> </th><th><a name="part-r41" /><small>skipping to change at</small><em> page 90, line 20</em></th><td></td></tr>1315 <tr bgcolor="gray" ><td></td><th><a name="part-l38" /><small>skipping to change at</small><em> page 90, line 27</em></th><th> </th><th><a name="part-r38" /><small>skipping to change at</small><em> page 90, line 20</em></th><td></td></tr> 1448 1316 <tr><td class="lineno" valign="top"></td><td class="left"> message to an HTTP client.</td><td> </td><td class="right"> message to an HTTP client.</td><td class="lineno" valign="top"></td></tr> 1449 1317 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1456 1324 <tr><td class="lineno" valign="top"></td><td class="left"> likelihood of safe transport over the destination protocol.</td><td> </td><td class="right"> likelihood of safe transport over the destination protocol.</td><td class="lineno" valign="top"></td></tr> 1457 1325 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1458 <tr><td><a name="diff00 72" /></td></tr>1326 <tr><td><a name="diff0065" /></td></tr> 1459 1327 <tr><td class="lineno" valign="top"></td><td class="lblock">A.6. MHTML and Line<span class="delete"> </span>Length Limitations</td><td> </td><td class="rblock">A.6. MHTML and Line<span class="insert">-</span>Length Limitations</td><td class="lineno" valign="top"></td></tr> 1460 1328 <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 1329 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP implementations that share code with MHTML [RFC2557]</td><td> </td><td class="right"> HTTP implementations that share code with MHTML [RFC2557]</td><td class="lineno" valign="top"></td></tr> 1462 <tr><td><a name="diff00 73" /></td></tr>1330 <tr><td><a name="diff0066" /></td></tr> 1463 1331 <tr><td class="lineno" valign="top"></td><td class="lblock"> implementations need to be aware of MIME line<span class="delete"> </span>length limitations.</td><td> </td><td class="rblock"> implementations need to be aware of MIME line<span class="insert">-</span>length limitations.</td><td class="lineno" valign="top"></td></tr> 1464 1332 <tr><td class="lineno" valign="top"></td><td class="left"> Since HTTP does not have this limitation, HTTP does not fold long</td><td> </td><td class="right"> Since HTTP does not have this limitation, HTTP does not fold long</td><td class="lineno" valign="top"></td></tr> 1465 1333 <tr><td class="lineno" valign="top"></td><td class="left"> lines. MHTML messages being transported by HTTP follow all</td><td> </td><td class="right"> lines. MHTML messages being transported by HTTP follow all</td><td class="lineno" valign="top"></td></tr> 1466 <tr><td><a name="diff00 74" /></td></tr>1334 <tr><td><a name="diff0067" /></td></tr> 1467 1335 <tr><td class="lineno" valign="top"></td><td class="lblock"> conventions of MHTML, including line<span class="delete"> </span>length limitations and folding,</td><td> </td><td class="rblock"> conventions of MHTML, including line<span class="insert">-</span>length limitations and folding,</td><td class="lineno" valign="top"></td></tr> 1468 1336 <tr><td class="lineno" valign="top"></td><td class="left"> canonicalization, etc., since HTTP transfers message-bodies as</td><td> </td><td class="right"> canonicalization, etc., since HTTP transfers message-bodies as</td><td class="lineno" valign="top"></td></tr> … … 1481 1349 <tr><td class="lineno" valign="top"></td><td class="left"> representations and representations from resources.</td><td> </td><td class="right"> representations and representations from resources.</td><td class="lineno" valign="top"></td></tr> 1482 1350 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1483 <tr><td><a name="diff00 75" /></td></tr>1351 <tr><td><a name="diff0068" /></td></tr> 1484 1352 <tr><td class="lineno" valign="top"></td><td class="lblock"> A new requirement has been added that semantics embedded in a URI</td><td> </td><td class="rblock"> A new requirement has been added that semantics embedded in a URI be</td><td class="lineno" valign="top"></td></tr> 1485 1353 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">should</span> be disabled when those semantics are inconsistent with the</td><td> </td><td class="rblock"> disabled when those semantics are inconsistent with the request</td><td class="lineno" valign="top"></td></tr> … … 1488 1356 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1489 1357 <tr><td class="lineno" valign="top"></td><td class="left"> An algorithm has been added for determining if a payload is</td><td> </td><td class="right"> An algorithm has been added for determining if a payload is</td><td class="lineno" valign="top"></td></tr> 1490 <tr><td><a name="diff00 76" /></td></tr>1358 <tr><td><a name="diff0069" /></td></tr> 1491 1359 <tr><td class="lineno" valign="top"></td><td class="lblock"> associated with a specific identifier<span class="delete">. (Section 3.1.4.1)</span></td><td> </td><td class="rblock"> associated with a specific identifier<span class="insert"> (Section 3.1.4.1).</span></td><td class="lineno" valign="top"></td></tr> 1492 1360 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1494 1362 <tr><td class="lineno" valign="top"></td><td class="left"> removed; the default is now whatever the media type definition says.</td><td> </td><td class="right"> removed; the default is now whatever the media type definition says.</td><td class="lineno" valign="top"></td></tr> 1495 1363 <tr><td class="lineno" valign="top"></td><td class="left"> Likewise, special treatment of ISO-8859-1 has been removed from the</td><td> </td><td class="right"> Likewise, special treatment of ISO-8859-1 has been removed from the</td><td class="lineno" valign="top"></td></tr> 1496 <tr><td><a name="diff007 7" /></td></tr>1364 <tr><td><a name="diff0070" /></td></tr> 1497 1365 <tr><td class="lineno" valign="top"></td><td class="lblock"> Accept-Charset header field. (Section<span class="delete"> 3.1.1.3 and Section 5.3.3</span>)</td><td> </td><td class="rblock"> Accept-Charset header field. (Section<span class="insert">s 3.1.1.3 and 5.3.3.</span>)</td><td class="lineno" valign="top"></td></tr> 1498 1366 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1500 1368 <tr><td class="lineno" valign="top"></td><td class="left"> affect the base URI for resolving relative URI references, due to</td><td> </td><td class="right"> affect the base URI for resolving relative URI references, due to</td><td class="lineno" valign="top"></td></tr> 1501 1369 <tr><td class="lineno" valign="top"></td><td class="left"> poor implementation support and the undesirable effect of potentially</td><td> </td><td class="right"> poor implementation support and the undesirable effect of potentially</td><td class="lineno" valign="top"></td></tr> 1502 <tr><td><a name="diff007 8" /></td></tr>1370 <tr><td><a name="diff0071" /></td></tr> 1503 1371 <tr><td class="lineno" valign="top"></td><td class="lblock"> breaking relative links in content-negotiated <span class="delete">resources.</span></td><td> </td><td class="rblock"> breaking relative links in content-negotiated <span class="insert">resources</span></td><td class="lineno" valign="top"></td></tr> 1504 1372 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">3.1.4.2)</span></td><td> </td><td class="rblock"> (Section <span class="insert">3.1.4.2).</span></td><td class="lineno" valign="top"></td></tr> … … 1506 1374 <tr><td class="lineno" valign="top"></td><td class="left"> To be consistent with the method-neutral parsing algorithm of</td><td> </td><td class="right"> To be consistent with the method-neutral parsing algorithm of</td><td class="lineno" valign="top"></td></tr> 1507 1375 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7230], the definition of GET has been relaxed so that requests</td><td> </td><td class="right"> [RFC7230], the definition of GET has been relaxed so that requests</td><td class="lineno" valign="top"></td></tr> 1508 <tr><td><a name="diff007 9" /></td></tr>1376 <tr><td><a name="diff0072" /></td></tr> 1509 1377 <tr><td class="lineno" valign="top"></td><td class="lblock"> can have a body, even though a body has no meaning for <span class="delete">GET.</span></td><td> </td><td class="rblock"> can have a body, even though a body has no meaning for <span class="insert">GET</span></td><td class="lineno" valign="top"></td></tr> 1510 1378 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">4.3.1)</span></td><td> </td><td class="rblock"> (Section <span class="insert">4.3.1).</span></td><td class="lineno" valign="top"></td></tr> 1511 1379 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1512 1380 <tr><td class="lineno" valign="top"></td><td class="left"> Servers are no longer required to handle all Content-* header fields</td><td> </td><td class="right"> Servers are no longer required to handle all Content-* header fields</td><td class="lineno" valign="top"></td></tr> 1513 <tr><td><a name="diff00 80" /></td></tr>1381 <tr><td><a name="diff0073" /></td></tr> 1514 1382 <tr><td class="lineno" valign="top"></td><td class="lblock"> and use of Content-Range has been explicitly banned in PUT <span class="delete">requests.</span></td><td> </td><td class="rblock"> and use of Content-Range has been explicitly banned in PUT <span class="insert">requests</span></td><td class="lineno" valign="top"></td></tr> 1515 1383 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">4.3.4)</span></td><td> </td><td class="rblock"> (Section <span class="insert">4.3.4).</span></td><td class="lineno" valign="top"></td></tr> 1516 1384 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1517 1385 <tr><td class="lineno" valign="top"></td><td class="left"> Definition of the CONNECT method has been moved from [RFC2817] to</td><td> </td><td class="right"> Definition of the CONNECT method has been moved from [RFC2817] to</td><td class="lineno" valign="top"></td></tr> 1518 <tr><td><a name="diff00 81" /></td></tr>1386 <tr><td><a name="diff0074" /></td></tr> 1519 1387 <tr><td class="lineno" valign="top"></td><td class="lblock"> this specification<span class="delete">. (Section 4.3.6)</span></td><td> </td><td class="rblock"> this specification<span class="insert"> (Section 4.3.6).</span></td><td class="lineno" valign="top"></td></tr> 1520 1388 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1521 <tr><td><a name="diff00 82" /></td></tr>1389 <tr><td><a name="diff0075" /></td></tr> 1522 1390 <tr><td class="lineno" valign="top"></td><td class="lblock"> The OPTIONS and TRACE request methods have been defined as being</td><td> </td><td class="rblock"> The OPTIONS and TRACE request methods have been defined as being <span class="insert">safe</span></td><td class="lineno" valign="top"></td></tr> 1523 1391 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">safe.</span> (Section 4.3.7 and Section <span class="delete">4.3.8)</span></td><td> </td><td class="rblock"> (Section 4.3.7 and Section <span class="insert">4.3.8).</span></td><td class="lineno" valign="top"></td></tr> 1524 1392 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1525 1393 <tr><td class="lineno" valign="top"></td><td class="left"> The Expect header field's extension mechanism has been removed due to</td><td> </td><td class="right"> The Expect header field's extension mechanism has been removed due to</td><td class="lineno" valign="top"></td></tr> 1526 <tr><td><a name="diff00 83" /></td></tr>1394 <tr><td><a name="diff0076" /></td></tr> 1527 1395 <tr><td class="lineno" valign="top"></td><td class="lblock"> widely<span class="delete">-deployed broken implementations. (Section 5.1.1)</span></td><td> </td><td class="rblock"> widely<span class="insert"> deployed broken implementations (Section 5.1.1).</span></td><td class="lineno" valign="top"></td></tr> 1528 1396 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1529 1397 <tr><td class="lineno" valign="top"></td><td class="left"> The Max-Forwards header field has been restricted to the OPTIONS and</td><td> </td><td class="right"> The Max-Forwards header field has been restricted to the OPTIONS and</td><td class="lineno" valign="top"></td></tr> 1530 1398 <tr><td class="lineno" valign="top"></td><td class="left"> TRACE methods; previously, extension methods could have used it as</td><td> </td><td class="right"> TRACE methods; previously, extension methods could have used it as</td><td class="lineno" valign="top"></td></tr> 1531 <tr><td><a name="diff00 84" /></td></tr>1399 <tr><td><a name="diff0077" /></td></tr> 1532 1400 <tr><td class="lineno" valign="top"></td><td class="lblock"> well<span class="delete">. (Section 5.1.2)</span></td><td> </td><td class="rblock"> well<span class="insert"> (Section 5.1.2).</span></td><td class="lineno" valign="top"></td></tr> 1533 1401 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1535 1403 <tr><td class="lineno" valign="top"></td><td class="left"> header field when no referring URI is applicable, which distinguishes</td><td> </td><td class="right"> header field when no referring URI is applicable, which distinguishes</td><td class="lineno" valign="top"></td></tr> 1536 1404 <tr><td class="lineno" valign="top"></td><td class="left"> that case from others where the Referer field is not sent or has been</td><td> </td><td class="right"> that case from others where the Referer field is not sent or has been</td><td class="lineno" valign="top"></td></tr> 1537 <tr><td><a name="diff00 85" /></td></tr>1405 <tr><td><a name="diff0078" /></td></tr> 1538 1406 <tr><td class="lineno" valign="top"></td><td class="lblock"> removed<span class="delete">. (Section 5.5.2)</span></td><td> </td><td class="rblock"> removed<span class="insert"> (Section 5.5.2).</span></td><td class="lineno" valign="top"></td></tr> 1539 1407 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1540 1408 <tr><td class="lineno" valign="top"></td><td class="left"> The following status codes are now cacheable (that is, they can be</td><td> </td><td class="right"> The following status codes are now cacheable (that is, they can be</td><td class="lineno" valign="top"></td></tr> 1541 1409 <tr><td class="lineno" valign="top"></td><td class="left"> stored and reused by a cache without explicit freshness information</td><td> </td><td class="right"> stored and reused by a cache without explicit freshness information</td><td class="lineno" valign="top"></td></tr> 1542 <tr><td><a name="diff00 86" /></td></tr>1410 <tr><td><a name="diff0079" /></td></tr> 1543 1411 <tr><td class="lineno" valign="top"></td><td class="lblock"> present): 204, 404, 405, 414, 501<span class="delete">. (Section 6)</span></td><td> </td><td class="rblock"> present): 204, 404, 405, 414, 501<span class="insert"> (Section 6).</span></td><td class="lineno" valign="top"></td></tr> 1544 1412 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1545 1413 <tr><td class="lineno" valign="top"></td><td class="left"> The 201 (Created) status description has been changed to allow for</td><td> </td><td class="right"> The 201 (Created) status description has been changed to allow for</td><td class="lineno" valign="top"></td></tr> 1546 <tr><td><a name="diff008 7" /></td></tr>1414 <tr><td><a name="diff0080" /></td></tr> 1547 1415 <tr><td class="lineno" valign="top"></td><td class="lblock"> the possibility that more than one resource has been <span class="delete">created.</span></td><td> </td><td class="rblock"> the possibility that more than one resource has been <span class="insert">created</span></td><td class="lineno" valign="top"></td></tr> 1548 1416 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">6.3.2)</span></td><td> </td><td class="rblock"> (Section <span class="insert">6.3.2).</span></td><td class="lineno" valign="top"></td></tr> 1549 1417 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1550 1418 <tr><td class="lineno" valign="top"></td><td class="left"> The definition of 203 (Non-Authoritative Information) has been</td><td> </td><td class="right"> The definition of 203 (Non-Authoritative Information) has been</td><td class="lineno" valign="top"></td></tr> 1551 <tr><td><a name="diff008 8" /></td></tr>1419 <tr><td><a name="diff0081" /></td></tr> 1552 1420 <tr><td class="lineno" valign="top"></td><td class="lblock"> broadened to include cases of payload transformations as <span class="delete">well.</span></td><td> </td><td class="rblock"> broadened to include cases of payload transformations as <span class="insert">well</span></td><td class="lineno" valign="top"></td></tr> 1553 1421 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">6.3.4)</span></td><td> </td><td class="rblock"> (Section <span class="insert">6.3.4).</span></td><td class="lineno" valign="top"></td></tr> … …