Changeset 2640
- Timestamp:
- 06/05/14 13:15:23 (7 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/auth48/p1-messaging.unpg.txt
r2639 r2640 1183 1183 Too Long) status code (see Section 6.5.12 of [RFC7231]). 1184 1184 1185 Various ad -hoc limitations on request-line length are found in1185 Various ad hoc limitations on request-line length are found in 1186 1186 practice. It is RECOMMENDED that all HTTP senders and recipients 1187 1187 support, at a minimum, request-line lengths of 8000 octets. … … 1450 1450 HTTP does not place a pre-defined limit on the length of each header 1451 1451 field or on the length of the header section as a whole, as described 1452 in Section 2.5. Various ad -hoc limitations on individual header1452 in Section 2.5. Various ad hoc limitations on individual header 1453 1453 field length are found in practice, often depending on the specific 1454 1454 field semantics. -
draft-ietf-httpbis/latest/auth48/rfc7230.abdiff.txt
r2639 r2640 806 806 807 807 808 Section 400, paragraph 2:809 OLD:810 811 Various ad-hoc limitations on request-line length are found in812 practice. It is RECOMMENDED that all HTTP senders and recipients813 support, at a minimum, request-line lengths of 8000 octets.814 815 NEW:816 817 Various ad hoc limitations on request-line length are found in818 practice. It is RECOMMENDED that all HTTP senders and recipients819 support, at a minimum, request-line lengths of 8000 octets.820 821 822 808 Section 3.1.2., paragraph 1: 823 809 OLD: … … 949 935 HTTP does not place a pre-defined limit on the length of each header 950 936 field or on the length of the header section as a whole, as described 951 in Section 2.5. Various ad -hoc limitations on individual header937 in Section 2.5. Various ad hoc limitations on individual header 952 938 field length are found in practice, often depending on the specific 953 939 field semantics. -
draft-ietf-httpbis/latest/auth48/rfc7230.diff.html
r2639 r2640 623 623 <tr><td class="lineno" valign="top"></td><td class="left"> Too Long) status code (see Section 6.5.12 of [RFC7231]).</td><td> </td><td class="right"> Too Long) status code (see Section 6.5.12 of [RFC7231]).</td><td class="lineno" valign="top"></td></tr> 624 624 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 625 <tr><td><a name="diff0035" /></td></tr> 626 <tr><td class="lineno" valign="top"></td><td class="lblock"> Various ad<span class="delete">-</span>hoc limitations on request-line length are found in</td><td> </td><td class="rblock"> Various ad<span class="insert"> </span>hoc limitations on request-line length are found in</td><td class="lineno" valign="top"></td></tr> 625 <tr><td class="lineno" valign="top"></td><td class="left"> Various ad hoc limitations on request-line length are found in</td><td> </td><td class="right"> Various ad hoc limitations on request-line length are found in</td><td class="lineno" valign="top"></td></tr> 627 626 <tr><td class="lineno" valign="top"></td><td class="left"> practice. It is RECOMMENDED that all HTTP senders and recipients</td><td> </td><td class="right"> practice. It is RECOMMENDED that all HTTP senders and recipients</td><td class="lineno" valign="top"></td></tr> 628 627 <tr><td class="lineno" valign="top"></td><td class="left"> support, at a minimum, request-line lengths of 8000 octets.</td><td> </td><td class="right"> support, at a minimum, request-line lengths of 8000 octets.</td><td class="lineno" valign="top"></td></tr> … … 631 630 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 632 631 <tr><td class="lineno" valign="top"></td><td class="left"> The first line of a response message is the status-line, consisting</td><td> </td><td class="right"> The first line of a response message is the status-line, consisting</td><td class="lineno" valign="top"></td></tr> 633 <tr><td><a name="diff003 6" /></td></tr>632 <tr><td><a name="diff0035" /></td></tr> 634 633 <tr><td class="lineno" valign="top"></td><td class="lblock"> of the protocol version, a space (SP), the status code, another</td><td> </td><td class="rblock"> of the protocol version, a space (SP), the status code, another <span class="insert">space</span></td><td class="lineno" valign="top"></td></tr> 635 634 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">space,</span> a <span class="delete">possibly-empty</span> textual phrase describing the status code,</td><td> </td><td class="rblock"><span class="insert"> (SP),</span> a <span class="insert">possibly empty</span> textual phrase describing the status code,</td><td class="lineno" valign="top"></td></tr> … … 657 656 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 658 657 <tr><td class="lineno" valign="top"></td><td class="left"> All defined header fields ought to be registered with IANA in the</td><td> </td><td class="right"> All defined header fields ought to be registered with IANA in the</td><td class="lineno" valign="top"></td></tr> 659 <tr><td><a name="diff003 7" /></td></tr>658 <tr><td><a name="diff0036" /></td></tr> 660 659 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">Message Header Field R</span>egistry, as described in Section 8.3 of</td><td> </td><td class="rblock"> <span class="insert">"Message Headers" field r</span>egistry, as described in Section 8.3 of</td><td class="lineno" valign="top"></td></tr> 661 660 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7231].</td><td> </td><td class="right"> [RFC7231].</td><td class="lineno" valign="top"></td></tr> … … 681 680 <tr><td class="lineno" valign="top"></td><td class="left"> list syntax, violating the above requirements on multiple header</td><td> </td><td class="right"> list syntax, violating the above requirements on multiple header</td><td class="lineno" valign="top"></td></tr> 682 681 <tr><td class="lineno" valign="top"></td><td class="left"> fields with the same name. Since it cannot be combined into a</td><td> </td><td class="right"> fields with the same name. Since it cannot be combined into a</td><td class="lineno" valign="top"></td></tr> 683 <tr><td><a name="diff003 8" /></td></tr>682 <tr><td><a name="diff0037" /></td></tr> 684 683 <tr><td class="lineno" valign="top"></td><td class="lblock"> single field-value, recipients ought to handle <span class="delete">"Set-Cookie"</span> as a</td><td> </td><td class="rblock"> single field-value, recipients ought to handle <span class="insert">Set-Cookie</span> as a</td><td class="lineno" valign="top"></td></tr> 685 684 <tr><td class="lineno" valign="top"></td><td class="left"> special case while processing header fields. (See Appendix A.2.3</td><td> </td><td class="right"> special case while processing header fields. (See Appendix A.2.3</td><td class="lineno" valign="top"></td></tr> … … 696 695 <tr><td class="lineno" valign="top"></td><td class="left"> preferred to improve readability, a sender SHOULD generate the</td><td> </td><td class="right"> preferred to improve readability, a sender SHOULD generate the</td><td class="lineno" valign="top"></td></tr> 697 696 <tr><td class="lineno" valign="top"></td><td class="left"> optional whitespace as a single SP; otherwise, a sender SHOULD NOT</td><td> </td><td class="right"> optional whitespace as a single SP; otherwise, a sender SHOULD NOT</td><td class="lineno" valign="top"></td></tr> 698 <tr><td><a name="diff003 9" /></td></tr>697 <tr><td><a name="diff0038" /></td></tr> 699 698 <tr><td class="lineno" valign="top"></td><td class="lblock"> generate optional whitespace except as needed to white<span class="delete">-</span>out invalid or</td><td> </td><td class="rblock"> generate optional whitespace except as needed to white<span class="insert"> </span>out invalid or</td><td class="lineno" valign="top"></td></tr> 700 699 <tr><td class="lineno" valign="top"></td><td class="left"> unwanted protocol elements during in-place message filtering.</td><td> </td><td class="right"> unwanted protocol elements during in-place message filtering.</td><td class="lineno" valign="top"></td></tr> … … 720 719 <tr><td class="lineno" valign="top"></td><td class="left"> (usually after the message's entire header section has been</td><td> </td><td class="right"> (usually after the message's entire header section has been</td><td class="lineno" valign="top"></td></tr> 721 720 <tr><td class="lineno" valign="top"></td><td class="left"> processed). Consequently, this specification does not use ABNF rules</td><td> </td><td class="right"> processed). Consequently, this specification does not use ABNF rules</td><td class="lineno" valign="top"></td></tr> 722 <tr><td><a name="diff00 40" /></td></tr>721 <tr><td><a name="diff0039" /></td></tr> 723 722 <tr><td class="lineno" valign="top"></td><td class="lblock"> to define each <span class="delete">"Field-Name: Field Value"</span> pair, as was done in</td><td> </td><td class="rblock"> to define each <span class="insert">"field-name: field-value"</span> pair, as was done in</td><td class="lineno" valign="top"></td></tr> 724 723 <tr><td class="lineno" valign="top"></td><td class="lblock"> previous editions. Instead, this specification uses ABNF rules <span class="delete">which</span></td><td> </td><td class="rblock"> previous editions. Instead, this specification uses ABNF rules <span class="insert">that</span></td><td class="lineno" valign="top"></td></tr> … … 739 738 <tr><td class="lineno" valign="top"></td><td class="left"> whitespace (OWS); a single SP preceding the field-value is preferred</td><td> </td><td class="right"> whitespace (OWS); a single SP preceding the field-value is preferred</td><td class="lineno" valign="top"></td></tr> 740 739 <tr><td class="lineno" valign="top"></td><td class="left"> for consistent readability by humans. The field value does not</td><td> </td><td class="right"> for consistent readability by humans. The field value does not</td><td class="lineno" valign="top"></td></tr> 741 <tr><td><a name="diff004 1" /></td></tr>740 <tr><td><a name="diff0040" /></td></tr> 742 741 <tr><td class="lineno" valign="top"></td><td class="lblock"> include any leading or trailing white<span class="delete"> </span>space: OWS occurring before the</td><td> </td><td class="rblock"> include any leading or trailing whitespace: OWS occurring before the</td><td class="lineno" valign="top"></td></tr> 743 742 <tr><td class="lineno" valign="top"></td><td class="left"> first non-whitespace octet of the field value or after the last non-</td><td> </td><td class="right"> first non-whitespace octet of the field value or after the last non-</td><td class="lineno" valign="top"></td></tr> … … 763 762 <tr><td class="lineno" valign="top"></td><td class="left"> value.</td><td> </td><td class="right"> value.</td><td class="lineno" valign="top"></td></tr> 764 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> 765 <tr><td><a name="diff004 2" /></td></tr>764 <tr><td><a name="diff0041" /></td></tr> 766 765 <tr><td class="lineno" valign="top"></td><td class="lblock"> Historically, HTTP has allowed field content with text in the <span class="delete">ISO-</span></td><td> </td><td class="rblock"> Historically, HTTP has allowed field content with text in the</td><td class="lineno" valign="top"></td></tr> 767 766 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> 8859-1</span> [ISO-8859-1] charset, supporting other charsets only through</td><td> </td><td class="rblock"> <span class="insert">ISO-8859-1</span> [ISO-8859-1] charset, supporting other charsets only</td><td class="lineno" valign="top"></td></tr> … … 774 773 <tr><td class="lineno" valign="top"></td><td class="left">3.2.5. Field Limits</td><td> </td><td class="right">3.2.5. Field Limits</td><td class="lineno" valign="top"></td></tr> 775 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> 776 <tr><td><a name="diff004 3" /></td></tr>775 <tr><td><a name="diff0042" /></td></tr> 777 776 <tr><td class="lineno" valign="top"></td><td class="lblock"> HTTP does not place a pre<span class="delete">-</span>defined limit on the length of each header</td><td> </td><td class="rblock"> HTTP does not place a predefined limit on the length of each header</td><td class="lineno" valign="top"></td></tr> 778 777 <tr><td class="lineno" valign="top"></td><td class="left"> field or on the length of the header section as a whole, as described</td><td> </td><td class="right"> field or on the length of the header section as a whole, as described</td><td class="lineno" valign="top"></td></tr> 779 <tr><td><a name="diff0044" /></td></tr> 780 <tr><td class="lineno" valign="top"></td><td class="lblock"> in Section 2.5. Various ad<span class="delete">-</span>hoc limitations on individual header</td><td> </td><td class="rblock"> in Section 2.5. Various ad<span class="insert"> </span>hoc limitations on individual header</td><td class="lineno" valign="top"></td></tr> 778 <tr><td class="lineno" valign="top"></td><td class="left"> in Section 2.5. Various ad hoc limitations on individual header</td><td> </td><td class="right"> in Section 2.5. Various ad hoc limitations on individual header</td><td class="lineno" valign="top"></td></tr> 781 779 <tr><td class="lineno" valign="top"></td><td class="left"> field length are found in practice, often depending on the specific</td><td> </td><td class="right"> field length are found in practice, often depending on the specific</td><td class="lineno" valign="top"></td></tr> 782 780 <tr><td class="lineno" valign="top"></td><td class="left"> field semantics.</td><td> </td><td class="right"> field semantics.</td><td class="lineno" valign="top"></td></tr> … … 787 785 <tr><td class="lineno" valign="top"></td><td class="left"> increase the server's vulnerability to request smuggling attacks</td><td> </td><td class="right"> increase the server's vulnerability to request smuggling attacks</td><td class="lineno" valign="top"></td></tr> 788 786 <tr><td class="lineno" valign="top"></td><td class="left"> (Section 9.5).</td><td> </td><td class="right"> (Section 9.5).</td><td class="lineno" valign="top"></td></tr> 789 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>790 <tr><td class="lineno" valign="top"></td><td class="left"> A client MAY discard or truncate received header fields that are</td><td> </td><td class="right"> A client MAY discard or truncate received header fields that are</td><td class="lineno" valign="top"></td></tr>791 787 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 792 788 <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 33, line 6</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 33, line 6</em></th><td></td></tr> … … 801 797 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 802 798 <tr><td class="lineno" valign="top"></td><td class="left"> Since there is no way to distinguish a successfully completed, close-</td><td> </td><td class="right"> Since there is no way to distinguish a successfully completed, close-</td><td class="lineno" valign="top"></td></tr> 803 <tr><td><a name="diff004 5" /></td></tr>799 <tr><td><a name="diff0043" /></td></tr> 804 800 <tr><td class="lineno" valign="top"></td><td class="lblock"> delimited message from a partially<span class="delete">-</span>received message interrupted by</td><td> </td><td class="rblock"> delimited message from a partially<span class="insert"> </span>received message interrupted by</td><td class="lineno" valign="top"></td></tr> 805 801 <tr><td class="lineno" valign="top"></td><td class="left"> network failure, a server SHOULD generate encoding or length-</td><td> </td><td class="right"> network failure, a server SHOULD generate encoding or length-</td><td class="lineno" valign="top"></td></tr> … … 825 821 <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 822 <tr><td class="lineno" valign="top"></td><td class="left"> A server that receives an incomplete request message, usually due to</td><td> </td><td class="right"> A server that receives an incomplete request message, usually due to</td><td class="lineno" valign="top"></td></tr> 827 <tr><td><a name="diff004 6" /></td></tr>823 <tr><td><a name="diff0044" /></td></tr> 828 824 <tr><td class="lineno" valign="top"></td><td class="lblock"> a canceled request or a triggered time<span class="delete">-</span>out exception, MAY send an</td><td> </td><td class="rblock"> a canceled request or a triggered timeout exception, MAY send an</td><td class="lineno" valign="top"></td></tr> 829 825 <tr><td class="lineno" valign="top"></td><td class="left"> error response prior to closing the connection.</td><td> </td><td class="right"> error response prior to closing the connection.</td><td class="lineno" valign="top"></td></tr> … … 849 845 <tr><td class="lineno" valign="top"></td><td class="left"> transfer-parameter = token BWS "=" BWS ( token / quoted-string )</td><td> </td><td class="right"> transfer-parameter = token BWS "=" BWS ( token / quoted-string )</td><td class="lineno" valign="top"></td></tr> 850 846 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 851 <tr><td><a name="diff004 7" /></td></tr>847 <tr><td><a name="diff0045" /></td></tr> 852 848 <tr><td class="lineno" valign="top"></td><td class="lblock"> All transfer-coding names are <span class="delete">case-insensitive</span> and ought to be</td><td> </td><td class="rblock"> All transfer-coding names are <span class="insert">case insensitive</span> and ought to be</td><td class="lineno" valign="top"></td></tr> 853 849 <tr><td class="lineno" valign="top"></td><td class="lblock"> registered within the <span class="delete">HTTP</span> Transfer <span class="delete">Coding</span> registry, as defined in</td><td> </td><td class="rblock"> registered within the <span class="insert">"HTTP</span> Transfer <span class="insert">Coding"</span> registry, as defined in</td><td class="lineno" valign="top"></td></tr> … … 874 870 <tr><td class="lineno" valign="top"></td><td class="left">4.2.3. Gzip Coding</td><td> </td><td class="right">4.2.3. Gzip Coding</td><td class="lineno" valign="top"></td></tr> 875 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> 876 <tr><td><a name="diff004 8" /></td></tr>872 <tr><td><a name="diff0046" /></td></tr> 877 873 <tr><td class="lineno" valign="top"></td><td class="lblock"> The "gzip" coding is an LZ77 coding with a <span class="delete">32 bit CRC</span> that is</td><td> </td><td class="rblock"> The "gzip" coding is an LZ77 coding with a <span class="insert">32-bit Cyclic Redundancy</span></td><td class="lineno" valign="top"></td></tr> 878 874 <tr><td class="lineno" valign="top"></td><td class="lblock"> commonly produced by the gzip file compression program [RFC1952]. A</td><td> </td><td class="rblock"><span class="insert"> Check (CRC)</span> that is commonly produced by the gzip file compression</td><td class="lineno" valign="top"></td></tr> … … 901 897 <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 898 <tr><td class="lineno" valign="top"></td><td class="left"> A proxy MUST NOT transform the payload (Section 3.3 of [RFC7231]) of</td><td> </td><td class="right"> A proxy MUST NOT transform the payload (Section 3.3 of [RFC7231]) of</td><td class="lineno" valign="top"></td></tr> 903 <tr><td><a name="diff004 9" /></td></tr>899 <tr><td><a name="diff0047" /></td></tr> 904 900 <tr><td class="lineno" valign="top"></td><td class="lblock"> a message that contains a no-transform <span class="delete">cache-c</span>ontrol directive</td><td> </td><td class="rblock"> a message that contains a no-transform <span class="insert">Cache-C</span>ontrol directive</td><td class="lineno" valign="top"></td></tr> 905 901 <tr><td class="lineno" valign="top"></td><td class="left"> (Section 5.2 of [RFC7234]).</td><td> </td><td class="right"> (Section 5.2 of [RFC7234]).</td><td class="lineno" valign="top"></td></tr> 906 902 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 907 903 <tr><td class="lineno" valign="top"></td><td class="left"> A proxy MAY transform the payload of a message that does not contain</td><td> </td><td class="right"> A proxy MAY transform the payload of a message that does not contain</td><td class="lineno" valign="top"></td></tr> 908 <tr><td><a name="diff00 50" /></td></tr>904 <tr><td><a name="diff0048" /></td></tr> 909 905 <tr><td class="lineno" valign="top"></td><td class="lblock"> a no-transform <span class="delete">cache-c</span>ontrol directive. A proxy that transforms a</td><td> </td><td class="rblock"> a no-transform <span class="insert">Cache-C</span>ontrol directive. A proxy that transforms a</td><td class="lineno" valign="top"></td></tr> 910 906 <tr><td class="lineno" valign="top"></td><td class="left"> payload MUST add a Warning header field with the warn-code of 214</td><td> </td><td class="right"> payload MUST add a Warning header field with the warn-code of 214</td><td class="lineno" valign="top"></td></tr> … … 916 912 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 917 913 <tr><td class="lineno" valign="top"></td><td class="left"> A proxy SHOULD NOT modify header fields that provide information</td><td> </td><td class="right"> A proxy SHOULD NOT modify header fields that provide information</td><td class="lineno" valign="top"></td></tr> 918 <tr><td><a name="diff00 51" /></td></tr>914 <tr><td><a name="diff0049" /></td></tr> 919 915 <tr><td class="lineno" valign="top"></td><td class="lblock"> about the end<span class="delete"> </span>points of the communication chain, the resource state,</td><td> </td><td class="rblock"> about the endpoints of the communication chain, the resource state,</td><td class="lineno" valign="top"></td></tr> 920 916 <tr><td class="lineno" valign="top"></td><td class="left"> or the selected representation (other than the payload) unless the</td><td> </td><td class="right"> or the selected representation (other than the payload) unless the</td><td class="lineno" valign="top"></td></tr> … … 924 920 <tr><td class="lineno" valign="top"></td><td class="left">6. Connection Management</td><td> </td><td class="right">6. Connection Management</td><td class="lineno" valign="top"></td></tr> 925 921 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 926 <tr><td><a name="diff005 2" /></td></tr>922 <tr><td><a name="diff0050" /></td></tr> 927 923 <tr><td class="lineno" valign="top"></td><td class="lblock"> HTTP messaging is independent of the underlying <span class="delete">transport</span> or <span class="delete">session-</span></td><td> </td><td class="rblock"> HTTP messaging is independent of the underlying <span class="insert">transport-</span> or</td><td class="lineno" valign="top"></td></tr> 928 924 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> layer</span> connection protocol(s). HTTP only presumes a reliable</td><td> </td><td class="rblock"> <span class="insert">session-layer</span> connection protocol(s). HTTP only presumes a reliable</td><td class="lineno" valign="top"></td></tr> … … 947 943 <tr><td class="lineno" valign="top"></td><td class="left"> per server endpoint. Most servers are designed to maintain thousands</td><td> </td><td class="right"> per server endpoint. Most servers are designed to maintain thousands</td><td class="lineno" valign="top"></td></tr> 948 944 <tr><td class="lineno" valign="top"></td><td class="left"> of concurrent connections, while controlling request queues to enable</td><td> </td><td class="right"> of concurrent connections, while controlling request queues to enable</td><td class="lineno" valign="top"></td></tr> 949 <tr><td><a name="diff005 3" /></td></tr>945 <tr><td><a name="diff0051" /></td></tr> 950 946 <tr><td class="lineno" valign="top"></td><td class="lblock"> fair use and detect denial<span class="delete"> of </span>service attacks.</td><td> </td><td class="rblock"> fair use and detect denial<span class="insert">-of-</span>service attacks.</td><td class="lineno" valign="top"></td></tr> 951 947 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 971 967 <tr><td class="lineno" valign="top"></td><td class="left"> connection-option = token</td><td> </td><td class="right"> connection-option = token</td><td class="lineno" valign="top"></td></tr> 972 968 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 973 <tr><td><a name="diff005 4" /></td></tr>969 <tr><td><a name="diff0052" /></td></tr> 974 970 <tr><td class="lineno" valign="top"></td><td class="lblock"> Connection options are case<span class="delete">-</span>insensitive.</td><td> </td><td class="rblock"> Connection options are case<span class="insert"> </span>insensitive.</td><td class="lineno" valign="top"></td></tr> 975 971 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 995 991 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 996 992 <tr><td class="lineno" valign="top"></td><td class="left"> It is beyond the scope of this specification to describe how</td><td> </td><td class="right"> It is beyond the scope of this specification to describe how</td><td class="lineno" valign="top"></td></tr> 997 <tr><td><a name="diff005 5" /></td></tr>993 <tr><td><a name="diff0053" /></td></tr> 998 994 <tr><td class="lineno" valign="top"></td><td class="lblock"> connections are established via various transport or session-layer</td><td> </td><td class="rblock"> connections are established via various transport<span class="insert">-</span> or session-layer</td><td class="lineno" valign="top"></td></tr> 999 995 <tr><td class="lineno" valign="top"></td><td class="left"> protocols. Each connection applies to only one transport link.</td><td> </td><td class="right"> protocols. Each connection applies to only one transport link.</td><td class="lineno" valign="top"></td></tr> … … 1003 999 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP/1.1 defaults to the use of "persistent connections", allowing</td><td> </td><td class="right"> HTTP/1.1 defaults to the use of "persistent connections", allowing</td><td class="lineno" valign="top"></td></tr> 1004 1000 <tr><td class="lineno" valign="top"></td><td class="left"> multiple requests and responses to be carried over a single</td><td> </td><td class="right"> multiple requests and responses to be carried over a single</td><td class="lineno" valign="top"></td></tr> 1005 <tr><td><a name="diff005 6" /></td></tr>1001 <tr><td><a name="diff0054" /></td></tr> 1006 1002 <tr><td class="lineno" valign="top"></td><td class="lblock"> connection. The "close" connection<span class="delete">-</span>option is used to signal that a</td><td> </td><td class="rblock"> connection. The "close" connection<span class="insert"> </span>option is used to signal that a</td><td class="lineno" valign="top"></td></tr> 1007 1003 <tr><td class="lineno" valign="top"></td><td class="left"> connection will not persist after the current request/response. HTTP</td><td> </td><td class="right"> connection will not persist after the current request/response. HTTP</td><td class="lineno" valign="top"></td></tr> … … 1012 1008 <tr><td class="lineno" valign="top"></td><td class="left"> Connection header field (if any):</td><td> </td><td class="right"> Connection header field (if any):</td><td class="lineno" valign="top"></td></tr> 1013 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> 1014 <tr><td><a name="diff005 7" /></td></tr>1010 <tr><td><a name="diff0055" /></td></tr> 1015 1011 <tr><td class="lineno" valign="top"></td><td class="lblock"> o If the <span class="delete">close</span> connection option is present, the connection will not</td><td> </td><td class="rblock"> o If the <span class="insert">"close"</span> connection option is present, the connection will</td><td class="lineno" valign="top"></td></tr> 1016 1012 <tr><td class="lineno" valign="top"></td><td class="lblock"> persist after the current response; else,</td><td> </td><td class="rblock"> not persist after the current response; else,</td><td class="lineno" valign="top"></td></tr> … … 1027 1023 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1028 1024 <tr><td class="lineno" valign="top"></td><td class="left"> A client MAY send additional requests on a persistent connection</td><td> </td><td class="right"> A client MAY send additional requests on a persistent connection</td><td class="lineno" valign="top"></td></tr> 1029 <tr><td><a name="diff005 8" /></td></tr>1025 <tr><td><a name="diff0056" /></td></tr> 1030 1026 <tr><td class="lineno" valign="top"></td><td class="lblock"> until it sends or receives a <span class="delete">close</span> connection option or receives an</td><td> </td><td class="rblock"> until it sends or receives a <span class="insert">"close"</span> connection option or receives an</td><td class="lineno" valign="top"></td></tr> 1031 1027 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP/1.0 response without a "keep-alive" connection option.</td><td> </td><td class="right"> HTTP/1.0 response without a "keep-alive" connection option.</td><td class="lineno" valign="top"></td></tr> … … 1045 1041 <tr><td class="lineno" valign="top"></td><td class="left"> implemented by many HTTP/1.0 clients).</td><td> </td><td class="right"> implemented by many HTTP/1.0 clients).</td><td class="lineno" valign="top"></td></tr> 1046 1042 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1047 <tr><td><a name="diff005 9" /></td></tr>1043 <tr><td><a name="diff0057" /></td></tr> 1048 1044 <tr><td class="lineno" valign="top"></td><td class="lblock"> See Appendix A.1.2 for more information on backward compatibility</td><td> </td><td class="rblock"> See Appendix A.1.2 for more information on backward<span class="insert">s</span> compatibility</td><td class="lineno" valign="top"></td></tr> 1049 1045 <tr><td class="lineno" valign="top"></td><td class="left"> with HTTP/1.0 clients.</td><td> </td><td class="right"> with HTTP/1.0 clients.</td><td class="lineno" valign="top"></td></tr> … … 1069 1065 <tr><td class="lineno" valign="top"></td><td class="left"> response). A server MAY process a sequence of pipelined requests in</td><td> </td><td class="right"> response). A server MAY process a sequence of pipelined requests in</td><td class="lineno" valign="top"></td></tr> 1070 1066 <tr><td class="lineno" valign="top"></td><td class="left"> parallel if they all have safe methods (Section 4.2.1 of [RFC7231]),</td><td> </td><td class="right"> parallel if they all have safe methods (Section 4.2.1 of [RFC7231]),</td><td class="lineno" valign="top"></td></tr> 1071 <tr><td><a name="diff00 60" /></td></tr>1067 <tr><td><a name="diff0058" /></td></tr> 1072 1068 <tr><td class="lineno" valign="top"></td><td class="lblock"> but MUST send the corresponding responses in the same order that the</td><td> </td><td class="rblock"> but <span class="insert">it</span> MUST send the corresponding responses in the same order that</td><td class="lineno" valign="top"></td></tr> 1073 1069 <tr><td class="lineno" valign="top"></td><td class="lblock"> requests were received.</td><td> </td><td class="rblock"> the requests were received.</td><td class="lineno" valign="top"></td></tr> … … 1094 1090 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1095 1091 <tr><td class="lineno" valign="top"></td><td class="left"> Note that a server might reject traffic that it deems abusive or</td><td> </td><td class="right"> Note that a server might reject traffic that it deems abusive or</td><td class="lineno" valign="top"></td></tr> 1096 <tr><td><a name="diff00 61" /></td></tr>1092 <tr><td><a name="diff0059" /></td></tr> 1097 1093 <tr><td class="lineno" valign="top"></td><td class="lblock"> characteristic of a denial<span class="delete"> of </span>service attack, such as an excessive</td><td> </td><td class="rblock"> characteristic of a denial<span class="insert">-of-</span>service attack, such as an excessive</td><td class="lineno" valign="top"></td></tr> 1098 1094 <tr><td class="lineno" valign="top"></td><td class="left"> number of open connections from a single client.</td><td> </td><td class="right"> number of open connections from a single client.</td><td class="lineno" valign="top"></td></tr> 1099 1095 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1100 <tr><td><a name="diff006 2" /></td></tr>1096 <tr><td><a name="diff0060" /></td></tr> 1101 1097 <tr><td class="lineno" valign="top"></td><td class="lblock">6.5. Failures and Time<span class="delete">-</span>outs</td><td> </td><td class="rblock">6.5. Failures and Timeouts</td><td class="lineno" valign="top"></td></tr> 1102 1098 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1103 <tr><td><a name="diff006 3" /></td></tr>1099 <tr><td><a name="diff0061" /></td></tr> 1104 1100 <tr><td class="lineno" valign="top"></td><td class="lblock"> Servers will usually have some time<span class="delete">-</span>out value beyond which they will</td><td> </td><td class="rblock"> Servers will usually have some timeout value beyond which they will</td><td class="lineno" valign="top"></td></tr> 1105 1101 <tr><td class="lineno" valign="top"></td><td class="left"> no longer maintain an inactive connection. Proxy servers might make</td><td> </td><td class="right"> no longer maintain an inactive connection. Proxy servers might make</td><td class="lineno" valign="top"></td></tr> … … 1107 1103 <tr><td class="lineno" valign="top"></td><td class="left"> more connections through the same proxy server. The use of</td><td> </td><td class="right"> more connections through the same proxy server. The use of</td><td class="lineno" valign="top"></td></tr> 1108 1104 <tr><td class="lineno" valign="top"></td><td class="left"> persistent connections places no requirements on the length (or</td><td> </td><td class="right"> persistent connections places no requirements on the length (or</td><td class="lineno" valign="top"></td></tr> 1109 <tr><td><a name="diff006 4" /></td></tr>1105 <tr><td><a name="diff0062" /></td></tr> 1110 1106 <tr><td class="lineno" valign="top"></td><td class="lblock"> existence) of this time<span class="delete">-</span>out for either the client or the server.</td><td> </td><td class="rblock"> existence) of this timeout for either the client or the server.</td><td class="lineno" valign="top"></td></tr> 1111 1107 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1112 <tr><td><a name="diff006 5" /></td></tr>1108 <tr><td><a name="diff0063" /></td></tr> 1113 1109 <tr><td class="lineno" valign="top"></td><td class="lblock"> A client or server that wishes to time<span class="delete">-</span>out SHOULD issue a graceful</td><td> </td><td class="rblock"> A client or server that wishes to time<span class="insert"> </span>out SHOULD issue a graceful</td><td class="lineno" valign="top"></td></tr> 1114 1110 <tr><td class="lineno" valign="top"></td><td class="left"> close on the connection. Implementations SHOULD constantly monitor</td><td> </td><td class="right"> close on the connection. Implementations SHOULD constantly monitor</td><td class="lineno" valign="top"></td></tr> … … 1125 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> 1126 1122 <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> 1127 <tr><td><a name="diff006 6" /></td></tr>1123 <tr><td><a name="diff0064" /></td></tr> 1128 1124 <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> 1129 1125 <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> … … 1138 1134 <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> 1139 1135 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1140 <tr><td><a name="diff006 7" /></td></tr>1136 <tr><td><a name="diff0065" /></td></tr> 1141 1137 <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> 1142 1138 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1145 1141 <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> 1146 1142 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1147 <tr><td><a name="diff006 8" /></td></tr>1143 <tr><td><a name="diff0066" /></td></tr> 1148 1144 <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> 1149 1145 <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> … … 1151 1147 <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> 1152 1148 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1153 <tr><td><a name="diff006 9" /></td></tr>1149 <tr><td><a name="diff0067" /></td></tr> 1154 1150 <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> 1155 1151 <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> … … 1159 1155 <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> 1160 1156 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1161 <tr><td><a name="diff00 70" /></td></tr>1157 <tr><td><a name="diff0068" /></td></tr> 1162 1158 <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> 1163 1159 <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> … … 1165 1161 <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> 1166 1162 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1167 <tr><td><a name="diff00 71" /></td></tr>1163 <tr><td><a name="diff0069" /></td></tr> 1168 1164 <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> 1169 1165 <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> … … 1175 1171 <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> 1176 1172 <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> 1177 <tr><td><a name="diff007 2" /></td></tr>1173 <tr><td><a name="diff0070" /></td></tr> 1178 1174 <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> 1179 1175 <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> … … 1199 1195 <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> 1200 1196 <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> 1201 <tr><td><a name="diff007 3" /></td></tr>1197 <tr><td><a name="diff0071" /></td></tr> 1202 1198 <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> 1203 1199 <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> … … 1213 1209 <tr><td class="lineno" valign="top"></td><td class="left"> GET on the target resource. This allows a connection to be upgraded</td><td> </td><td class="right"> GET on the target resource. This allows a connection to be upgraded</td><td class="lineno" valign="top"></td></tr> 1214 1210 <tr><td class="lineno" valign="top"></td><td class="left"> to protocols with the same semantics as HTTP without the latency cost</td><td> </td><td class="right"> to protocols with the same semantics as HTTP without the latency cost</td><td class="lineno" valign="top"></td></tr> 1215 <tr><td><a name="diff007 4" /></td></tr>1211 <tr><td><a name="diff0072" /></td></tr> 1216 1212 <tr><td class="lineno" valign="top"></td><td class="lblock"> of an additional round<span class="delete">-</span>trip. A server MUST NOT switch protocols</td><td> </td><td class="rblock"> of an additional round<span class="insert"> </span>trip. A server MUST NOT switch protocols</td><td class="lineno" valign="top"></td></tr> 1217 1213 <tr><td class="lineno" valign="top"></td><td class="left"> unless the received message semantics can be honored by the new</td><td> </td><td class="right"> unless the received message semantics can be honored by the new</td><td class="lineno" valign="top"></td></tr> … … 1237 1233 <tr><td class="lineno" valign="top"></td><td class="left"> until it has completely sent the request message (i.e., the client</td><td> </td><td class="right"> until it has completely sent the request message (i.e., the client</td><td class="lineno" valign="top"></td></tr> 1238 1234 <tr><td class="lineno" valign="top"></td><td class="left"> can't change the protocol it is sending in the middle of a message).</td><td> </td><td class="right"> can't change the protocol it is sending in the middle of a message).</td><td class="lineno" valign="top"></td></tr> 1239 <tr><td><a name="diff007 5" /></td></tr>1235 <tr><td><a name="diff0073" /></td></tr> 1240 1236 <tr><td class="lineno" valign="top"></td><td class="lblock"> If a server receives both Upgrade and an Expect header field with the</td><td> </td><td class="rblock"> If a server receives both <span class="insert">an</span> Upgrade and an Expect header field with</td><td class="lineno" valign="top"></td></tr> 1241 1237 <tr><td class="lineno" valign="top"></td><td class="lblock"> "100-continue" expectation (Section 5.1.1 of [RFC7231]), the server</td><td> </td><td class="rblock"> the "100-continue" expectation (Section 5.1.1 of [RFC7231]), the</td><td class="lineno" valign="top"></td></tr> … … 1264 1260 <tr><td class="lineno" valign="top"></td><td class="left"> ignore a reasonable number of empty list elements: enough to handle</td><td> </td><td class="right"> ignore a reasonable number of empty list elements: enough to handle</td><td class="lineno" valign="top"></td></tr> 1265 1261 <tr><td class="lineno" valign="top"></td><td class="left"> common mistakes by senders that merge values, but not so much that</td><td> </td><td class="right"> common mistakes by senders that merge values, but not so much that</td><td class="lineno" valign="top"></td></tr> 1266 <tr><td><a name="diff007 6" /></td></tr>1262 <tr><td><a name="diff0074" /></td></tr> 1267 1263 <tr><td class="lineno" valign="top"></td><td class="lblock"> they could be used as a denial<span class="delete"> of </span>service mechanism. In other words,</td><td> </td><td class="rblock"> they could be used as a denial<span class="insert">-of-</span>service mechanism. In other words,</td><td class="lineno" valign="top"></td></tr> 1268 1264 <tr><td class="lineno" valign="top"></td><td class="left"> a recipient MUST accept lists that satisfy the following syntax:</td><td> </td><td class="right"> a recipient MUST accept lists that satisfy the following syntax:</td><td class="lineno" valign="top"></td></tr> … … 1278 1274 <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> 1279 1275 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1280 <tr><td><a name="diff007 7" /></td></tr>1276 <tr><td><a name="diff0075" /></td></tr> 1281 1277 <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> 1282 1278 <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> … … 1300 1296 <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> 1301 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> 1302 <tr><td><a name="diff007 8" /></td></tr>1298 <tr><td><a name="diff0076" /></td></tr> 1303 1299 <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> 1304 1300 <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> 1305 1301 <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> 1306 1302 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1307 <tr><td><a name="diff007 9" /></td></tr>1303 <tr><td><a name="diff0077" /></td></tr> 1308 1304 <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> 1309 1305 <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> … … 1323 1319 <tr><td class="lineno" valign="top"></td><td class="left"> +-------------------+----------+----------+---------------+</td><td> </td><td class="right"> +-------------------+----------+----------+---------------+</td><td class="lineno" valign="top"></td></tr> 1324 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> 1325 <tr><td><a name="diff00 80" /></td></tr>1321 <tr><td><a name="diff0078" /></td></tr> 1326 1322 <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> 1327 1323 <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> … … 1343 1339 <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> 1344 1340 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1345 <tr><td><a name="diff00 81" /></td></tr>1341 <tr><td><a name="diff0079" /></td></tr> 1346 1342 <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> 1347 1343 <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> … … 1361 1357 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1362 1358 <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> 1363 <tr><td><a name="diff008 2" /></td></tr>1359 <tr><td><a name="diff0080" /></td></tr> 1364 1360 <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> 1365 1361 <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> … … 1385 1381 <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> 1386 1382 <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 <tr><td><a name="diff008 3" /></td></tr>1383 <tr><td><a name="diff0081" /></td></tr> 1388 1384 <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> 1389 1385 <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> … … 1410 1406 <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> 1411 1407 <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> 1412 <tr><td><a name="diff008 4" /></td></tr>1408 <tr><td><a name="diff0082" /></td></tr> 1413 1409 <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> 1414 1410 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1434 1430 <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> 1435 1431 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1436 <tr><td><a name="diff008 5" /></td></tr>1432 <tr><td><a name="diff0083" /></td></tr> 1437 1433 <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> 1438 1434 <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> … … 1448 1444 <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> 1449 1445 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1450 <tr><td><a name="diff008 6" /></td></tr>1446 <tr><td><a name="diff0084" /></td></tr> 1451 1447 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Transfer <span class="delete">Coding Registry</span> defines the <span class="delete">name space</span> for transfer</td><td> </td><td class="rblock"> The <span class="insert">"HTTP</span> Transfer <span class="insert">Coding" registry</span> defines the <span class="insert">namespace</span> for</td><td class="lineno" valign="top"></td></tr> 1452 1448 <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> … … 1467 1463 <tr><td class="lineno" valign="top"></td><td class="left"> codings defined in Section 4.2.</td><td> </td><td class="right"> codings defined in Section 4.2.</td><td class="lineno" valign="top"></td></tr> 1468 1464 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1469 <tr><td><a name="diff008 7" /></td></tr>1465 <tr><td><a name="diff0085" /></td></tr> 1470 1466 <tr><td class="lineno" valign="top"></td><td class="lblock"> Values to be added to this <span class="delete">name space</span> require IETF Review (see</td><td> </td><td class="rblock"> Values to be added to this <span class="insert">namespace</span> require IETF Review (see Section</td><td class="lineno" valign="top"></td></tr> 1471 1467 <tr><td class="lineno" valign="top"></td><td class="lblock"> Section 4.1 of [RFC5226]), and MUST conform to the purpose of</td><td> </td><td class="rblock"> 4.1 of [RFC5226]), and MUST conform to the purpose of transfer coding</td><td class="lineno" valign="top"></td></tr> … … 1477 1473 <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> 1478 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> 1479 <tr><td><a name="diff008 8" /></td></tr>1475 <tr><td><a name="diff0086" /></td></tr> 1480 1476 <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> 1481 1477 <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> … … 1496 1492 <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> 1497 1493 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1498 <tr><td><a name="diff008 9" /></td></tr>1494 <tr><td><a name="diff0087" /></td></tr> 1499 1495 <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> 1500 1496 <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> 1501 1497 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1502 <tr><td><a name="diff00 90" /></td></tr>1498 <tr><td><a name="diff0088" /></td></tr> 1503 1499 <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> 1504 1500 <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> … … 1518 1514 <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> 1519 1515 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1520 <tr><td><a name="diff00 91" /></td></tr>1516 <tr><td><a name="diff0089" /></td></tr> 1521 1517 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Upgrade Token <span class="delete">Registry</span> defines the <span class="delete">name space</span> for <span class="delete">protocol-</span></td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Upgrade Token <span class="insert">Registry"</span></td><td class="lineno" valign="top"></td></tr> 1522 1518 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> name</span> tokens used to identify protocols in the Upgrade header field.</td><td> </td><td class="rblock"> defines the <span class="insert">namespace</span> for <span class="insert">protocol-name</span> tokens used to identify</td><td class="lineno" valign="top"></td></tr> … … 1544 1540 <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> 1545 1541 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1546 <tr><td><a name="diff009 2" /></td></tr>1542 <tr><td><a name="diff0090" /></td></tr> 1547 1543 <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> 1548 1544 <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> … … 1569 1565 <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> 1570 1566 <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> 1571 <tr><td><a name="diff009 3" /></td></tr>1567 <tr><td><a name="diff0091" /></td></tr> 1572 1568 <tr><td class="lineno" valign="top"></td><td class="lblock"> mappings; <span class="delete">DNSSEC</span> ([RFC4033]) is one way to improve authenticity.</td><td> </td><td class="rblock"> mappings; <span class="insert">DNS Security Extensions (DNSSEC)</span> ([RFC4033]) is one way to</td><td class="lineno" valign="top"></td></tr> 1573 1569 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"> improve authenticity.</td><td class="lineno" valign="top"></td></tr> … … 1587 1583 <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> 1588 1584 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1589 <tr><td><a name="diff009 4" /></td></tr>1585 <tr><td><a name="diff0092" /></td></tr> 1590 1586 <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> 1591 1587 <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> … … 1612 1608 <tr><td class="lineno" valign="top"></td><td class="left"> and body chunks. Failure to limit such processing can result in</td><td> </td><td class="right"> and body chunks. Failure to limit such processing can result in</td><td class="lineno" valign="top"></td></tr> 1613 1609 <tr><td class="lineno" valign="top"></td><td class="left"> buffer overflows, arithmetic overflows, or increased vulnerability to</td><td> </td><td class="right"> buffer overflows, arithmetic overflows, or increased vulnerability to</td><td class="lineno" valign="top"></td></tr> 1614 <tr><td><a name="diff009 5" /></td></tr>1610 <tr><td><a name="diff0093" /></td></tr> 1615 1611 <tr><td class="lineno" valign="top"></td><td class="lblock"> denial<span class="delete"> of </span>service attacks.</td><td> </td><td class="rblock"> denial<span class="insert">-of-</span>service attacks.</td><td class="lineno" valign="top"></td></tr> 1616 1612 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1636 1632 <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> 1637 1633 <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> 1638 <tr><td><a name="diff009 6" /></td></tr>1634 <tr><td><a name="diff0094" /></td></tr> 1639 1635 <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> 1640 1636 <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> … … 1660 1656 <tr><td class="lineno" valign="top"></td><td class="left"> securely stored and appropriate guidelines followed for its analysis.</td><td> </td><td class="right"> securely stored and appropriate guidelines followed for its analysis.</td><td class="lineno" valign="top"></td></tr> 1661 1657 <tr><td class="lineno" valign="top"></td><td class="left"> Anonymization of personal information within individual entries</td><td> </td><td class="right"> Anonymization of personal information within individual entries</td><td class="lineno" valign="top"></td></tr> 1662 <tr><td><a name="diff009 7" /></td></tr>1658 <tr><td><a name="diff0095" /></td></tr> 1663 1659 <tr><td class="lineno" valign="top"></td><td class="lblock"> helps, but is generally not sufficient to prevent real log traces</td><td> </td><td class="rblock"> helps, but i<span class="insert">t i</span>s generally not sufficient to prevent real log traces</td><td class="lineno" valign="top"></td></tr> 1664 1660 <tr><td class="lineno" valign="top"></td><td class="left"> from being re-identified based on correlation with other access</td><td> </td><td class="right"> from being re-identified based on correlation with other access</td><td class="lineno" valign="top"></td></tr> … … 1684 1680 <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> 1685 1681 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1686 <tr><td><a name="diff009 8" /></td></tr>1682 <tr><td><a name="diff0096" /></td></tr> 1687 1683 <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> 1688 1684 <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> … … 1710 1706 <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> 1711 1707 <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> 1712 <tr><td><a name="diff009 9" /></td></tr>1708 <tr><td><a name="diff0097" /></td></tr> 1713 1709 <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> 1714 1710 <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> … … 1716 1712 <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> 1717 1713 <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> 1718 <tr><td><a name="diff0 100" /></td></tr>1714 <tr><td><a name="diff0098" /></td></tr> 1719 1715 <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> 1720 1716 <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> … … 1722 1718 <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> 1723 1719 <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> 1724 <tr><td><a name="diff0 101" /></td></tr>1720 <tr><td><a name="diff0099" /></td></tr> 1725 1721 <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> 1726 1722 <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> … … 1728 1724 <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> 1729 1725 <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> 1730 <tr><td><a name="diff010 2" /></td></tr>1726 <tr><td><a name="diff0100" /></td></tr> 1731 1727 <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> 1732 1728 <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> … … 1734 1730 <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> 1735 1731 <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> 1736 <tr><td><a name="diff010 3" /></td></tr>1732 <tr><td><a name="diff0101" /></td></tr> 1737 1733 <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> 1738 1734 <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> … … 1744 1740 <tr><td class="lineno" valign="top"></td><td class="left"> Interchange", ANSI X3.4, 1986.</td><td> </td><td class="right"> Interchange", ANSI X3.4, 1986.</td><td class="lineno" valign="top"></td></tr> 1745 1741 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1746 <tr><td><a name="diff010 4" /></td></tr>1742 <tr><td><a name="diff0102" /></td></tr> 1747 1743 <tr><td class="lineno" valign="top"></td><td class="lblock"> [Welch] Welch, T., "A Technique for High<span class="delete"> </span>Performance Data</td><td> </td><td class="rblock"> [Welch] Welch, T., "A Technique for High<span class="insert">-</span>Performance Data</td><td class="lineno" valign="top"></td></tr> 1748 1744 <tr><td class="lineno" valign="top"></td><td class="left"> Compression", IEEE Computer 17(6), June 1984.</td><td> </td><td class="right"> Compression", IEEE Computer 17(6), June 1984.</td><td class="lineno" valign="top"></td></tr> … … 1768 1764 <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> 1769 1765 <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> 1770 <tr><td><a name="diff010 5" /></td></tr>1766 <tr><td><a name="diff0103" /></td></tr> 1771 1767 <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> 1772 1768 <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> … … 1777 1773 <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> 1778 1774 <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> 1779 <tr><td><a name="diff010 6" /></td></tr>1775 <tr><td><a name="diff0104" /></td></tr> 1780 1776 <tr><td class="lineno" valign="top"></td><td class="lblock"> or only sent when communicating with a party advertising conformance</td><td> </td><td class="rblock"> or only <span class="insert">be</span> sent when communicating with a party advertising</td><td class="lineno" valign="top"></td></tr> 1781 1777 <tr><td class="lineno" valign="top"></td><td class="lblock"> with HTTP/1.1.</td><td> </td><td class="rblock"> conformance with HTTP/1.1.</td><td class="lineno" valign="top"></td></tr> … … 1802 1798 <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> 1803 1799 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1804 <tr><td><a name="diff010 7" /></td></tr>1800 <tr><td><a name="diff0105" /></td></tr> 1805 1801 <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> 1806 1802 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1826 1822 <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> 1827 1823 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1828 <tr><td><a name="diff010 8" /></td></tr>1824 <tr><td><a name="diff0106" /></td></tr> 1829 1825 <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> 1830 1826 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1831 <tr><td><a name="diff010 9" /></td></tr>1827 <tr><td><a name="diff0107" /></td></tr> 1832 1828 <tr><td class="lineno" valign="top"></td><td class="lblock"> The HTTP-version ABNF production has been clarified to be <span class="delete">case-</span></td><td> </td><td class="rblock"> The HTTP-version ABNF production has been clarified to be <span class="insert">case</span></td><td class="lineno" valign="top"></td></tr> 1833 1829 <tr><td class="lineno" valign="top"></td><td class="lblock"> sensitive. Additionally, version numbers <span class="delete">has</span> been restricted to</td><td> </td><td class="rblock"> sensitive. Additionally, version numbers <span class="insert">have</span> been restricted to</td><td class="lineno" valign="top"></td></tr> 1834 1830 <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> 1835 <tr><td><a name="diff01 10" /></td></tr>1831 <tr><td><a name="diff0108" /></td></tr> 1836 1832 <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> 1837 1833 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1838 1834 <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> 1839 1835 <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> 1840 <tr><td><a name="diff01 11" /></td></tr>1836 <tr><td><a name="diff0109" /></td></tr> 1841 1837 <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> 1842 1838 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1843 1839 <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> 1844 <tr><td><a name="diff011 2" /></td></tr>1840 <tr><td><a name="diff0110" /></td></tr> 1845 1841 <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> 1846 1842 <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> … … 1850 1846 <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> 1851 1847 <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> 1852 <tr><td><a name="diff011 3" /></td></tr>1848 <tr><td><a name="diff0111" /></td></tr> 1853 1849 <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> 1854 1850 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1855 1851 <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> 1856 1852 <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> 1857 <tr><td><a name="diff011 4" /></td></tr>1853 <tr><td><a name="diff0112" /></td></tr> 1858 1854 <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> 1859 1855 <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> … … 1861 1857 <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> 1862 1858 <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> 1863 <tr><td><a name="diff011 5" /></td></tr>1859 <tr><td><a name="diff0113" /></td></tr> 1864 1860 <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> 1865 1861 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1866 1862 <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> 1867 <tr><td><a name="diff011 6" /></td></tr>1863 <tr><td><a name="diff0114" /></td></tr> 1868 1864 <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> 1869 1865 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"> </td><td class="lineno" valign="top"></td></tr> … … 1871 1867 <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> 1872 1868 <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> 1873 <tr><td><a name="diff011 7" /></td></tr>1869 <tr><td><a name="diff0115" /></td></tr> 1874 1870 <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> 1875 1871 <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> … … 1877 1873 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1878 1874 <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> 1879 <tr><td><a name="diff011 8" /></td></tr>1875 <tr><td><a name="diff0116" /></td></tr> 1880 1876 <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> 1881 1877 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1885 1881 <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> 1886 1882 <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> 1887 <tr><td><a name="diff011 9" /></td></tr>1883 <tr><td><a name="diff0117" /></td></tr> 1888 1884 <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> 1889 1885 <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> 1890 1886 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1891 <tr><td><a name="diff01 20" /></td></tr>1887 <tr><td><a name="diff0118" /></td></tr> 1892 1888 <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> 1893 1889 <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> 1894 1890 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1895 1891 <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> 1896 <tr><td><a name="diff01 21" /></td></tr>1892 <tr><td><a name="diff0119" /></td></tr> 1897 1893 <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> 1898 1894 <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> 1899 1895 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1900 <tr><td><a name="diff012 2" /></td></tr>1896 <tr><td><a name="diff0120" /></td></tr> 1901 1897 <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> 1902 1898 <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> … … 1904 1900 <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> 1905 1901 <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> 1906 <tr><td><a name="diff012 3" /></td></tr>1902 <tr><td><a name="diff0121" /></td></tr> 1907 1903 <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> 1908 1904 <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> 1909 1905 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1910 <tr><td><a name="diff012 4" /></td></tr>1906 <tr><td><a name="diff0122" /></td></tr> 1911 1907 <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> 1912 1908 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1913 <tr><td><a name="diff012 5" /></td></tr>1909 <tr><td><a name="diff0123" /></td></tr> 1914 1910 <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> 1915 1911 <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> … … 1918 1914 <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> 1919 1915 <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> 1920 <tr><td><a name="diff012 6" /></td></tr>1916 <tr><td><a name="diff0124" /></td></tr> 1921 1917 <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> 1922 1918 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1926 1922 <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> 1927 1923 <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> 1928 <tr><td><a name="diff012 7" /></td></tr>1924 <tr><td><a name="diff0125" /></td></tr> 1929 1925 <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> 1930 1926 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1931 1927 <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> 1932 1928 <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> 1929 <tr><td><a name="diff0126" /></td></tr> 1930 <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> 1931 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1932 <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> 1933 <tr><td><a name="diff0127" /></td></tr> 1934 <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> 1935 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1936 <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> 1933 1937 <tr><td><a name="diff0128" /></td></tr> 1934 <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> 1935 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1936 <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> 1938 <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> 1939 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1937 1940 <tr><td><a name="diff0129" /></td></tr> 1938 <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>1939 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1940 <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>1941 <tr><td><a name="diff0130" /></td></tr>1942 <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>1943 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1944 <tr><td><a name="diff0131" /></td></tr>1945 1941 <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> 1946 1942 <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> 1947 1943 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1948 <tr><td><a name="diff013 2" /></td></tr>1944 <tr><td><a name="diff0130" /></td></tr> 1949 1945 <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> 1950 1946 <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> … … 1952 1948 <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> 1953 1949 <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> 1954 <tr><td><a name="diff013 3" /></td></tr>1950 <tr><td><a name="diff0131" /></td></tr> 1955 1951 <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> 1956 1952 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1976 1972 <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> 1977 1973 <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> 1978 <tr><td><a name="diff013 4" /></td></tr>1974 <tr><td><a name="diff0132" /></td></tr> 1979 1975 <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> 1980 1976 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 2000 1996 <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> 2001 1997 <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> 2002 <tr><td><a name="diff013 5" /></td></tr>1998 <tr><td><a name="diff0133" /></td></tr> 2003 1999 <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> 2004 2000 <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> 2005 <tr><td><a name="diff013 6" /></td></tr>2001 <tr><td><a name="diff0134" /></td></tr> 2006 2002 <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> 2007 2003 <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> … … 2027 2023 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 2028 2024 <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> 2029 <tr><td><a name="diff013 7" /></td></tr>2025 <tr><td><a name="diff0135" /></td></tr> 2030 2026 <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> 2031 2027 <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> … … 2046 2042 <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> 2047 2043 <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> 2048 <tr><td><a name="diff013 8" /></td></tr>2044 <tr><td><a name="diff0136" /></td></tr> 2049 2045 <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> 2050 2046 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 2070 2066 <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> 2071 2067 <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> 2072 <tr><td><a name="diff013 9" /></td></tr>2068 <tr><td><a name="diff0137" /></td></tr> 2073 2069 <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> 2074 2070 <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> … … 2084 2080 2085 2081 <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr> 2086 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 13 9change blocks. </a></th></tr>2087 <tr class="stats"><td></td><th><i>23 5 lines changed or deleted</i></th><th><i> </i></th><th><i>214lines changed or added</i></th><td></td></tr>2082 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 137 change blocks. </a></th></tr> 2083 <tr class="stats"><td></td><th><i>233 lines changed or deleted</i></th><th><i> </i></th><th><i>212 lines changed or added</i></th><td></td></tr> 2088 2084 <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> 2089 2085 </table> -
draft-ietf-httpbis/latest/p1-messaging.html
r2639 r2640 1262 1262 <p id="rfc.section.3.1.1.p.9">HTTP does not place a pre-defined limit on the length of a request-line, as described in <a href="#conformance" title="Conformance and Error Handling">Section 2.5</a>. A server that receives a method longer than any that it implements <em class="bcp14">SHOULD</em> respond with a <a href="p2-semantics.html#status.501" class="smpl">501 (Not Implemented)</a> status code. A server that receives a request-target longer than any URI it wishes to parse <em class="bcp14">MUST</em> respond with a <a href="p2-semantics.html#status.414" class="smpl">414 (URI Too Long)</a> status code (see <a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 6.5.12</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>). 1263 1263 </p> 1264 <p id="rfc.section.3.1.1.p.10">Various ad -hoc limitations on request-line length are found in practice. It is <em class="bcp14">RECOMMENDED</em> that all HTTP senders and recipients support, at a minimum, request-line lengths of 8000 octets.1264 <p id="rfc.section.3.1.1.p.10">Various ad hoc limitations on request-line length are found in practice. It is <em class="bcp14">RECOMMENDED</em> that all HTTP senders and recipients support, at a minimum, request-line lengths of 8000 octets. 1265 1265 </p> 1266 1266 </div> … … 1402 1402 <h3 id="rfc.section.3.2.5"><a href="#rfc.section.3.2.5">3.2.5</a> <a href="#field.limits">Field Limits</a></h3> 1403 1403 <p id="rfc.section.3.2.5.p.1">HTTP does not place a pre-defined limit on the length of each header field or on the length of the header section as a whole, 1404 as described in <a href="#conformance" title="Conformance and Error Handling">Section 2.5</a>. Various ad -hoc limitations on individual header field length are found in practice, often depending on the specific field1404 as described in <a href="#conformance" title="Conformance and Error Handling">Section 2.5</a>. Various ad hoc limitations on individual header field length are found in practice, often depending on the specific field 1405 1405 semantics. 1406 1406 </p> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2639 r2640 1165 1165 </t> 1166 1166 <t> 1167 Various ad -hoc limitations on request-line length are found in practice.1167 Various ad hoc limitations on request-line length are found in practice. 1168 1168 It is &RECOMMENDED; that all HTTP senders and recipients support, at a 1169 1169 minimum, request-line lengths of 8000 octets. … … 1432 1432 HTTP does not place a pre-defined limit on the length of each header field 1433 1433 or on the length of the header section as a whole, as described in 1434 <xref target="conformance"/>. Various ad -hoc limitations on individual1434 <xref target="conformance"/>. Various ad hoc limitations on individual 1435 1435 header field length are found in practice, often depending on the specific 1436 1436 field semantics.
Note: See TracChangeset
for help on using the changeset viewer.