Changeset 2642
- Timestamp:
- 06/05/14 13:27:05 (7 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/auth48/p1-messaging.unpg.txt
r2641 r2642 174 174 175 175 6.4. Concurrency . . . . . . . . . . . . . . . . . . . . . . . 54 176 6.5. Failures and Time -outs. . . . . . . . . . . . . . . . . . 54176 6.5. Failures and Timeouts . . . . . . . . . . . . . . . . . . 54 177 177 6.6. Tear-down . . . . . . . . . . . . . . . . . . . . . . . . 55 178 178 6.7. Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . 56 … … 1864 1864 1865 1865 A server that receives an incomplete request message, usually due to 1866 a canceled request or a triggered time -out exception, MAY send an1866 a canceled request or a triggered timeout exception, MAY send an 1867 1867 error response prior to closing the connection. 1868 1868 … … 3062 3062 number of open connections from a single client. 3063 3063 3064 6.5. Failures and Time -outs3065 3066 Servers will usually have some time -out value beyond which they will3064 6.5. Failures and Timeouts 3065 3066 Servers will usually have some timeout value beyond which they will 3067 3067 no longer maintain an inactive connection. Proxy servers might make 3068 3068 this a higher value since it is likely that the client will be making 3069 3069 more connections through the same proxy server. The use of 3070 3070 persistent connections places no requirements on the length (or 3071 existence) of this time -out for either the client or the server.3071 existence) of this timeout for either the client or the server. 3072 3072 3073 3073 … … 3080 3080 3081 3081 3082 A client or server that wishes to time -out SHOULD issue a graceful3082 A client or server that wishes to time out SHOULD issue a graceful 3083 3083 close on the connection. Implementations SHOULD constantly monitor 3084 3084 open connections for a received closure signal and respond to it as -
draft-ietf-httpbis/latest/auth48/rfc7230.abdiff.txt
r2641 r2642 169 169 170 170 6.4. Concurrency . . . . . . . . . . . . . . . . . . . . . . . 54 171 6.5. Failures and Time -outs. . . . . . . . . . . . . . . . . . 54171 6.5. Failures and Timeouts . . . . . . . . . . . . . . . . . . 54 172 172 6.6. Tear-down . . . . . . . . . . . . . . . . . . . . . . . . 55 173 173 6.7. Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . 56 … … 928 928 929 929 930 Section 3.4., paragraph 1:931 OLD:932 933 A server that receives an incomplete request message, usually due to934 a canceled request or a triggered time-out exception, MAY send an935 error response prior to closing the connection.936 937 NEW:938 939 A server that receives an incomplete request message, usually due to940 a canceled request or a triggered timeout exception, MAY send an941 error response prior to closing the connection.942 943 944 930 Section 4., paragraph 5: 945 931 OLD: … … 1171 1157 1172 1158 1173 Section 6.4., paragraph 5: 1174 OLD: 1175 1176 6.5. Failures and Time-outs 1177 1178 NEW: 1179 1180 6.5. Failures and Timeouts 1181 1182 1183 Section 6.4., paragraph 6: 1184 OLD: 1185 1186 Servers will usually have some time-out value beyond which they will 1187 no longer maintain an inactive connection. Proxy servers might make 1188 this a higher value since it is likely that the client will be making 1189 more connections through the same proxy server. The use of 1190 persistent connections places no requirements on the length (or 1191 existence) of this time-out for either the client or the server. 1192 1193 NEW: 1194 1195 Servers will usually have some timeout value beyond which they will 1196 no longer maintain an inactive connection. Proxy servers might make 1197 this a higher value since it is likely that the client will be making 1198 more connections through the same proxy server. The use of 1199 persistent connections places no requirements on the length (or 1200 existence) of this timeout for either the client or the server. 1201 1202 1203 Section 6.4., paragraph 7: 1204 OLD: 1205 1206 A client or server that wishes to time-out SHOULD issue a graceful 1207 close on the connection. Implementations SHOULD constantly monitor 1208 open connections for a received closure signal and respond to it as 1209 appropriate, since prompt closure of both sides of a connection 1210 enables allocated system resources to be reclaimed. 1211 1212 NEW: 1213 1214 A client or server that wishes to time out SHOULD issue a graceful 1215 close on the connection. Implementations SHOULD constantly monitor 1216 open connections for a received closure signal and respond to it as 1217 appropriate, since prompt closure of both sides of a connection 1218 enables allocated system resources to be reclaimed. 1219 1220 1221 Section 6.4., paragraph 9: 1159 Section 6.5., paragraph 4: 1222 1160 OLD: 1223 1161 … … 1237 1175 1238 1176 1239 Section 6. 4., paragraph 11:1177 Section 6.5., paragraph 6: 1240 1178 OLD: 1241 1179 … … 1247 1185 1248 1186 1249 Section 6. 4., paragraph 13:1187 Section 6.5., paragraph 8: 1250 1188 OLD: 1251 1189 … … 1263 1201 1264 1202 1265 Section 6. 4., paragraph 14:1203 Section 6.5., paragraph 9: 1266 1204 OLD: 1267 1205 … … 1283 1221 1284 1222 1285 Section 6. 4., paragraph 15:1223 Section 6.5., paragraph 10: 1286 1224 OLD: 1287 1225 … … 1299 1237 1300 1238 1301 Section 6. 4., paragraph 16:1239 Section 6.5., paragraph 11: 1302 1240 OLD: 1303 1241 … … 1317 1255 1318 1256 1319 Section 6. 4., paragraph 17:1257 Section 6.5., paragraph 12: 1320 1258 OLD: 1321 1259 -
draft-ietf-httpbis/latest/auth48/rfc7230.diff.html
r2641 r2642 124 124 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> 125 125 <tr><td class="lineno" valign="top"></td><td class="left"> 6.4. Concurrency . . . . . . . . . . . . . . . . . . . . . . . 54</td><td> </td><td class="right"> 6.4. Concurrency . . . . . . . . . . . . . . . . . . . . . . . 54</td><td class="lineno" valign="top"></td></tr> 126 <tr><td class="lineno" valign="top"></td><td class="left"> 6.5. Failures and Timeouts . . . . . . . . . . . . . . . . . . 54</td><td> </td><td class="right"> 6.5. Failures and Timeouts . . . . . . . . . . . . . . . . . . 54</td><td class="lineno" valign="top"></td></tr> 126 127 <tr><td><a name="diff0009" /></td></tr> 127 <tr><td class="lineno" valign="top"></td><td class="lblock"> 6.5. Failures and <span class="delete">Time-outs</span> . . . . . . . . . . . . . . . . . . 54</td><td> </td><td class="rblock"> 6.5. Failures and <span class="insert">Timeouts</span> . . . . . . . . . . . . . . . . . . 54</td><td class="lineno" valign="top"></td></tr> 128 <tr><td class="lineno" valign="top"></td><td class="lblock"> 6.6. <span class="delete">Tear-down</span> . . . . . . . . . . . . . . . . . . . . . . . . 55</td><td> </td><td class="rblock"> 6.6. <span class="insert">Teardown .</span> . . . . . . . . . . . . . . . . . . . . . . . . 55</td><td class="lineno" valign="top"></td></tr> 128 <tr><td class="lineno" valign="top"></td><td class="lblock"> 6.6. Tear<span class="delete">-down </span> . . . . . . . . . . . . . . . . . . . . . . . . 55</td><td> </td><td class="rblock"> 6.6. Tear<span class="insert">down .</span> . . . . . . . . . . . . . . . . . . . . . . . . 55</td><td class="lineno" valign="top"></td></tr> 129 129 <tr><td class="lineno" valign="top"></td><td class="left"> 6.7. Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . 56</td><td> </td><td class="right"> 6.7. Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . 56</td><td class="lineno" valign="top"></td></tr> 130 130 <tr><td class="lineno" valign="top"></td><td class="left"> 7. ABNF List Extension: #rule . . . . . . . . . . . . . . . . . . 58</td><td> </td><td class="right"> 7. ABNF List Extension: #rule . . . . . . . . . . . . . . . . . . 58</td><td class="lineno" valign="top"></td></tr> … … 790 790 <tr><td class="lineno" valign="top"></td><td class="left"> valid Content-Length header field if the message body length is known</td><td> </td><td class="right"> valid Content-Length header field if the message body length is known</td><td class="lineno" valign="top"></td></tr> 791 791 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 792 <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 33, line 43</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 33, line 43</em></th><td></td></tr> 793 <tr><td class="lineno" valign="top"></td><td class="left"> agent MAY discard the remaining data or attempt to determine if that</td><td> </td><td class="right"> agent MAY discard the remaining data or attempt to determine if that</td><td class="lineno" valign="top"></td></tr> 794 <tr><td class="lineno" valign="top"></td><td class="left"> data belongs as part of the prior response body, which might be the</td><td> </td><td class="right"> data belongs as part of the prior response body, which might be the</td><td class="lineno" valign="top"></td></tr> 795 <tr><td class="lineno" valign="top"></td><td class="left"> case if the prior message's Content-Length value is incorrect. A</td><td> </td><td class="right"> case if the prior message's Content-Length value is incorrect. A</td><td class="lineno" valign="top"></td></tr> 796 <tr><td class="lineno" valign="top"></td><td class="left"> client MUST NOT process, cache, or forward such extra data as a</td><td> </td><td class="right"> client MUST NOT process, cache, or forward such extra data as a</td><td class="lineno" valign="top"></td></tr> 797 <tr><td class="lineno" valign="top"></td><td class="left"> separate response, since such behavior would be vulnerable to cache</td><td> </td><td class="right"> separate response, since such behavior would be vulnerable to cache</td><td class="lineno" valign="top"></td></tr> 798 <tr><td class="lineno" valign="top"></td><td class="left"> poisoning.</td><td> </td><td class="right"> poisoning.</td><td class="lineno" valign="top"></td></tr> 799 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 800 <tr><td class="lineno" valign="top"></td><td class="left">3.4. Handling Incomplete Messages</td><td> </td><td class="right">3.4. Handling Incomplete Messages</td><td class="lineno" valign="top"></td></tr> 801 <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 <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> 803 <tr><td><a name="diff0042" /></td></tr> 804 <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> 805 <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> 806 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 807 <tr><td class="lineno" valign="top"></td><td class="left"> A client that receives an incomplete response message, which can</td><td> </td><td class="right"> A client that receives an incomplete response message, which can</td><td class="lineno" valign="top"></td></tr> 808 <tr><td class="lineno" valign="top"></td><td class="left"> occur when a connection is closed prematurely or when decoding a</td><td> </td><td class="right"> occur when a connection is closed prematurely or when decoding a</td><td class="lineno" valign="top"></td></tr> 809 <tr><td class="lineno" valign="top"></td><td class="left"> supposedly chunked transfer coding fails, MUST record the message as</td><td> </td><td class="right"> supposedly chunked transfer coding fails, MUST record the message as</td><td class="lineno" valign="top"></td></tr> 810 <tr><td class="lineno" valign="top"></td><td class="left"> incomplete. Cache requirements for incomplete responses are defined</td><td> </td><td class="right"> incomplete. Cache requirements for incomplete responses are defined</td><td class="lineno" valign="top"></td></tr> 811 <tr><td class="lineno" valign="top"></td><td class="left"> in Section 3 of [RFC7234].</td><td> </td><td class="right"> in Section 3 of [RFC7234].</td><td class="lineno" valign="top"></td></tr> 812 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 813 <tr><td class="lineno" valign="top"></td><td class="left"> If a response terminates in the middle of the header section (before</td><td> </td><td class="right"> If a response terminates in the middle of the header section (before</td><td class="lineno" valign="top"></td></tr> 814 <tr><td class="lineno" valign="top"></td><td class="left"> the empty line is received) and the status code might rely on header</td><td> </td><td class="right"> the empty line is received) and the status code might rely on header</td><td class="lineno" valign="top"></td></tr> 815 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 816 <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 35, line 26</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 35, line 26</em></th><td></td></tr> 792 <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 35, line 26</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 35, line 26</em></th><td></td></tr> 817 793 <tr><td class="lineno" valign="top"></td><td class="left"> / "compress" ; Section 4.2.1</td><td> </td><td class="right"> / "compress" ; Section 4.2.1</td><td class="lineno" valign="top"></td></tr> 818 794 <tr><td class="lineno" valign="top"></td><td class="left"> / "deflate" ; Section 4.2.2</td><td> </td><td class="right"> / "deflate" ; Section 4.2.2</td><td class="lineno" valign="top"></td></tr> … … 825 801 <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> 826 802 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 827 <tr><td><a name="diff004 3" /></td></tr>803 <tr><td><a name="diff0042" /></td></tr> 828 804 <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> 829 805 <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> … … 839 815 <tr><td class="lineno" valign="top"></td><td class="left"> sequence of length-delimited buffers, which enables the sender to</td><td> </td><td class="right"> sequence of length-delimited buffers, which enables the sender to</td><td class="lineno" valign="top"></td></tr> 840 816 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 841 <tr bgcolor="gray" ><td></td><th><a name="part-l2 7" /><small>skipping to change at</small><em> page 38, line 28</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 38, line 28</em></th><td></td></tr>817 <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 38, line 28</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 38, line 28</em></th><td></td></tr> 842 818 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 843 819 <tr><td class="lineno" valign="top"></td><td class="left"> The "deflate" coding is a "zlib" data format [RFC1950] containing a</td><td> </td><td class="right"> The "deflate" coding is a "zlib" data format [RFC1950] containing a</td><td class="lineno" valign="top"></td></tr> … … 850 826 <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> 851 827 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 852 <tr><td><a name="diff004 4" /></td></tr>828 <tr><td><a name="diff0043" /></td></tr> 853 829 <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> 854 830 <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> … … 866 842 <tr><td class="lineno" valign="top"></td><td class="left"> coding names, each allowing for optional parameters (as described in</td><td> </td><td class="right"> coding names, each allowing for optional parameters (as described in</td><td class="lineno" valign="top"></td></tr> 867 843 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 868 <tr bgcolor="gray" ><td></td><th><a name="part-l2 8" /><small>skipping to change at</small><em> page 49, line 29</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 49, line 29</em></th><td></td></tr>844 <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 49, line 29</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 49, line 29</em></th><td></td></tr> 869 845 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 870 846 <tr><td class="lineno" valign="top"></td><td class="left"> A proxy MUST NOT modify the "absolute-path" and "query" parts of the</td><td> </td><td class="right"> A proxy MUST NOT modify the "absolute-path" and "query" parts of the</td><td class="lineno" valign="top"></td></tr> … … 877 853 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 878 854 <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> 879 <tr><td><a name="diff004 5" /></td></tr>855 <tr><td><a name="diff0044" /></td></tr> 880 856 <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> 881 857 <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> 882 858 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 883 859 <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> 884 <tr><td><a name="diff004 6" /></td></tr>860 <tr><td><a name="diff0045" /></td></tr> 885 861 <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> 886 862 <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> … … 892 868 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 893 869 <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> 894 <tr><td><a name="diff004 7" /></td></tr>870 <tr><td><a name="diff0046" /></td></tr> 895 871 <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> 896 872 <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> … … 900 876 <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> 901 877 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 902 <tr><td><a name="diff004 8" /></td></tr>878 <tr><td><a name="diff0047" /></td></tr> 903 879 <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> 904 880 <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> … … 923 899 <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> 924 900 <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> 925 <tr><td><a name="diff004 9" /></td></tr>901 <tr><td><a name="diff0048" /></td></tr> 926 902 <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> 927 903 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 936 912 <tr><td class="lineno" valign="top"></td><td class="left"> When a header field aside from Connection is used to supply control</td><td> </td><td class="right"> When a header field aside from Connection is used to supply control</td><td class="lineno" valign="top"></td></tr> 937 913 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 938 <tr bgcolor="gray" ><td></td><th><a name="part-l2 9" /><small>skipping to change at</small><em> page 51, line 8</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 51, line 8</em></th><td></td></tr>914 <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 51, line 8</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 51, line 8</em></th><td></td></tr> 939 915 <tr><td class="lineno" valign="top"></td><td class="left"> recipients on the chain ("end-to-end"), enabling the message to be</td><td> </td><td class="right"> recipients on the chain ("end-to-end"), enabling the message to be</td><td class="lineno" valign="top"></td></tr> 940 916 <tr><td class="lineno" valign="top"></td><td class="left"> self-descriptive and allowing future connection-specific extensions</td><td> </td><td class="right"> self-descriptive and allowing future connection-specific extensions</td><td class="lineno" valign="top"></td></tr> … … 947 923 <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> 948 924 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 949 <tr><td><a name="diff00 50" /></td></tr>925 <tr><td><a name="diff0049" /></td></tr> 950 926 <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> 951 927 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 960 936 <tr><td class="lineno" valign="top"></td><td class="left"> connection option. In contrast, a connection-specific header field</td><td> </td><td class="right"> connection option. In contrast, a connection-specific header field</td><td class="lineno" valign="top"></td></tr> 961 937 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 962 <tr bgcolor="gray" ><td></td><th><a name="part-l 30" /><small>skipping to change at</small><em> page 51, line 51</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 51, line 51</em></th><td></td></tr>938 <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 51, line 51</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 51, line 51</em></th><td></td></tr> 963 939 <tr><td class="lineno" valign="top"></td><td class="left"> A client that does not support persistent connections MUST send the</td><td> </td><td class="right"> A client that does not support persistent connections MUST send the</td><td class="lineno" valign="top"></td></tr> 964 940 <tr><td class="lineno" valign="top"></td><td class="left"> "close" connection option in every request message.</td><td> </td><td class="right"> "close" connection option in every request message.</td><td class="lineno" valign="top"></td></tr> … … 971 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> 972 948 <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> 973 <tr><td><a name="diff005 1" /></td></tr>949 <tr><td><a name="diff0050" /></td></tr> 974 950 <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> 975 951 <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> … … 979 955 <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> 980 956 <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> 981 <tr><td><a name="diff005 2" /></td></tr>957 <tr><td><a name="diff0051" /></td></tr> 982 958 <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> 983 959 <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> … … 988 964 <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> 989 965 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 990 <tr><td><a name="diff005 3" /></td></tr>966 <tr><td><a name="diff0052" /></td></tr> 991 967 <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> 992 968 <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> … … 1003 979 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1004 980 <tr><td class="lineno" valign="top"></td><td class="left"> 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> 1005 <tr><td><a name="diff005 4" /></td></tr>981 <tr><td><a name="diff0053" /></td></tr> 1006 982 <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> 1007 983 <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> … … 1021 997 <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> 1022 998 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1023 <tr><td><a name="diff005 5" /></td></tr>999 <tr><td><a name="diff0054" /></td></tr> 1024 1000 <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> 1025 1001 <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> … … 1034 1010 <tr><td class="lineno" valign="top"></td><td class="left"> new connection and automatically retransmit an aborted sequence of</td><td> </td><td class="right"> new connection and automatically retransmit an aborted sequence of</td><td class="lineno" valign="top"></td></tr> 1035 1011 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1036 <tr bgcolor="gray" ><td></td><th><a name="part-l3 1" /><small>skipping to change at</small><em> page 53, line 38</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 53, line 38</em></th><td></td></tr>1012 <tr bgcolor="gray" ><td></td><th><a name="part-l30" /><small>skipping to change at</small><em> page 53, line 38</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 53, line 38</em></th><td></td></tr> 1037 1013 <tr><td class="lineno" valign="top"></td><td class="left"> the requests that failed.</td><td> </td><td class="right"> the requests that failed.</td><td class="lineno" valign="top"></td></tr> 1038 1014 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1045 1021 <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> 1046 1022 <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> 1047 <tr><td><a name="diff005 6" /></td></tr>1023 <tr><td><a name="diff0055" /></td></tr> 1048 1024 <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> 1049 1025 <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> … … 1059 1035 <tr><td class="lineno" valign="top"></td><td class="left"> connection (see the TCP reset problem described in Section 6.6).</td><td> </td><td class="right"> connection (see the TCP reset problem described in Section 6.6).</td><td class="lineno" valign="top"></td></tr> 1060 1036 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1061 <tr bgcolor="gray" ><td></td><th><a name="part-l3 2" /><small>skipping to change at</small><em> page 54, line 40</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 54, line 40</em></th><td></td></tr>1037 <tr bgcolor="gray" ><td></td><th><a name="part-l31" /><small>skipping to change at</small><em> page 54, line 40</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 54, line 40</em></th><td></td></tr> 1062 1038 <tr><td class="lineno" valign="top"></td><td class="left"> conservative when opening multiple connections.</td><td> </td><td class="right"> conservative when opening multiple connections.</td><td class="lineno" valign="top"></td></tr> 1063 1039 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1070 1046 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1071 1047 <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> 1072 <tr><td><a name="diff005 7" /></td></tr>1048 <tr><td><a name="diff0056" /></td></tr> 1073 1049 <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> 1074 1050 <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> 1075 1051 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1076 <tr><td><a name="diff0058" /></td></tr> 1077 <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> 1078 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1079 <tr><td><a name="diff0059" /></td></tr> 1080 <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> 1052 <tr><td class="lineno" valign="top"></td><td class="left">6.5. Failures and Timeouts</td><td> </td><td class="right">6.5. Failures and Timeouts</td><td class="lineno" valign="top"></td></tr> 1053 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1054 <tr><td class="lineno" valign="top"></td><td class="left"> Servers will usually have some timeout value beyond which they will</td><td> </td><td class="right"> Servers will usually have some timeout value beyond which they will</td><td class="lineno" valign="top"></td></tr> 1081 1055 <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> 1082 1056 <tr><td class="lineno" valign="top"></td><td class="left"> this a higher value since it is likely that the client will be making</td><td> </td><td class="right"> this a higher value since it is likely that the client will be making</td><td class="lineno" valign="top"></td></tr> 1083 1057 <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> 1084 1058 <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> 1085 <tr><td><a name="diff0060" /></td></tr> 1086 <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> 1087 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1088 <tr><td><a name="diff0061" /></td></tr> 1089 <tr><td class="lineno" valign="top"></td><td class="lblock"> 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> 1090 <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> 1091 <tr><td class="lineno" valign="top"></td><td class="left"> open connections for a received closure signal and respond to it as</td><td> </td><td class="right"> open connections for a received closure signal and respond to it as</td><td class="lineno" valign="top"></td></tr> 1092 <tr><td class="lineno" valign="top"></td><td class="left"> appropriate, since prompt closure of both sides of a connection</td><td> </td><td class="right"> appropriate, since prompt closure of both sides of a connection</td><td class="lineno" valign="top"></td></tr> 1059 <tr><td class="lineno" valign="top"></td><td class="left"> existence) of this timeout for either the client or the server.</td><td> </td><td class="right"> existence) of this timeout for either the client or the server.</td><td class="lineno" valign="top"></td></tr> 1060 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 1061 <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 55, line 19</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 55, line 19</em></th><td></td></tr> 1093 1062 <tr><td class="lineno" valign="top"></td><td class="left"> enables allocated system resources to be reclaimed.</td><td> </td><td class="right"> enables allocated system resources to be reclaimed.</td><td class="lineno" valign="top"></td></tr> 1094 1063 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1101 1070 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1102 1071 <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> 1103 <tr><td><a name="diff00 62" /></td></tr>1072 <tr><td><a name="diff0057" /></td></tr> 1104 1073 <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> 1105 1074 <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> … … 1114 1083 <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> 1115 1084 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1116 <tr><td><a name="diff00 63" /></td></tr>1085 <tr><td><a name="diff0058" /></td></tr> 1117 1086 <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> 1118 1087 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1121 1090 <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> 1122 1091 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1123 <tr><td><a name="diff00 64" /></td></tr>1092 <tr><td><a name="diff0059" /></td></tr> 1124 1093 <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> 1125 1094 <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> … … 1127 1096 <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> 1128 1097 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1129 <tr><td><a name="diff006 5" /></td></tr>1098 <tr><td><a name="diff0060" /></td></tr> 1130 1099 <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> 1131 1100 <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> … … 1135 1104 <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> 1136 1105 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1137 <tr><td><a name="diff006 6" /></td></tr>1106 <tr><td><a name="diff0061" /></td></tr> 1138 1107 <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> 1139 1108 <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> … … 1141 1110 <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> 1142 1111 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1143 <tr><td><a name="diff006 7" /></td></tr>1112 <tr><td><a name="diff0062" /></td></tr> 1144 1113 <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> 1145 1114 <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> … … 1151 1120 <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> 1152 1121 <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> 1153 <tr><td><a name="diff006 8" /></td></tr>1122 <tr><td><a name="diff0063" /></td></tr> 1154 1123 <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> 1155 1124 <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> … … 1175 1144 <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> 1176 1145 <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> 1177 <tr><td><a name="diff006 9" /></td></tr>1146 <tr><td><a name="diff0064" /></td></tr> 1178 1147 <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> 1179 1148 <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> … … 1189 1158 <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> 1190 1159 <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> 1191 <tr><td><a name="diff00 70" /></td></tr>1160 <tr><td><a name="diff0065" /></td></tr> 1192 1161 <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> 1193 1162 <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> … … 1213 1182 <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> 1214 1183 <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> 1215 <tr><td><a name="diff00 71" /></td></tr>1184 <tr><td><a name="diff0066" /></td></tr> 1216 1185 <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> 1217 1186 <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> … … 1240 1209 <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> 1241 1210 <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> 1242 <tr><td><a name="diff00 72" /></td></tr>1211 <tr><td><a name="diff0067" /></td></tr> 1243 1212 <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> 1244 1213 <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> … … 1254 1223 <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> 1255 1224 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1256 <tr><td><a name="diff00 73" /></td></tr>1225 <tr><td><a name="diff0068" /></td></tr> 1257 1226 <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> 1258 1227 <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> … … 1276 1245 <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> 1277 1246 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1278 <tr><td><a name="diff00 74" /></td></tr>1247 <tr><td><a name="diff0069" /></td></tr> 1279 1248 <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> 1280 1249 <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> 1281 1250 <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> 1282 1251 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1283 <tr><td><a name="diff007 5" /></td></tr>1252 <tr><td><a name="diff0070" /></td></tr> 1284 1253 <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> 1285 1254 <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> … … 1299 1268 <tr><td class="lineno" valign="top"></td><td class="left"> +-------------------+----------+----------+---------------+</td><td> </td><td class="right"> +-------------------+----------+----------+---------------+</td><td class="lineno" valign="top"></td></tr> 1300 1269 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1301 <tr><td><a name="diff007 6" /></td></tr>1270 <tr><td><a name="diff0071" /></td></tr> 1302 1271 <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> 1303 1272 <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> … … 1319 1288 <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> 1320 1289 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1321 <tr><td><a name="diff007 7" /></td></tr>1290 <tr><td><a name="diff0072" /></td></tr> 1322 1291 <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> 1323 1292 <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> … … 1337 1306 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1338 1307 <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> 1339 <tr><td><a name="diff007 8" /></td></tr>1308 <tr><td><a name="diff0073" /></td></tr> 1340 1309 <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> 1341 1310 <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> … … 1361 1330 <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> 1362 1331 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1363 <tr><td><a name="diff007 9" /></td></tr>1332 <tr><td><a name="diff0074" /></td></tr> 1364 1333 <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> 1365 1334 <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> … … 1386 1355 <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> 1387 1356 <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> 1388 <tr><td><a name="diff00 80" /></td></tr>1357 <tr><td><a name="diff0075" /></td></tr> 1389 1358 <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> 1390 1359 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1410 1379 <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> 1411 1380 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1412 <tr><td><a name="diff00 81" /></td></tr>1381 <tr><td><a name="diff0076" /></td></tr> 1413 1382 <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> 1414 1383 <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> … … 1424 1393 <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> 1425 1394 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1426 <tr><td><a name="diff00 82" /></td></tr>1395 <tr><td><a name="diff0077" /></td></tr> 1427 1396 <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> 1428 1397 <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> … … 1443 1412 <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> 1444 1413 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1445 <tr><td><a name="diff00 83" /></td></tr>1414 <tr><td><a name="diff0078" /></td></tr> 1446 1415 <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> 1447 1416 <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> … … 1453 1422 <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> 1454 1423 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1455 <tr><td><a name="diff00 84" /></td></tr>1424 <tr><td><a name="diff0079" /></td></tr> 1456 1425 <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> 1457 1426 <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> … … 1472 1441 <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> 1473 1442 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1474 <tr><td><a name="diff008 5" /></td></tr>1443 <tr><td><a name="diff0080" /></td></tr> 1475 1444 <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> 1476 1445 <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> 1477 1446 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1478 <tr><td><a name="diff008 6" /></td></tr>1447 <tr><td><a name="diff0081" /></td></tr> 1479 1448 <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> 1480 1449 <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> … … 1494 1463 <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> 1495 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> 1496 <tr><td><a name="diff008 7" /></td></tr>1465 <tr><td><a name="diff0082" /></td></tr> 1497 1466 <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> 1498 1467 <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> … … 1520 1489 <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> 1521 1490 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1522 <tr><td><a name="diff008 8" /></td></tr>1491 <tr><td><a name="diff0083" /></td></tr> 1523 1492 <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> 1524 1493 <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> … … 1545 1514 <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> 1546 1515 <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> 1547 <tr><td><a name="diff008 9" /></td></tr>1516 <tr><td><a name="diff0084" /></td></tr> 1548 1517 <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> 1549 1518 <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> … … 1563 1532 <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> 1564 1533 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1565 <tr><td><a name="diff00 90" /></td></tr>1534 <tr><td><a name="diff0085" /></td></tr> 1566 1535 <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> 1567 1536 <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> … … 1588 1557 <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> 1589 1558 <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> 1590 <tr><td><a name="diff00 91" /></td></tr>1559 <tr><td><a name="diff0086" /></td></tr> 1591 1560 <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> 1592 1561 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1612 1581 <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> 1613 1582 <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> 1614 <tr><td><a name="diff00 92" /></td></tr>1583 <tr><td><a name="diff0087" /></td></tr> 1615 1584 <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> 1616 1585 <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> … … 1636 1605 <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> 1637 1606 <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> 1638 <tr><td><a name="diff00 93" /></td></tr>1607 <tr><td><a name="diff0088" /></td></tr> 1639 1608 <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> 1640 1609 <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> … … 1660 1629 <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> 1661 1630 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1662 <tr><td><a name="diff00 94" /></td></tr>1631 <tr><td><a name="diff0089" /></td></tr> 1663 1632 <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> 1664 1633 <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> … … 1686 1655 <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> 1687 1656 <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> 1688 <tr><td><a name="diff009 5" /></td></tr>1657 <tr><td><a name="diff0090" /></td></tr> 1689 1658 <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> 1690 1659 <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> … … 1692 1661 <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> 1693 1662 <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> 1694 <tr><td><a name="diff009 6" /></td></tr>1663 <tr><td><a name="diff0091" /></td></tr> 1695 1664 <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> 1696 1665 <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> … … 1698 1667 <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> 1699 1668 <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> 1700 <tr><td><a name="diff009 7" /></td></tr>1669 <tr><td><a name="diff0092" /></td></tr> 1701 1670 <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> 1702 1671 <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> … … 1704 1673 <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> 1705 1674 <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> 1706 <tr><td><a name="diff009 8" /></td></tr>1675 <tr><td><a name="diff0093" /></td></tr> 1707 1676 <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> 1708 1677 <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> … … 1710 1679 <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> 1711 1680 <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> 1712 <tr><td><a name="diff009 9" /></td></tr>1681 <tr><td><a name="diff0094" /></td></tr> 1713 1682 <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> 1714 1683 <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> … … 1720 1689 <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> 1721 1690 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1722 <tr><td><a name="diff0 100" /></td></tr>1691 <tr><td><a name="diff0095" /></td></tr> 1723 1692 <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> 1724 1693 <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> … … 1744 1713 <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> 1745 1714 <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> 1746 <tr><td><a name="diff0 101" /></td></tr>1715 <tr><td><a name="diff0096" /></td></tr> 1747 1716 <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> 1748 1717 <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> … … 1753 1722 <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> 1754 1723 <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> 1755 <tr><td><a name="diff0 102" /></td></tr>1724 <tr><td><a name="diff0097" /></td></tr> 1756 1725 <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> 1757 1726 <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> … … 1778 1747 <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> 1779 1748 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1780 <tr><td><a name="diff0 103" /></td></tr>1749 <tr><td><a name="diff0098" /></td></tr> 1781 1750 <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> 1782 1751 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1802 1771 <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> 1803 1772 <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="diff0 104" /></td></tr>1773 <tr><td><a name="diff0099" /></td></tr> 1805 1774 <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> 1806 1775 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1807 <tr><td><a name="diff010 5" /></td></tr>1776 <tr><td><a name="diff0100" /></td></tr> 1808 1777 <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> 1809 1778 <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> 1810 1779 <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> 1811 <tr><td><a name="diff010 6" /></td></tr>1780 <tr><td><a name="diff0101" /></td></tr> 1812 1781 <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> 1813 1782 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1814 1783 <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> 1815 1784 <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> 1816 <tr><td><a name="diff010 7" /></td></tr>1785 <tr><td><a name="diff0102" /></td></tr> 1817 1786 <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> 1818 1787 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1819 1788 <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> 1820 <tr><td><a name="diff010 8" /></td></tr>1789 <tr><td><a name="diff0103" /></td></tr> 1821 1790 <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> 1822 1791 <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> … … 1826 1795 <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> 1827 1796 <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> 1828 <tr><td><a name="diff010 9" /></td></tr>1797 <tr><td><a name="diff0104" /></td></tr> 1829 1798 <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> 1830 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> 1831 1800 <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> 1832 1801 <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> 1833 <tr><td><a name="diff01 10" /></td></tr>1802 <tr><td><a name="diff0105" /></td></tr> 1834 1803 <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> 1835 1804 <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> … … 1837 1806 <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> 1838 1807 <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> 1839 <tr><td><a name="diff01 11" /></td></tr>1808 <tr><td><a name="diff0106" /></td></tr> 1840 1809 <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> 1841 1810 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1842 1811 <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> 1843 <tr><td><a name="diff01 12" /></td></tr>1812 <tr><td><a name="diff0107" /></td></tr> 1844 1813 <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> 1845 1814 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"> </td><td class="lineno" valign="top"></td></tr> … … 1847 1816 <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> 1848 1817 <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> 1849 <tr><td><a name="diff01 13" /></td></tr>1818 <tr><td><a name="diff0108" /></td></tr> 1850 1819 <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> 1851 1820 <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> … … 1853 1822 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1854 1823 <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> 1855 <tr><td><a name="diff01 14" /></td></tr>1824 <tr><td><a name="diff0109" /></td></tr> 1856 1825 <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> 1857 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> … … 1861 1830 <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> 1862 1831 <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> 1863 <tr><td><a name="diff011 5" /></td></tr>1832 <tr><td><a name="diff0110" /></td></tr> 1864 1833 <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> 1865 1834 <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> 1866 1835 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1867 <tr><td><a name="diff011 6" /></td></tr>1836 <tr><td><a name="diff0111" /></td></tr> 1868 1837 <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> 1869 1838 <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> 1870 1839 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1871 1840 <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> 1872 <tr><td><a name="diff011 7" /></td></tr>1841 <tr><td><a name="diff0112" /></td></tr> 1873 1842 <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> 1874 1843 <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> 1875 1844 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1876 <tr><td><a name="diff011 8" /></td></tr>1845 <tr><td><a name="diff0113" /></td></tr> 1877 1846 <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> 1878 1847 <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> … … 1880 1849 <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> 1881 1850 <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> 1882 <tr><td><a name="diff011 9" /></td></tr>1851 <tr><td><a name="diff0114" /></td></tr> 1883 1852 <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> 1884 1853 <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> 1885 1854 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1886 <tr><td><a name="diff01 20" /></td></tr>1855 <tr><td><a name="diff0115" /></td></tr> 1887 1856 <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> 1888 1857 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1889 <tr><td><a name="diff01 21" /></td></tr>1858 <tr><td><a name="diff0116" /></td></tr> 1890 1859 <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> 1891 1860 <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> … … 1894 1863 <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> 1895 1864 <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> 1896 <tr><td><a name="diff01 22" /></td></tr>1865 <tr><td><a name="diff0117" /></td></tr> 1897 1866 <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> 1898 1867 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1902 1871 <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> 1903 1872 <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> 1904 <tr><td><a name="diff01 23" /></td></tr>1873 <tr><td><a name="diff0118" /></td></tr> 1905 1874 <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> 1906 1875 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1907 1876 <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> 1908 1877 <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> 1909 <tr><td><a name="diff01 24" /></td></tr>1878 <tr><td><a name="diff0119" /></td></tr> 1910 1879 <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> 1911 1880 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1912 1881 <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> 1913 <tr><td><a name="diff012 5" /></td></tr>1882 <tr><td><a name="diff0120" /></td></tr> 1914 1883 <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> 1915 1884 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1916 1885 <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> 1917 <tr><td><a name="diff012 6" /></td></tr>1886 <tr><td><a name="diff0121" /></td></tr> 1918 1887 <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> 1919 1888 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1920 <tr><td><a name="diff012 7" /></td></tr>1889 <tr><td><a name="diff0122" /></td></tr> 1921 1890 <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> 1922 1891 <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> 1923 1892 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1924 <tr><td><a name="diff012 8" /></td></tr>1893 <tr><td><a name="diff0123" /></td></tr> 1925 1894 <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> 1926 1895 <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> … … 1928 1897 <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> 1929 1898 <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> 1930 <tr><td><a name="diff012 9" /></td></tr>1899 <tr><td><a name="diff0124" /></td></tr> 1931 1900 <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> 1932 1901 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1952 1921 <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> 1953 1922 <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> 1954 <tr><td><a name="diff01 30" /></td></tr>1923 <tr><td><a name="diff0125" /></td></tr> 1955 1924 <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> 1956 1925 <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 1945 <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> 1977 1946 <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> 1978 <tr><td><a name="diff01 31" /></td></tr>1947 <tr><td><a name="diff0126" /></td></tr> 1979 1948 <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> 1980 1949 <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> 1981 <tr><td><a name="diff01 32" /></td></tr>1950 <tr><td><a name="diff0127" /></td></tr> 1982 1951 <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> 1983 1952 <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> … … 2003 1972 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 2004 1973 <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> 2005 <tr><td><a name="diff01 33" /></td></tr>1974 <tr><td><a name="diff0128" /></td></tr> 2006 1975 <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> 2007 1976 <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> … … 2022 1991 <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> 2023 1992 <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> 2024 <tr><td><a name="diff01 34" /></td></tr>1993 <tr><td><a name="diff0129" /></td></tr> 2025 1994 <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> 2026 1995 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 2046 2015 <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> 2047 2016 <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> 2048 <tr><td><a name="diff013 5" /></td></tr>2017 <tr><td><a name="diff0130" /></td></tr> 2049 2018 <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> 2050 2019 <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> … … 2060 2029 2061 2030 <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr> 2062 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 13 5change blocks. </a></th></tr>2063 <tr class="stats"><td></td><th><i>2 31 lines changed or deleted</i></th><th><i> </i></th><th><i>210lines changed or added</i></th><td></td></tr>2031 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 130 change blocks. </a></th></tr> 2032 <tr class="stats"><td></td><th><i>225 lines changed or deleted</i></th><th><i> </i></th><th><i>204 lines changed or added</i></th><td></td></tr> 2064 2033 <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> 2065 2034 </table> -
draft-ietf-httpbis/latest/p1-messaging.html
r2641 r2642 677 677 </li> 678 678 <li><a href="#rfc.section.6.4">6.4</a> <a href="#persistent.concurrency">Concurrency</a></li> 679 <li><a href="#rfc.section.6.5">6.5</a> <a href="#persistent.failures">Failures and Time -outs</a></li>679 <li><a href="#rfc.section.6.5">6.5</a> <a href="#persistent.failures">Failures and Timeouts</a></li> 680 680 <li><a href="#rfc.section.6.6">6.6</a> <a href="#persistent.tear-down">Tear-down</a></li> 681 681 <li><a href="#rfc.section.6.7">6.7</a> <a href="#header.upgrade">Upgrade</a></li> … … 1617 1617 <div id="incomplete.messages"> 1618 1618 <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a> <a href="#incomplete.messages">Handling Incomplete Messages</a></h2> 1619 <p id="rfc.section.3.4.p.1">A server that receives an incomplete request message, usually due to a canceled request or a triggered time -out exception, <em class="bcp14">MAY</em> send an error response prior to closing the connection.1619 <p id="rfc.section.3.4.p.1">A server that receives an incomplete request message, usually due to a canceled request or a triggered timeout exception, <em class="bcp14">MAY</em> send an error response prior to closing the connection. 1620 1620 </p> 1621 1621 <p id="rfc.section.3.4.p.2">A client that receives an incomplete response message, which can occur when a connection is closed prematurely or when decoding … … 2266 2266 </div> 2267 2267 <div id="persistent.failures"> 2268 <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a> <a href="#persistent.failures">Failures and Time -outs</a></h2>2269 <p id="rfc.section.6.5.p.1">Servers will usually have some time -out value beyond which they will no longer maintain an inactive connection. Proxy servers2268 <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a> <a href="#persistent.failures">Failures and Timeouts</a></h2> 2269 <p id="rfc.section.6.5.p.1">Servers will usually have some timeout value beyond which they will no longer maintain an inactive connection. Proxy servers 2270 2270 might make this a higher value since it is likely that the client will be making more connections through the same proxy server. 2271 The use of persistent connections places no requirements on the length (or existence) of this time -out for either the client2271 The use of persistent connections places no requirements on the length (or existence) of this timeout for either the client 2272 2272 or the server. 2273 2273 </p> 2274 <p id="rfc.section.6.5.p.2">A client or server that wishes to time -out <em class="bcp14">SHOULD</em> issue a graceful close on the connection. Implementations <em class="bcp14">SHOULD</em> constantly monitor open connections for a received closure signal and respond to it as appropriate, since prompt closure of2274 <p id="rfc.section.6.5.p.2">A client or server that wishes to time out <em class="bcp14">SHOULD</em> issue a graceful close on the connection. Implementations <em class="bcp14">SHOULD</em> constantly monitor open connections for a received closure signal and respond to it as appropriate, since prompt closure of 2275 2275 both sides of a connection enables allocated system resources to be reclaimed. 2276 2276 </p> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2641 r2642 1864 1864 <t> 1865 1865 A server that receives an incomplete request message, usually due to a 1866 canceled request or a triggered time -out exception, &MAY; send an error1866 canceled request or a triggered timeout exception, &MAY; send an error 1867 1867 response prior to closing the connection. 1868 1868 </t> … … 3129 3129 </section> 3130 3130 3131 <section title="Failures and Time -outs" anchor="persistent.failures">3132 <t> 3133 Servers will usually have some time -out value beyond which they will3131 <section title="Failures and Timeouts" anchor="persistent.failures"> 3132 <t> 3133 Servers will usually have some timeout value beyond which they will 3134 3134 no longer maintain an inactive connection. Proxy servers might make 3135 3135 this a higher value since it is likely that the client will be making 3136 3136 more connections through the same proxy server. The use of persistent 3137 3137 connections places no requirements on the length (or existence) of 3138 this time -out for either the client or the server.3139 </t> 3140 <t> 3141 A client or server that wishes to time -out &SHOULD; issue a graceful close3138 this timeout for either the client or the server. 3139 </t> 3140 <t> 3141 A client or server that wishes to time out &SHOULD; issue a graceful close 3142 3142 on the connection. Implementations &SHOULD; constantly monitor open 3143 3143 connections for a received closure signal and respond to it as appropriate,
Note: See TracChangeset
for help on using the changeset viewer.