Changeset 2645 for draft-ietf-httpbis
- Timestamp:
- 06/05/14 14:15:32 (7 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/auth48/p2-semantics.unpg.txt
r2644 r2645 2633 2633 6. Response Status Codes 2634 2634 2635 The status-code element is a 3-digit integer code giving the result2636 of the attempt to understand and satisfy the request.2635 The status-code element is a three-digit integer code giving the 2636 result of the attempt to understand and satisfy the request. 2637 2637 2638 2638 HTTP status codes are extensible. HTTP clients are not required to … … 2651 2651 2652 2652 The first digit of the status-code defines the class of response. 2653 The last two digits do not have any categorization role. There are 52654 values for the first digit:2653 The last two digits do not have any categorization role. There are 2654 five values for the first digit: 2655 2655 2656 2656 o 1xx (Informational): The request was received, continuing process -
draft-ietf-httpbis/latest/auth48/rfc7231.abdiff.txt
r2644 r2645 1105 1105 1106 1106 1107 Section 6., paragraph 1:1108 OLD:1109 1110 The status-code element is a 3-digit integer code giving the result1111 of the attempt to understand and satisfy the request.1112 1113 NEW:1114 1115 The status-code element is a three-digit integer code giving the1116 result of the attempt to understand and satisfy the request.1117 1118 1119 1107 Section 6., paragraph 3: 1120 1108 OLD: … … 1133 1121 Request) status code. The response message will usually contain a 1134 1122 representation that explains the status. 1135 1136 1137 Section 6., paragraph 4:1138 OLD:1139 1140 The first digit of the status-code defines the class of response.1141 The last two digits do not have any categorization role. There are 51142 values for the first digit:1143 1144 NEW:1145 1146 The first digit of the status-code defines the class of response.1147 The last two digits do not have any categorization role. There are1148 five values for the first digit:1149 1123 1150 1124 -
draft-ietf-httpbis/latest/auth48/rfc7231.diff.html
r2644 r2645 856 856 <tr><td class="lineno" valign="top"></td><td class="left">6. Response Status Codes</td><td> </td><td class="right">6. Response Status Codes</td><td class="lineno" valign="top"></td></tr> 857 857 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 858 <tr><td><a name="diff0045" /></td></tr> 859 <tr><td class="lineno" valign="top"></td><td class="lblock"> The status-code element is a <span class="delete">3-digit</span> integer code giving the result</td><td> </td><td class="rblock"> The status-code element is a <span class="insert">three-digit</span> integer code giving the</td><td class="lineno" valign="top"></td></tr> 860 <tr><td class="lineno" valign="top"></td><td class="lblock"> of the attempt to understand and satisfy the request.</td><td> </td><td class="rblock"> result of the attempt to understand and satisfy the request.</td><td class="lineno" valign="top"></td></tr> 858 <tr><td class="lineno" valign="top"></td><td class="left"> The status-code element is a three-digit integer code giving the</td><td> </td><td class="right"> The status-code element is a three-digit integer code giving the</td><td class="lineno" valign="top"></td></tr> 859 <tr><td class="lineno" valign="top"></td><td class="left"> result of the attempt to understand and satisfy the request.</td><td> </td><td class="right"> result of the attempt to understand and satisfy the request.</td><td class="lineno" valign="top"></td></tr> 861 860 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 862 861 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP status codes are extensible. HTTP clients are not required to</td><td> </td><td class="right"> HTTP status codes are extensible. HTTP clients are not required to</td><td class="lineno" valign="top"></td></tr> … … 870 869 <tr><td class="lineno" valign="top"></td><td class="left"> For example, if an unrecognized status code of 471 is received by a</td><td> </td><td class="right"> For example, if an unrecognized status code of 471 is received by a</td><td class="lineno" valign="top"></td></tr> 871 870 <tr><td class="lineno" valign="top"></td><td class="left"> client, the client can assume that there was something wrong with its</td><td> </td><td class="right"> client, the client can assume that there was something wrong with its</td><td class="lineno" valign="top"></td></tr> 872 <tr><td><a name="diff004 6" /></td></tr>871 <tr><td><a name="diff0045" /></td></tr> 873 872 <tr><td class="lineno" valign="top"></td><td class="lblock"> request and treat the response as if it had received a 400 status</td><td> </td><td class="rblock"> request and treat the response as if it had received a 400 <span class="insert">(Bad</span></td><td class="lineno" valign="top"></td></tr> 874 873 <tr><td class="lineno" valign="top"></td><td class="lblock"> code. The response message will usually contain a representation</td><td> </td><td class="rblock"><span class="insert"> Request)</span> status code. The response message will usually contain a</td><td class="lineno" valign="top"></td></tr> … … 876 875 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 877 876 <tr><td class="lineno" valign="top"></td><td class="left"> The first digit of the status-code defines the class of response.</td><td> </td><td class="right"> The first digit of the status-code defines the class of response.</td><td class="lineno" valign="top"></td></tr> 878 <tr><td><a name="diff0047" /></td></tr> 879 <tr><td class="lineno" valign="top"></td><td class="lblock"> The last two digits do not have any categorization role. There are <span class="delete">5</span></td><td> </td><td class="rblock"> The last two digits do not have any categorization role. There are</td><td class="lineno" valign="top"></td></tr> 880 <tr><td class="lineno" valign="top"></td><td class="lblock"> values for the first digit:</td><td> </td><td class="rblock"> <span class="insert">five</span> values for the first digit:</td><td class="lineno" valign="top"></td></tr> 877 <tr><td class="lineno" valign="top"></td><td class="left"> The last two digits do not have any categorization role. There are</td><td> </td><td class="right"> The last two digits do not have any categorization role. There are</td><td class="lineno" valign="top"></td></tr> 878 <tr><td class="lineno" valign="top"></td><td class="left"> five values for the first digit:</td><td> </td><td class="right"> five values for the first digit:</td><td class="lineno" valign="top"></td></tr> 881 879 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 882 880 <tr><td class="lineno" valign="top"></td><td class="left"> o 1xx (Informational): The request was received, continuing process</td><td> </td><td class="right"> o 1xx (Informational): The request was received, continuing process</td><td class="lineno" valign="top"></td></tr> … … 885 883 <tr><td class="lineno" valign="top"></td><td class="left"> understood, and accepted</td><td> </td><td class="right"> understood, and accepted</td><td class="lineno" valign="top"></td></tr> 886 884 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 887 <tr><td class="lineno" valign="top"></td><td class="left"> o 3xx (Redirection): Further action needs to be taken in order to</td><td> </td><td class="right"> o 3xx (Redirection): Further action needs to be taken in order to</td><td class="lineno" valign="top"></td></tr>888 <tr><td class="lineno" valign="top"></td><td class="left"> complete the request</td><td> </td><td class="right"> complete the request</td><td class="lineno" valign="top"></td></tr>889 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>890 <tr><td class="lineno" valign="top"></td><td class="left"> o 4xx (Client Error): The request contains bad syntax or cannot be</td><td> </td><td class="right"> o 4xx (Client Error): The request contains bad syntax or cannot be</td><td class="lineno" valign="top"></td></tr>891 885 <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr> 892 886 <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 48, line 14</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 48, line 14</em></th><td></td></tr> … … 901 895 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 902 896 <tr><td class="lineno" valign="top"></td><td class="left"> Responses with status codes that are defined as cacheable by default</td><td> </td><td class="right"> Responses with status codes that are defined as cacheable by default</td><td class="lineno" valign="top"></td></tr> 903 <tr><td><a name="diff004 8" /></td></tr>897 <tr><td><a name="diff0046" /></td></tr> 904 898 <tr><td class="lineno" valign="top"></td><td class="lblock"> (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414, 501 in this</td><td> </td><td class="rblock"> (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414, <span class="insert">and</span> 501 in</td><td class="lineno" valign="top"></td></tr> 905 899 <tr><td class="lineno" valign="top"></td><td class="lblock"> specification) can be reused by a cache with heuristic expiration</td><td> </td><td class="rblock"> this specification) can be reused by a cache with heuristic</td><td class="lineno" valign="top"></td></tr> … … 929 923 <tr><td class="lineno" valign="top"></td><td class="left"> operation.</td><td> </td><td class="right"> operation.</td><td class="lineno" valign="top"></td></tr> 930 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> 931 <tr><td><a name="diff004 9" /></td></tr>925 <tr><td><a name="diff0047" /></td></tr> 932 926 <tr><td class="lineno" valign="top"></td><td class="lblock"> The 202 response is intentionally non<span class="delete">-</span>committal. Its purpose is to</td><td> </td><td class="rblock"> The 202 response is intentionally noncommittal. Its purpose is to</td><td class="lineno" valign="top"></td></tr> 933 927 <tr><td class="lineno" valign="top"></td><td class="left"> allow a server to accept a request for some other process (perhaps a</td><td> </td><td class="right"> allow a server to accept a request for some other process (perhaps a</td><td class="lineno" valign="top"></td></tr> … … 953 947 <tr><td class="lineno" valign="top"></td><td class="left"> Section 4.2.2 of [RFC7234]).</td><td> </td><td class="right"> Section 4.2.2 of [RFC7234]).</td><td class="lineno" valign="top"></td></tr> 954 948 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 955 <tr><td><a name="diff00 50" /></td></tr>949 <tr><td><a name="diff0048" /></td></tr> 956 950 <tr><td class="lineno" valign="top"></td><td class="lblock"> Note: The original proposal for 300 defined the URI header field</td><td> </td><td class="rblock"> Note: The original proposal for <span class="insert">the</span> 300 <span class="insert">response</span> defined the URI</td><td class="lineno" valign="top"></td></tr> 957 951 <tr><td class="lineno" valign="top"></td><td class="lblock"> as providing a list of alternative representations, such that it</td><td> </td><td class="rblock"> header field as providing a list of alternative representations,</td><td class="lineno" valign="top"></td></tr> … … 969 963 <tr><td class="lineno" valign="top"></td><td class="left"> resource has been assigned a new permanent URI and any future</td><td> </td><td class="right"> resource has been assigned a new permanent URI and any future</td><td class="lineno" valign="top"></td></tr> 970 964 <tr><td class="lineno" valign="top"></td><td class="left"> references to this resource ought to use one of the enclosed URIs.</td><td> </td><td class="right"> references to this resource ought to use one of the enclosed URIs.</td><td class="lineno" valign="top"></td></tr> 971 <tr><td><a name="diff00 51" /></td></tr>965 <tr><td><a name="diff0049" /></td></tr> 972 966 <tr><td class="lineno" valign="top"></td><td class="lblock"> Clients with link<span class="delete"> </span>editing capabilities ought to automatically re-link</td><td> </td><td class="rblock"> Clients with link<span class="insert">-</span>editing capabilities ought to automatically re-link</td><td class="lineno" valign="top"></td></tr> 973 967 <tr><td class="lineno" valign="top"></td><td class="left"> references to the effective request URI to one or more of the new</td><td> </td><td class="right"> references to the effective request URI to one or more of the new</td><td class="lineno" valign="top"></td></tr> … … 993 987 <tr><td class="lineno" valign="top"></td><td class="left"> does not allow changing the request method from POST to GET. This</td><td> </td><td class="right"> does not allow changing the request method from POST to GET. This</td><td class="lineno" valign="top"></td></tr> 994 988 <tr><td class="lineno" valign="top"></td><td class="left"> specification defines no equivalent counterpart for 301 (Moved</td><td> </td><td class="right"> specification defines no equivalent counterpart for 301 (Moved</td><td class="lineno" valign="top"></td></tr> 995 <tr><td><a name="diff005 2" /></td></tr>989 <tr><td><a name="diff0050" /></td></tr> 996 990 <tr><td class="lineno" valign="top"></td><td class="lblock"> Permanently) ([RFC7238]<span class="delete">, however,</span> defines the status code 308</td><td> </td><td class="rblock"> Permanently) ([RFC7238]<span class="insert">; however, it</span> defines the status code 308</td><td class="lineno" valign="top"></td></tr> 997 991 <tr><td class="lineno" valign="top"></td><td class="left"> (Permanent Redirect) for this purpose).</td><td> </td><td class="right"> (Permanent Redirect) for this purpose).</td><td class="lineno" valign="top"></td></tr> … … 1009 1003 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1010 1004 <tr><td class="lineno" valign="top"></td><td class="left"> The 400 (Bad Request) status code indicates that the server cannot or</td><td> </td><td class="right"> The 400 (Bad Request) status code indicates that the server cannot or</td><td class="lineno" valign="top"></td></tr> 1011 <tr><td><a name="diff005 3" /></td></tr>1005 <tr><td><a name="diff0051" /></td></tr> 1012 1006 <tr><td class="lineno" valign="top"></td><td class="lblock"> will not process the request due to something <span class="delete">which</span> is perceived to</td><td> </td><td class="rblock"> will not process the request due to something <span class="insert">that</span> is perceived to be</td><td class="lineno" valign="top"></td></tr> 1013 1007 <tr><td class="lineno" valign="top"></td><td class="lblock"> be a client error (e.g., malformed request syntax, invalid request</td><td> </td><td class="rblock"> a client error (e.g., malformed request syntax, invalid request</td><td class="lineno" valign="top"></td></tr> … … 1034 1028 <tr><td class="lineno" valign="top"></td><td class="left"> ; defined in Section 3.3 of [RFC5322]</td><td> </td><td class="right"> ; defined in Section 3.3 of [RFC5322]</td><td class="lineno" valign="top"></td></tr> 1035 1029 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1036 <tr><td><a name="diff005 4" /></td></tr>1030 <tr><td><a name="diff0052" /></td></tr> 1037 1031 <tr><td class="lineno" valign="top"></td><td class="lblock"> day-name = %x4D.6F.6E ; "Mon", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock"> day-name = %x4D.6F.6E ; "Mon", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr> 1038 1032 <tr><td class="lineno" valign="top"></td><td class="lblock"> / %x54.75.65 ; "Tue", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock"> / %x54.75.65 ; "Tue", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr> … … 1047 1041 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1048 1042 <tr><td class="lineno" valign="top"></td><td class="left"> day = 2DIGIT</td><td> </td><td class="right"> day = 2DIGIT</td><td class="lineno" valign="top"></td></tr> 1049 <tr><td><a name="diff005 5" /></td></tr>1043 <tr><td><a name="diff0053" /></td></tr> 1050 1044 <tr><td class="lineno" valign="top"></td><td class="lblock"> month = %x4A.61.6E ; "Jan", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock"> month = %x4A.61.6E ; "Jan", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr> 1051 1045 <tr><td class="lineno" valign="top"></td><td class="lblock"> / %x46.65.62 ; "Feb", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock"> / %x46.65.62 ; "Feb", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr> … … 1062 1056 <tr><td class="lineno" valign="top"></td><td class="left"> year = 4DIGIT</td><td> </td><td class="right"> year = 4DIGIT</td><td class="lineno" valign="top"></td></tr> 1063 1057 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1064 <tr><td><a name="diff005 6" /></td></tr>1058 <tr><td><a name="diff0054" /></td></tr> 1065 1059 <tr><td class="lineno" valign="top"></td><td class="lblock"> GMT = %x47.4D.54 ; "GMT", case<span class="delete">-</span>sensitive</td><td> </td><td class="rblock"> GMT = %x47.4D.54 ; "GMT", case<span class="insert"> </span>sensitive</td><td class="lineno" valign="top"></td></tr> 1066 1060 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1079 1073 <tr><td class="lineno" valign="top"></td><td class="left"> ; e.g., 02-Jun-82</td><td> </td><td class="right"> ; e.g., 02-Jun-82</td><td class="lineno" valign="top"></td></tr> 1080 1074 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1081 <tr><td><a name="diff005 7" /></td></tr>1075 <tr><td><a name="diff0055" /></td></tr> 1082 1076 <tr><td class="lineno" valign="top"></td><td class="lblock"> day-name-l = %x4D.6F.6E.64.61.79 ; "Monday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock"> day-name-l = %x4D.6F.6E.64.61.79 ; "Monday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr> 1083 1077 <tr><td class="lineno" valign="top"></td><td class="lblock"> / %x54.75.65.73.64.61.79 ; "Tuesday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock"> / %x54.75.65.73.64.61.79 ; "Tuesday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr> … … 1109 1103 <tr><td class="lineno" valign="top"></td><td class="left"> automatically redirecting the request.</td><td> </td><td class="right"> automatically redirecting the request.</td><td class="lineno" valign="top"></td></tr> 1110 1104 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1111 <tr><td><a name="diff005 8" /></td></tr>1105 <tr><td><a name="diff0056" /></td></tr> 1112 1106 <tr><td class="lineno" valign="top"></td><td class="lblock"> If the Location value provided in a 3xx (Redirection) does not have a</td><td> </td><td class="rblock"> If the Location value provided in a 3xx (Redirection) <span class="insert">response</span> does</td><td class="lineno" valign="top"></td></tr> 1113 1107 <tr><td class="lineno" valign="top"></td><td class="lblock"> fragment component, a user agent MUST process the redirection as if</td><td> </td><td class="rblock"> not have a fragment component, a user agent MUST process the</td><td class="lineno" valign="top"></td></tr> … … 1137 1131 <tr><td class="lineno" valign="top"></td><td class="left"> request target, might influence the origin server's process for</td><td> </td><td class="right"> request target, might influence the origin server's process for</td><td class="lineno" valign="top"></td></tr> 1138 1132 <tr><td class="lineno" valign="top"></td><td class="left"> selecting and representing this response. The value consists of</td><td> </td><td class="right"> selecting and representing this response. The value consists of</td><td class="lineno" valign="top"></td></tr> 1139 <tr><td><a name="diff005 9" /></td></tr>1133 <tr><td><a name="diff0057" /></td></tr> 1140 1134 <tr><td class="lineno" valign="top"></td><td class="lblock"> either a single asterisk ("*") or a list of header field names (case<span class="delete">-</span></td><td> </td><td class="rblock"> either a single asterisk ("*") or a list of header field names (case</td><td class="lineno" valign="top"></td></tr> 1141 1135 <tr><td class="lineno" valign="top"></td><td class="left"> insensitive).</td><td> </td><td class="right"> insensitive).</td><td class="lineno" valign="top"></td></tr> … … 1161 1155 <tr><td class="lineno" valign="top"></td><td class="left"> required to match a new request to the stored cache entry.</td><td> </td><td class="right"> required to match a new request to the stored cache entry.</td><td class="lineno" valign="top"></td></tr> 1162 1156 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1163 <tr><td><a name="diff00 60" /></td></tr>1157 <tr><td><a name="diff0058" /></td></tr> 1164 1158 <tr><td class="lineno" valign="top"></td><td class="lblock"> 2. To inform user<span class="delete"> </span>agent recipients that this response is subject to</td><td> </td><td class="rblock"> 2. To inform user<span class="insert">-</span>agent recipients that this response is subject to</td><td class="lineno" valign="top"></td></tr> 1165 1159 <tr><td class="lineno" valign="top"></td><td class="left"> content negotiation (Section 5.3) and that a different</td><td> </td><td class="right"> content negotiation (Section 5.3) and that a different</td><td class="lineno" valign="top"></td></tr> … … 1185 1179 <tr><td class="lineno" valign="top"></td><td class="left"> selected representation as a result of processing the request.</td><td> </td><td class="right"> selected representation as a result of processing the request.</td><td class="lineno" valign="top"></td></tr> 1186 1180 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1187 <tr><td><a name="diff00 61" /></td></tr>1181 <tr><td><a name="diff0059" /></td></tr> 1188 1182 <tr><td class="lineno" valign="top"></td><td class="lblock"> For example, an ETag header field in a 201 response communicates the</td><td> </td><td class="rblock"> For example, an ETag header field in a 201 <span class="insert">(Created)</span> response</td><td class="lineno" valign="top"></td></tr> 1189 1183 <tr><td class="lineno" valign="top"></td><td class="lblock"> entity-tag of the newly created resource's representation, so that it</td><td> </td><td class="rblock"> communicates the entity-tag of the newly created resource's</td><td class="lineno" valign="top"></td></tr> … … 1212 1206 <tr><td class="lineno" valign="top"></td><td class="left">8.1. Method Registry</td><td> </td><td class="right">8.1. Method Registry</td><td class="lineno" valign="top"></td></tr> 1213 1207 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1214 <tr><td><a name="diff006 2" /></td></tr>1208 <tr><td><a name="diff0060" /></td></tr> 1215 1209 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Method <span class="delete">Registry</span> defines the <span class="delete">name space</span> for the request</td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Method <span class="insert">Registry"</span> defines the</td><td class="lineno" valign="top"></td></tr> 1216 1210 <tr><td class="lineno" valign="top"></td><td class="lblock"> method token (Section 4). The <span class="delete">method registry will be</span> created and</td><td> </td><td class="rblock"> <span class="insert">namespace</span> for the request method token (Section 4). The <span class="insert">"HTTP Method</span></td><td class="lineno" valign="top"></td></tr> … … 1230 1224 <tr><td class="lineno" valign="top"></td><td class="left"> o Pointer to specification text</td><td> </td><td class="right"> o Pointer to specification text</td><td class="lineno" valign="top"></td></tr> 1231 1225 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1232 <tr><td><a name="diff006 3" /></td></tr>1226 <tr><td><a name="diff0061" /></td></tr> 1233 1227 <tr><td class="lineno" valign="top"></td><td class="lblock"> Values to be added to this name<span class="delete"> </span>space require IETF Review (see</td><td> </td><td class="rblock"> Values to be added to this namespace require IETF Review (see</td><td class="lineno" valign="top"></td></tr> 1234 1228 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC5226], Section 4.1).</td><td> </td><td class="right"> [RFC5226], Section 4.1).</td><td class="lineno" valign="top"></td></tr> … … 1252 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> 1253 1247 <tr><td class="lineno" valign="top"></td><td class="left"> A new method definition needs to indicate whether it is safe</td><td> </td><td class="right"> A new method definition needs to indicate whether it is safe</td><td class="lineno" valign="top"></td></tr> 1254 <tr><td><a name="diff006 4" /></td></tr>1248 <tr><td><a name="diff0062" /></td></tr> 1255 1249 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section 4.2.1), idempotent (Section 4.2.2), cacheable</td><td> </td><td class="rblock"> (Section 4.2.1), idempotent (Section 4.2.2), <span class="insert">or</span> cacheable</td><td class="lineno" valign="top"></td></tr> 1256 1250 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">4.2.3),</span> what semantics are to be associated with the payload</td><td> </td><td class="rblock"> (Section <span class="insert">4.2.3). It needs to indicate</span> what semantics are to be</td><td class="lineno" valign="top"></td></tr> … … 1271 1265 <tr><td class="lineno" valign="top"></td><td class="left">8.1.3. Registrations</td><td> </td><td class="right">8.1.3. Registrations</td><td class="lineno" valign="top"></td></tr> 1272 1266 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1273 <tr><td><a name="diff006 5" /></td></tr>1267 <tr><td><a name="diff0063" /></td></tr> 1274 1268 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Method <span class="delete">Registry shall be</span> populated with the registrations</td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Method <span class="insert">Registry" has been</span></td><td class="lineno" valign="top"></td></tr> 1275 1269 <tr><td class="lineno" valign="top"></td><td class="lblock"> below:</td><td> </td><td class="rblock"> populated with the registrations below:</td><td class="lineno" valign="top"></td></tr> … … 1290 1284 <tr><td class="lineno" valign="top"></td><td class="left">8.2. Status Code Registry</td><td> </td><td class="right">8.2. Status Code Registry</td><td class="lineno" valign="top"></td></tr> 1291 1285 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1292 <tr><td><a name="diff006 6" /></td></tr>1286 <tr><td><a name="diff0064" /></td></tr> 1293 1287 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Status Code <span class="delete">Registry</span> defines the <span class="delete">name space</span> for the response</td><td> </td><td class="rblock"> The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Status Code <span class="insert">Registry"</span> defines</td><td class="lineno" valign="top"></td></tr> 1294 1288 <tr><td class="lineno" valign="top"></td><td class="lblock"> status-code token (Section 6). The <span class="delete">status code</span> registry is</td><td> </td><td class="rblock"> the <span class="insert">namespace</span> for the response status-code token (Section 6). The</td><td class="lineno" valign="top"></td></tr> … … 1296 1290 <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"> <http://www.iana.org/assignments/http-status-codes>.</td><td class="lineno" valign="top"></td></tr> 1297 1291 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1298 <tr><td><a name="diff006 7" /></td></tr>1292 <tr><td><a name="diff0065" /></td></tr> 1299 1293 <tr><td class="lineno" valign="top"></td><td class="lblock"> This <span class="delete">S</span>ection replaces the registration procedure for HTTP Status</td><td> </td><td class="rblock"> This <span class="insert">s</span>ection replaces the registration procedure for HTTP Status</td><td class="lineno" valign="top"></td></tr> 1300 1294 <tr><td class="lineno" valign="top"></td><td class="left"> Codes previously defined in Section 7.1 of [RFC2817].</td><td> </td><td class="right"> Codes previously defined in Section 7.1 of [RFC2817].</td><td class="lineno" valign="top"></td></tr> … … 1310 1304 <tr><td class="lineno" valign="top"></td><td class="left"> o Pointer to specification text</td><td> </td><td class="right"> o Pointer to specification text</td><td class="lineno" valign="top"></td></tr> 1311 1305 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1312 <tr><td><a name="diff006 8" /></td></tr>1306 <tr><td><a name="diff0066" /></td></tr> 1313 1307 <tr><td class="lineno" valign="top"></td><td class="lblock"> Values to be added to the HTTP status code name<span class="delete"> </span>space require IETF</td><td> </td><td class="rblock"> Values to be added to the HTTP status code namespace require IETF</td><td class="lineno" valign="top"></td></tr> 1314 1308 <tr><td class="lineno" valign="top"></td><td class="left"> Review (see [RFC5226], Section 4.1).</td><td> </td><td class="right"> Review (see [RFC5226], Section 4.1).</td><td class="lineno" valign="top"></td></tr> … … 1334 1328 <tr><td class="lineno" valign="top"></td><td class="left">8.2.3. Registrations</td><td> </td><td class="right">8.2.3. Registrations</td><td class="lineno" valign="top"></td></tr> 1335 1329 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1336 <tr><td><a name="diff006 9" /></td></tr>1330 <tr><td><a name="diff0067" /></td></tr> 1337 1331 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Status <span class="delete">Code Registry shall be</span> updated with the registrations</td><td> </td><td class="rblock"> The <span class="insert">"HTTP</span> Status <span class="insert">Codes" registry has been</span> updated with the</td><td class="lineno" valign="top"></td></tr> 1338 1332 <tr><td class="lineno" valign="top"></td><td class="lblock"> below:</td><td> </td><td class="rblock"> registrations below:</td><td class="lineno" valign="top"></td></tr> … … 1359 1353 <tr><td class="lineno" valign="top"></td><td class="left">8.3. Header Field Registry</td><td> </td><td class="right">8.3. Header Field Registry</td><td class="lineno" valign="top"></td></tr> 1360 1354 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1361 <tr><td><a name="diff00 70" /></td></tr>1355 <tr><td><a name="diff0068" /></td></tr> 1362 1356 <tr><td class="lineno" valign="top"></td><td class="lblock"> HTTP header fields are registered within the <span class="delete">Message Header Field</span></td><td> </td><td class="rblock"> HTTP header fields are registered within the <span class="insert">"Message Headers"</span></td><td class="lineno" valign="top"></td></tr> 1363 1357 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> Registry</span> located at <span class="delete"><http://www.iana.org/assignments/message-headers/</span></td><td> </td><td class="rblock"><span class="insert"> registry</span> located at <span class="insert"><http://www.iana.org/assignments/message-headers></span></td><td class="lineno" valign="top"></td></tr> … … 1374 1368 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1375 1369 <tr><td class="lineno" valign="top"></td><td class="left"> Authors of specifications defining new fields are advised to keep the</td><td> </td><td class="right"> Authors of specifications defining new fields are advised to keep the</td><td class="lineno" valign="top"></td></tr> 1376 <tr><td><a name="diff00 71" /></td></tr>1370 <tr><td><a name="diff0069" /></td></tr> 1377 1371 <tr><td class="lineno" valign="top"></td><td class="lblock"> name as short as practical and <span class="delete">to not</span> prefix the name with "X-"</td><td> </td><td class="rblock"> name as short as practical and <span class="insert">not to</span> prefix the name with "X-"</td><td class="lineno" valign="top"></td></tr> 1378 1372 <tr><td class="lineno" valign="top"></td><td class="left"> unless the header field will never be used on the Internet. (The</td><td> </td><td class="right"> unless the header field will never be used on the Internet. (The</td><td class="lineno" valign="top"></td></tr> 1379 <tr><td><a name="diff007 2" /></td></tr>1373 <tr><td><a name="diff0070" /></td></tr> 1380 1374 <tr><td class="lineno" valign="top"></td><td class="lblock"> "<span class="delete">x</span>-" prefix idiom has been extensively misused in practice; it was</td><td> </td><td class="rblock"> "<span class="insert">X</span>-" prefix idiom has been extensively misused in practice; it was</td><td class="lineno" valign="top"></td></tr> 1381 1375 <tr><td class="lineno" valign="top"></td><td class="left"> intended to only be used as a mechanism for avoiding name collisions</td><td> </td><td class="right"> intended to only be used as a mechanism for avoiding name collisions</td><td class="lineno" valign="top"></td></tr> 1382 1376 <tr><td class="lineno" valign="top"></td><td class="left"> inside proprietary software or intranet processing, since the prefix</td><td> </td><td class="right"> inside proprietary software or intranet processing, since the prefix</td><td class="lineno" valign="top"></td></tr> 1383 1377 <tr><td class="lineno" valign="top"></td><td class="left"> would ensure that private names never collide with a newly registered</td><td> </td><td class="right"> would ensure that private names never collide with a newly registered</td><td class="lineno" valign="top"></td></tr> 1384 <tr><td><a name="diff007 3" /></td></tr>1378 <tr><td><a name="diff0071" /></td></tr> 1385 1379 <tr><td class="lineno" valign="top"></td><td class="lblock"> Internet name; see [BCP178] for further information)</td><td> </td><td class="rblock"> Internet name; see [BCP178] for further information)<span class="insert">.</span></td><td class="lineno" valign="top"></td></tr> 1386 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> 1387 1381 <tr><td class="lineno" valign="top"></td><td class="left"> New header field values typically have their syntax defined using</td><td> </td><td class="right"> New header field values typically have their syntax defined using</td><td class="lineno" valign="top"></td></tr> 1388 <tr><td><a name="diff007 4" /></td></tr>1382 <tr><td><a name="diff0072" /></td></tr> 1389 1383 <tr><td class="lineno" valign="top"></td><td class="lblock"> ABNF <span class="delete">([RFC5234]), using</span> the extension defined in Section 7 of</td><td> </td><td class="rblock"> ABNF <span class="insert">([RFC5234]) (implementing</span> the extension defined in Section 7 of</td><td class="lineno" valign="top"></td></tr> 1390 1384 <tr><td class="lineno" valign="top"></td><td class="lblock"> [RFC7230] as <span class="delete">necessary,</span> and are usually constrained to the range of</td><td> </td><td class="rblock"> [RFC7230] as <span class="insert">necessary),</span> and <span class="insert">they</span> are usually constrained to the</td><td class="lineno" valign="top"></td></tr> … … 1412 1406 <tr><td class="lineno" valign="top"></td><td class="left">8.3.2. Registrations</td><td> </td><td class="right">8.3.2. Registrations</td><td class="lineno" valign="top"></td></tr> 1413 1407 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1414 <tr><td><a name="diff007 5" /></td></tr>1408 <tr><td><a name="diff0073" /></td></tr> 1415 1409 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">Message Header Field Registry shall be</span> updated with the following</td><td> </td><td class="rblock"> The <span class="insert">"Message Headers" registry has been</span> updated with the following</td><td class="lineno" valign="top"></td></tr> 1416 1410 <tr><td class="lineno" valign="top"></td><td class="left"> permanent registrations:</td><td> </td><td class="right"> permanent registrations:</td><td class="lineno" valign="top"></td></tr> … … 1436 1430 <tr><td class="lineno" valign="top"></td><td class="left">8.4. Content Coding Registry</td><td> </td><td class="right">8.4. Content Coding Registry</td><td class="lineno" valign="top"></td></tr> 1437 1431 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1438 <tr><td><a name="diff007 6" /></td></tr>1432 <tr><td><a name="diff0074" /></td></tr> 1439 1433 <tr><td class="lineno" valign="top"></td><td class="lblock"> The <span class="delete">HTTP</span> Content Coding <span class="delete">Registry</span> defines the <span class="delete">name space</span> for content</td><td> </td><td class="rblock"> The <span class="insert">"HTTP</span> Content Coding <span class="insert">Registry"</span> defines the <span class="insert">namespace</span> for content</td><td class="lineno" valign="top"></td></tr> 1440 1434 <tr><td class="lineno" valign="top"></td><td class="lblock"> coding names (Section 4.2 of [RFC7230]). The <span class="delete">content coding registry</span></td><td> </td><td class="rblock"> coding names (Section 4.2 of [RFC7230]). The <span class="insert">"HTTP Content Coding</span></td><td class="lineno" valign="top"></td></tr> … … 1444 1438 <tr><td class="lineno" valign="top"></td><td class="left">8.4.1. Procedure</td><td> </td><td class="right">8.4.1. Procedure</td><td class="lineno" valign="top"></td></tr> 1445 1439 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1446 <tr><td><a name="diff007 7" /></td></tr>1440 <tr><td><a name="diff0075" /></td></tr> 1447 1441 <tr><td class="lineno" valign="top"></td><td class="lblock"> Content <span class="delete">C</span>oding registrations MUST include the following fields:</td><td> </td><td class="rblock"> Content <span class="insert">c</span>oding registrations MUST include the following fields:</td><td class="lineno" valign="top"></td></tr> 1448 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> … … 1458 1452 <tr><td class="lineno" valign="top"></td><td class="left"> Section 4.2 of [RFC7230]).</td><td> </td><td class="right"> Section 4.2 of [RFC7230]).</td><td class="lineno" valign="top"></td></tr> 1459 1453 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1460 <tr><td><a name="diff007 8" /></td></tr>1454 <tr><td><a name="diff0076" /></td></tr> 1461 1455 <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> 1462 1456 <tr><td class="lineno" valign="top"></td><td class="lblock"> Section 4.1 of <span class="delete">[RFC5226]),</span> and MUST conform to the purpose of content</td><td> </td><td class="rblock"> 4.1 of <span class="insert">[RFC5226])</span> and MUST conform to the purpose of content coding</td><td class="lineno" valign="top"></td></tr> … … 1465 1459 <tr><td class="lineno" valign="top"></td><td class="left">8.4.2. Registrations</td><td> </td><td class="right">8.4.2. Registrations</td><td class="lineno" valign="top"></td></tr> 1466 1460 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1467 <tr><td><a name="diff007 9" /></td></tr>1461 <tr><td><a name="diff0077" /></td></tr> 1468 1462 <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> 1469 1463 <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> … … 1486 1480 <tr><td class="lineno" valign="top"></td><td class="left"> The list of considerations below is not exhaustive. Most security</td><td> </td><td class="right"> The list of considerations below is not exhaustive. Most security</td><td class="lineno" valign="top"></td></tr> 1487 1481 <tr><td class="lineno" valign="top"></td><td class="left"> concerns related to HTTP semantics are about securing server-side</td><td> </td><td class="right"> concerns related to HTTP semantics are about securing server-side</td><td class="lineno" valign="top"></td></tr> 1488 <tr><td><a name="diff00 80" /></td></tr>1482 <tr><td><a name="diff0078" /></td></tr> 1489 1483 <tr><td class="lineno" valign="top"></td><td class="lblock"> applications (code behind the HTTP <span class="delete">interface),</span> securing <span class="delete">user agent</span></td><td> </td><td class="rblock"> applications (code behind the HTTP <span class="insert">interface) or</span> securing <span class="insert">user-agent</span></td><td class="lineno" valign="top"></td></tr> 1490 1484 <tr><td class="lineno" valign="top"></td><td class="lblock"> processing of payloads received via <span class="delete">HTTP, or secure</span> use of the</td><td> </td><td class="rblock"> processing of payloads received via <span class="insert">HTTP. Secure</span> use of the Internet</td><td class="lineno" valign="top"></td></tr> … … 1506 1500 <tr><td class="lineno" valign="top"></td><td class="left"> For example, UNIX, Microsoft Windows, and other operating systems use</td><td> </td><td class="right"> For example, UNIX, Microsoft Windows, and other operating systems use</td><td class="lineno" valign="top"></td></tr> 1507 1501 <tr><td class="lineno" valign="top"></td><td class="left"> ".." as a path component to indicate a directory level above the</td><td> </td><td class="right"> ".." as a path component to indicate a directory level above the</td><td class="lineno" valign="top"></td></tr> 1508 <tr><td><a name="diff00 81" /></td></tr>1502 <tr><td><a name="diff0079" /></td></tr> 1509 1503 <tr><td class="lineno" valign="top"></td><td class="lblock"> current one, and use specially named paths or file names to send data</td><td> </td><td class="rblock"> current one, and <span class="insert">they</span> use specially named paths or file names to send</td><td class="lineno" valign="top"></td></tr> 1510 1504 <tr><td class="lineno" valign="top"></td><td class="lblock"> to system devices. Similar naming conventions might exist within</td><td> </td><td class="rblock"> data to system devices. Similar naming conventions might exist</td><td class="lineno" valign="top"></td></tr> … … 1515 1509 <tr><td class="lineno" valign="top"></td><td class="lblock"> names.</td><td> </td><td class="rblock"> case-insensitive names.</td><td class="lineno" valign="top"></td></tr> 1516 1510 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1517 <tr><td><a name="diff008 2" /></td></tr>1511 <tr><td><a name="diff0080" /></td></tr> 1518 1512 <tr><td class="lineno" valign="top"></td><td class="lblock"> Attacks based on such special names tend to focus on either <span class="delete">denial-</span></td><td> </td><td class="rblock"> Attacks based on such special names tend to focus on either <span class="insert">denial of</span></td><td class="lineno" valign="top"></td></tr> 1519 1513 <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"> of-service</span> (e.g., telling the server to read from a COM port) or</td><td> </td><td class="rblock"><span class="insert"> service</span> (e.g., telling the server to read from a COM port) or</td><td class="lineno" valign="top"></td></tr> … … 1540 1534 <tr><td class="lineno" valign="top"></td><td class="left"> information about the user's immediate browsing history and any</td><td> </td><td class="right"> information about the user's immediate browsing history and any</td><td class="lineno" valign="top"></td></tr> 1541 1535 <tr><td class="lineno" valign="top"></td><td class="left"> personal information that might be found in the referring resource's</td><td> </td><td class="right"> personal information that might be found in the referring resource's</td><td class="lineno" valign="top"></td></tr> 1542 <tr><td><a name="diff008 3" /></td></tr>1536 <tr><td><a name="diff0081" /></td></tr> 1543 1537 <tr><td class="lineno" valign="top"></td><td class="lblock"> URI. Limitations on Referer are described in Section 5.5.2 to</td><td> </td><td class="rblock"> URI. Limitations on <span class="insert">the</span> Referer <span class="insert">header field</span> are described in</td><td class="lineno" valign="top"></td></tr> 1544 1538 <tr><td class="lineno" valign="top"></td><td class="lblock"> address some of its security considerations.</td><td> </td><td class="rblock"> Section 5.5.2 to address some of its security considerations.</td><td class="lineno" valign="top"></td></tr> … … 1565 1559 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right"> [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr> 1566 1560 <tr><td class="lineno" valign="top"></td><td class="left"> Protocol (HTTP/1.1): Message Syntax and Routing",</td><td> </td><td class="right"> Protocol (HTTP/1.1): Message Syntax and Routing",</td><td class="lineno" valign="top"></td></tr> 1567 <tr><td><a name="diff008 4" /></td></tr>1561 <tr><td><a name="diff0082" /></td></tr> 1568 1562 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p1-messaging-latest (work in progress),</span></td><td> </td><td class="rblock"> <span class="insert">RFC 7230,</span> May 2014.</td><td class="lineno" valign="top"></td></tr> 1569 1563 <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> 1570 1564 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1571 1565 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7232] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right"> [RFC7232] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr> 1572 <tr><td><a name="diff008 5" /></td></tr>1566 <tr><td><a name="diff0083" /></td></tr> 1573 1567 <tr><td class="lineno" valign="top"></td><td class="lblock"> Protocol (HTTP/1.1): Conditional Requests",</td><td> </td><td class="rblock"> Protocol (HTTP/1.1): Conditional Requests", <span class="insert">RFC 7232,</span></td><td class="lineno" valign="top"></td></tr> 1574 1568 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p4-conditional-latest (work in</span></td><td> </td><td class="rblock"> May 2014.</td><td class="lineno" valign="top"></td></tr> … … 1577 1571 <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> 1578 1572 <tr><td class="lineno" valign="top"></td><td class="left"> "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",</td><td> </td><td class="right"> "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",</td><td class="lineno" valign="top"></td></tr> 1579 <tr><td><a name="diff008 6" /></td></tr>1573 <tr><td><a name="diff0084" /></td></tr> 1580 1574 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p5-range-latest (work in progress),</span></td><td> </td><td class="rblock"> <span class="insert">RFC 7233,</span> May 2014.</td><td class="lineno" valign="top"></td></tr> 1581 1575 <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> … … 1583 1577 <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> 1584 1578 <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> 1585 <tr><td><a name="diff008 7" /></td></tr>1579 <tr><td><a name="diff0085" /></td></tr> 1586 1580 <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> 1587 1581 <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> 1588 1582 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1589 1583 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7235] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right"> [RFC7235] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr> 1590 <tr><td><a name="diff008 8" /></td></tr>1584 <tr><td><a name="diff0086" /></td></tr> 1591 1585 <tr><td class="lineno" valign="top"></td><td class="lblock"> Protocol (HTTP/1.1): Authentication",</td><td> </td><td class="rblock"> Protocol (HTTP/1.1): Authentication", <span class="insert">RFC 7235,</span> May 2014.</td><td class="lineno" valign="top"></td></tr> 1592 1586 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-ietf-httpbis-p7-auth-latest (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> … … 1614 1608 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1615 1609 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7238] Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td> </td><td class="right"> [RFC7238] Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td class="lineno" valign="top"></td></tr> 1616 <tr><td><a name="diff008 9" /></td></tr>1610 <tr><td><a name="diff0087" /></td></tr> 1617 1611 <tr><td class="lineno" valign="top"></td><td class="lblock"> Status Code 308 (Permanent Redirect)",</td><td> </td><td class="rblock"> Status Code 308 (Permanent Redirect)", <span class="insert">RFC 7238, May 2014.</span></td><td class="lineno" valign="top"></td></tr> 1618 1612 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">draft-reschke-http-status-308-07 (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> … … 1626 1620 <tr><td class="lineno" valign="top"></td><td class="left"> variety of representations and with extensible header fields.</td><td> </td><td class="right"> variety of representations and with extensible header fields.</td><td class="lineno" valign="top"></td></tr> 1627 1621 <tr><td class="lineno" valign="top"></td><td class="left"> However, RFC 2045 is focused only on email; applications of HTTP have</td><td> </td><td class="right"> However, RFC 2045 is focused only on email; applications of HTTP have</td><td class="lineno" valign="top"></td></tr> 1628 <tr><td><a name="diff00 90" /></td></tr>1622 <tr><td><a name="diff0088" /></td></tr> 1629 1623 <tr><td class="lineno" valign="top"></td><td class="lblock"> many characteristics that differ from <span class="delete">email, and hence</span> HTTP has</td><td> </td><td class="rblock"> many characteristics that differ from <span class="insert">email; hence,</span> HTTP has features</td><td class="lineno" valign="top"></td></tr> 1630 1624 <tr><td class="lineno" valign="top"></td><td class="lblock"> features that differ from MIME. These differences were carefully</td><td> </td><td class="rblock"> that differ from MIME. These differences were carefully chosen to</td><td class="lineno" valign="top"></td></tr> … … 1655 1649 <tr><td class="lineno" valign="top"></td><td class="left"> likelihood of safe transport over the destination protocol.</td><td> </td><td class="right"> likelihood of safe transport over the destination protocol.</td><td class="lineno" valign="top"></td></tr> 1656 1650 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1657 <tr><td><a name="diff00 91" /></td></tr>1651 <tr><td><a name="diff0089" /></td></tr> 1658 1652 <tr><td class="lineno" valign="top"></td><td class="lblock">A.6. MHTML and Line<span class="delete"> </span>Length Limitations</td><td> </td><td class="rblock">A.6. MHTML and Line<span class="insert">-</span>Length Limitations</td><td class="lineno" valign="top"></td></tr> 1659 1653 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1660 1654 <tr><td class="lineno" valign="top"></td><td class="left"> HTTP implementations that share code with MHTML [RFC2557]</td><td> </td><td class="right"> HTTP implementations that share code with MHTML [RFC2557]</td><td class="lineno" valign="top"></td></tr> 1661 <tr><td><a name="diff009 2" /></td></tr>1655 <tr><td><a name="diff0090" /></td></tr> 1662 1656 <tr><td class="lineno" valign="top"></td><td class="lblock"> implementations need to be aware of MIME line<span class="delete"> </span>length limitations.</td><td> </td><td class="rblock"> implementations need to be aware of MIME line<span class="insert">-</span>length limitations.</td><td class="lineno" valign="top"></td></tr> 1663 1657 <tr><td class="lineno" valign="top"></td><td class="left"> Since HTTP does not have this limitation, HTTP does not fold long</td><td> </td><td class="right"> Since HTTP does not have this limitation, HTTP does not fold long</td><td class="lineno" valign="top"></td></tr> 1664 1658 <tr><td class="lineno" valign="top"></td><td class="left"> lines. MHTML messages being transported by HTTP follow all</td><td> </td><td class="right"> lines. MHTML messages being transported by HTTP follow all</td><td class="lineno" valign="top"></td></tr> 1665 <tr><td><a name="diff009 3" /></td></tr>1659 <tr><td><a name="diff0091" /></td></tr> 1666 1660 <tr><td class="lineno" valign="top"></td><td class="lblock"> conventions of MHTML, including line<span class="delete"> </span>length limitations and folding,</td><td> </td><td class="rblock"> conventions of MHTML, including line<span class="insert">-</span>length limitations and folding,</td><td class="lineno" valign="top"></td></tr> 1667 1661 <tr><td class="lineno" valign="top"></td><td class="left"> canonicalization, etc., since HTTP transfers message-bodies as</td><td> </td><td class="right"> canonicalization, etc., since HTTP transfers message-bodies as</td><td class="lineno" valign="top"></td></tr> … … 1680 1674 <tr><td class="lineno" valign="top"></td><td class="left"> representations and representations from resources.</td><td> </td><td class="right"> representations and representations from resources.</td><td class="lineno" valign="top"></td></tr> 1681 1675 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1682 <tr><td><a name="diff009 4" /></td></tr>1676 <tr><td><a name="diff0092" /></td></tr> 1683 1677 <tr><td class="lineno" valign="top"></td><td class="lblock"> A new requirement has been added that semantics embedded in a URI</td><td> </td><td class="rblock"> A new requirement has been added that semantics embedded in a URI be</td><td class="lineno" valign="top"></td></tr> 1684 1678 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">should</span> be disabled when those semantics are inconsistent with the</td><td> </td><td class="rblock"> disabled when those semantics are inconsistent with the request</td><td class="lineno" valign="top"></td></tr> … … 1687 1681 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1688 1682 <tr><td class="lineno" valign="top"></td><td class="left"> An algorithm has been added for determining if a payload is</td><td> </td><td class="right"> An algorithm has been added for determining if a payload is</td><td class="lineno" valign="top"></td></tr> 1689 <tr><td><a name="diff009 5" /></td></tr>1683 <tr><td><a name="diff0093" /></td></tr> 1690 1684 <tr><td class="lineno" valign="top"></td><td class="lblock"> associated with a specific identifier<span class="delete">. (Section 3.1.4.1)</span></td><td> </td><td class="rblock"> associated with a specific identifier<span class="insert"> (Section 3.1.4.1).</span></td><td class="lineno" valign="top"></td></tr> 1691 1685 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1693 1687 <tr><td class="lineno" valign="top"></td><td class="left"> removed; the default is now whatever the media type definition says.</td><td> </td><td class="right"> removed; the default is now whatever the media type definition says.</td><td class="lineno" valign="top"></td></tr> 1694 1688 <tr><td class="lineno" valign="top"></td><td class="left"> Likewise, special treatment of ISO-8859-1 has been removed from the</td><td> </td><td class="right"> Likewise, special treatment of ISO-8859-1 has been removed from the</td><td class="lineno" valign="top"></td></tr> 1695 <tr><td><a name="diff009 6" /></td></tr>1689 <tr><td><a name="diff0094" /></td></tr> 1696 1690 <tr><td class="lineno" valign="top"></td><td class="lblock"> Accept-Charset header field. (Section<span class="delete"> 3.1.1.3 and Section 5.3.3</span>)</td><td> </td><td class="rblock"> Accept-Charset header field. (Section<span class="insert">s 3.1.1.3 and 5.3.3.</span>)</td><td class="lineno" valign="top"></td></tr> 1697 1691 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1699 1693 <tr><td class="lineno" valign="top"></td><td class="left"> affect the base URI for resolving relative URI references, due to</td><td> </td><td class="right"> affect the base URI for resolving relative URI references, due to</td><td class="lineno" valign="top"></td></tr> 1700 1694 <tr><td class="lineno" valign="top"></td><td class="left"> poor implementation support and the undesirable effect of potentially</td><td> </td><td class="right"> poor implementation support and the undesirable effect of potentially</td><td class="lineno" valign="top"></td></tr> 1701 <tr><td><a name="diff009 7" /></td></tr>1695 <tr><td><a name="diff0095" /></td></tr> 1702 1696 <tr><td class="lineno" valign="top"></td><td class="lblock"> breaking relative links in content-negotiated <span class="delete">resources.</span></td><td> </td><td class="rblock"> breaking relative links in content-negotiated <span class="insert">resources</span></td><td class="lineno" valign="top"></td></tr> 1703 1697 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">3.1.4.2)</span></td><td> </td><td class="rblock"> (Section <span class="insert">3.1.4.2).</span></td><td class="lineno" valign="top"></td></tr> … … 1705 1699 <tr><td class="lineno" valign="top"></td><td class="left"> To be consistent with the method-neutral parsing algorithm of</td><td> </td><td class="right"> To be consistent with the method-neutral parsing algorithm of</td><td class="lineno" valign="top"></td></tr> 1706 1700 <tr><td class="lineno" valign="top"></td><td class="left"> [RFC7230], the definition of GET has been relaxed so that requests</td><td> </td><td class="right"> [RFC7230], the definition of GET has been relaxed so that requests</td><td class="lineno" valign="top"></td></tr> 1707 <tr><td><a name="diff009 8" /></td></tr>1701 <tr><td><a name="diff0096" /></td></tr> 1708 1702 <tr><td class="lineno" valign="top"></td><td class="lblock"> can have a body, even though a body has no meaning for <span class="delete">GET.</span></td><td> </td><td class="rblock"> can have a body, even though a body has no meaning for <span class="insert">GET</span></td><td class="lineno" valign="top"></td></tr> 1709 1703 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">4.3.1)</span></td><td> </td><td class="rblock"> (Section <span class="insert">4.3.1).</span></td><td class="lineno" valign="top"></td></tr> 1710 1704 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1711 1705 <tr><td class="lineno" valign="top"></td><td class="left"> Servers are no longer required to handle all Content-* header fields</td><td> </td><td class="right"> Servers are no longer required to handle all Content-* header fields</td><td class="lineno" valign="top"></td></tr> 1712 <tr><td><a name="diff009 9" /></td></tr>1706 <tr><td><a name="diff0097" /></td></tr> 1713 1707 <tr><td class="lineno" valign="top"></td><td class="lblock"> and use of Content-Range has been explicitly banned in PUT <span class="delete">requests.</span></td><td> </td><td class="rblock"> and use of Content-Range has been explicitly banned in PUT <span class="insert">requests</span></td><td class="lineno" valign="top"></td></tr> 1714 1708 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">4.3.4)</span></td><td> </td><td class="rblock"> (Section <span class="insert">4.3.4).</span></td><td class="lineno" valign="top"></td></tr> 1715 1709 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1716 1710 <tr><td class="lineno" valign="top"></td><td class="left"> Definition of the CONNECT method has been moved from [RFC2817] to</td><td> </td><td class="right"> Definition of the CONNECT method has been moved from [RFC2817] to</td><td class="lineno" valign="top"></td></tr> 1717 <tr><td><a name="diff0 100" /></td></tr>1711 <tr><td><a name="diff0098" /></td></tr> 1718 1712 <tr><td class="lineno" valign="top"></td><td class="lblock"> this specification<span class="delete">. (Section 4.3.6)</span></td><td> </td><td class="rblock"> this specification<span class="insert"> (Section 4.3.6).</span></td><td class="lineno" valign="top"></td></tr> 1719 1713 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1720 <tr><td><a name="diff0 101" /></td></tr>1714 <tr><td><a name="diff0099" /></td></tr> 1721 1715 <tr><td class="lineno" valign="top"></td><td class="lblock"> The OPTIONS and TRACE request methods have been defined as being</td><td> </td><td class="rblock"> The OPTIONS and TRACE request methods have been defined as being <span class="insert">safe</span></td><td class="lineno" valign="top"></td></tr> 1722 1716 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">safe.</span> (Section 4.3.7 and Section <span class="delete">4.3.8)</span></td><td> </td><td class="rblock"> (Section 4.3.7 and Section <span class="insert">4.3.8).</span></td><td class="lineno" valign="top"></td></tr> 1723 1717 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1724 1718 <tr><td class="lineno" valign="top"></td><td class="left"> The Expect header field's extension mechanism has been removed due to</td><td> </td><td class="right"> The Expect header field's extension mechanism has been removed due to</td><td class="lineno" valign="top"></td></tr> 1725 <tr><td><a name="diff010 2" /></td></tr>1719 <tr><td><a name="diff0100" /></td></tr> 1726 1720 <tr><td class="lineno" valign="top"></td><td class="lblock"> widely<span class="delete">-deployed broken implementations. (Section 5.1.1)</span></td><td> </td><td class="rblock"> widely<span class="insert"> deployed broken implementations (Section 5.1.1).</span></td><td class="lineno" valign="top"></td></tr> 1727 1721 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1728 1722 <tr><td class="lineno" valign="top"></td><td class="left"> The Max-Forwards header field has been restricted to the OPTIONS and</td><td> </td><td class="right"> The Max-Forwards header field has been restricted to the OPTIONS and</td><td class="lineno" valign="top"></td></tr> 1729 1723 <tr><td class="lineno" valign="top"></td><td class="left"> TRACE methods; previously, extension methods could have used it as</td><td> </td><td class="right"> TRACE methods; previously, extension methods could have used it as</td><td class="lineno" valign="top"></td></tr> 1730 <tr><td><a name="diff010 3" /></td></tr>1724 <tr><td><a name="diff0101" /></td></tr> 1731 1725 <tr><td class="lineno" valign="top"></td><td class="lblock"> well<span class="delete">. (Section 5.1.2)</span></td><td> </td><td class="rblock"> well<span class="insert"> (Section 5.1.2).</span></td><td class="lineno" valign="top"></td></tr> 1732 1726 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1734 1728 <tr><td class="lineno" valign="top"></td><td class="left"> header field when no referring URI is applicable, which distinguishes</td><td> </td><td class="right"> header field when no referring URI is applicable, which distinguishes</td><td class="lineno" valign="top"></td></tr> 1735 1729 <tr><td class="lineno" valign="top"></td><td class="left"> that case from others where the Referer field is not sent or has been</td><td> </td><td class="right"> that case from others where the Referer field is not sent or has been</td><td class="lineno" valign="top"></td></tr> 1736 <tr><td><a name="diff010 4" /></td></tr>1730 <tr><td><a name="diff0102" /></td></tr> 1737 1731 <tr><td class="lineno" valign="top"></td><td class="lblock"> removed<span class="delete">. (Section 5.5.2)</span></td><td> </td><td class="rblock"> removed<span class="insert"> (Section 5.5.2).</span></td><td class="lineno" valign="top"></td></tr> 1738 1732 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1739 1733 <tr><td class="lineno" valign="top"></td><td class="left"> The following status codes are now cacheable (that is, they can be</td><td> </td><td class="right"> The following status codes are now cacheable (that is, they can be</td><td class="lineno" valign="top"></td></tr> 1740 1734 <tr><td class="lineno" valign="top"></td><td class="left"> stored and reused by a cache without explicit freshness information</td><td> </td><td class="right"> stored and reused by a cache without explicit freshness information</td><td class="lineno" valign="top"></td></tr> 1741 <tr><td><a name="diff010 5" /></td></tr>1735 <tr><td><a name="diff0103" /></td></tr> 1742 1736 <tr><td class="lineno" valign="top"></td><td class="lblock"> present): 204, 404, 405, 414, 501<span class="delete">. (Section 6)</span></td><td> </td><td class="rblock"> present): 204, 404, 405, 414, 501<span class="insert"> (Section 6).</span></td><td class="lineno" valign="top"></td></tr> 1743 1737 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1744 1738 <tr><td class="lineno" valign="top"></td><td class="left"> The 201 (Created) status description has been changed to allow for</td><td> </td><td class="right"> The 201 (Created) status description has been changed to allow for</td><td class="lineno" valign="top"></td></tr> 1745 <tr><td><a name="diff010 6" /></td></tr>1739 <tr><td><a name="diff0104" /></td></tr> 1746 1740 <tr><td class="lineno" valign="top"></td><td class="lblock"> the possibility that more than one resource has been <span class="delete">created.</span></td><td> </td><td class="rblock"> the possibility that more than one resource has been <span class="insert">created</span></td><td class="lineno" valign="top"></td></tr> 1747 1741 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">6.3.2)</span></td><td> </td><td class="rblock"> (Section <span class="insert">6.3.2).</span></td><td class="lineno" valign="top"></td></tr> 1748 1742 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1749 1743 <tr><td class="lineno" valign="top"></td><td class="left"> The definition of 203 (Non-Authoritative Information) has been</td><td> </td><td class="right"> The definition of 203 (Non-Authoritative Information) has been</td><td class="lineno" valign="top"></td></tr> 1750 <tr><td><a name="diff010 7" /></td></tr>1744 <tr><td><a name="diff0105" /></td></tr> 1751 1745 <tr><td class="lineno" valign="top"></td><td class="lblock"> broadened to include cases of payload transformations as <span class="delete">well.</span></td><td> </td><td class="rblock"> broadened to include cases of payload transformations as <span class="insert">well</span></td><td class="lineno" valign="top"></td></tr> 1752 1746 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">6.3.4)</span></td><td> </td><td class="rblock"> (Section <span class="insert">6.3.4).</span></td><td class="lineno" valign="top"></td></tr> … … 1756 1750 <tr><td class="lineno" valign="top"></td><td class="left"> based upon the request method semantics. The redirect status codes</td><td> </td><td class="right"> based upon the request method semantics. The redirect status codes</td><td class="lineno" valign="top"></td></tr> 1757 1751 <tr><td class="lineno" valign="top"></td><td class="left"> 301, 302, and 307 no longer have normative requirements on response</td><td> </td><td class="right"> 301, 302, and 307 no longer have normative requirements on response</td><td class="lineno" valign="top"></td></tr> 1752 <tr><td><a name="diff0106" /></td></tr> 1753 <tr><td class="lineno" valign="top"></td><td class="lblock"> payloads and user interaction<span class="delete">. (Section 6.4)</span></td><td> </td><td class="rblock"> payloads and user interaction<span class="insert"> (Section 6.4).</span></td><td class="lineno" valign="top"></td></tr> 1754 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1755 <tr><td class="lineno" valign="top"></td><td class="left"> The status codes 301 and 302 have been changed to allow user agents</td><td> </td><td class="right"> The status codes 301 and 302 have been changed to allow user agents</td><td class="lineno" valign="top"></td></tr> 1756 <tr><td><a name="diff0107" /></td></tr> 1757 <tr><td class="lineno" valign="top"></td><td class="lblock"> to rewrite the method from POST to GET. (Sections 6.4.2 and 6.4.3)</td><td> </td><td class="rblock"> to rewrite the method from POST to GET. (Sections 6.4.2 and 6.4.3<span class="insert">.</span>)</td><td class="lineno" valign="top"></td></tr> 1758 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1758 1759 <tr><td><a name="diff0108" /></td></tr> 1759 <tr><td class="lineno" valign="top"></td><td class="lblock"> payloads and user interaction<span class="delete">. (Section 6.4)</span></td><td> </td><td class="rblock"> payloads and user interaction<span class="insert"> (Section 6.4).</span></td><td class="lineno" valign="top"></td></tr>1760 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1761 <tr><td class="lineno" valign="top"></td><td class="left"> The status codes 301 and 302 have been changed to allow user agents</td><td> </td><td class="right"> The status codes 301 and 302 have been changed to allow user agents</td><td class="lineno" valign="top"></td></tr>1762 <tr><td><a name="diff0109" /></td></tr>1763 <tr><td class="lineno" valign="top"></td><td class="lblock"> to rewrite the method from POST to GET. (Sections 6.4.2 and 6.4.3)</td><td> </td><td class="rblock"> to rewrite the method from POST to GET. (Sections 6.4.2 and 6.4.3<span class="insert">.</span>)</td><td class="lineno" valign="top"></td></tr>1764 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1765 <tr><td><a name="diff0110" /></td></tr>1766 1760 <tr><td class="lineno" valign="top"></td><td class="lblock"> The description of 303 (See Other) status code has been changed to</td><td> </td><td class="rblock"> The description of <span class="insert">the</span> 303 (See Other) status code has been changed</td><td class="lineno" valign="top"></td></tr> 1767 1761 <tr><td class="lineno" valign="top"></td><td class="lblock"> allow it to be cached if explicit freshness information is given, and</td><td> </td><td class="rblock"> to allow it to be cached if explicit freshness information is given,</td><td class="lineno" valign="top"></td></tr> … … 1770 1764 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1771 1765 <tr><td class="lineno" valign="top"></td><td class="left"> The 305 (Use Proxy) status code has been deprecated due to security</td><td> </td><td class="right"> The 305 (Use Proxy) status code has been deprecated due to security</td><td class="lineno" valign="top"></td></tr> 1766 <tr><td><a name="diff0109" /></td></tr> 1767 <tr><td class="lineno" valign="top"></td><td class="lblock"> concerns regarding in-band configuration of a proxy<span class="delete">. (Section 6.4.5)</span></td><td> </td><td class="rblock"> concerns regarding in-band configuration of a proxy<span class="insert"> (Section 6.4.5).</span></td><td class="lineno" valign="top"></td></tr> 1768 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1769 <tr><td class="lineno" valign="top"></td><td class="left"> The 400 (Bad Request) status code has been relaxed so that it isn't</td><td> </td><td class="right"> The 400 (Bad Request) status code has been relaxed so that it isn't</td><td class="lineno" valign="top"></td></tr> 1770 <tr><td><a name="diff0110" /></td></tr> 1771 <tr><td class="lineno" valign="top"></td><td class="lblock"> limited to syntax errors<span class="delete">. (Section 6.5.1)</span></td><td> </td><td class="rblock"> limited to syntax errors<span class="insert"> (Section 6.5.1).</span></td><td class="lineno" valign="top"></td></tr> 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> 1773 <tr><td class="lineno" valign="top"></td><td class="left"> The 426 (Upgrade Required) status code has been incorporated from</td><td> </td><td class="right"> The 426 (Upgrade Required) status code has been incorporated from</td><td class="lineno" valign="top"></td></tr> 1772 1774 <tr><td><a name="diff0111" /></td></tr> 1773 <tr><td class="lineno" valign="top"></td><td class="lblock"> concerns regarding in-band configuration of a proxy<span class="delete">. (Section 6.4.5)</span></td><td> </td><td class="rblock"> concerns regarding in-band configuration of a proxy<span class="insert"> (Section 6.4.5).</span></td><td class="lineno" valign="top"></td></tr>1774 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1775 <tr><td class="lineno" valign="top"></td><td class="left"> The 400 (Bad Request) status code has been relaxed so that it isn't</td><td> </td><td class="right"> The 400 (Bad Request) status code has been relaxed so that it isn't</td><td class="lineno" valign="top"></td></tr>1776 <tr><td><a name="diff0112" /></td></tr>1777 <tr><td class="lineno" valign="top"></td><td class="lblock"> limited to syntax errors<span class="delete">. (Section 6.5.1)</span></td><td> </td><td class="rblock"> limited to syntax errors<span class="insert"> (Section 6.5.1).</span></td><td class="lineno" valign="top"></td></tr>1778 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1779 <tr><td class="lineno" valign="top"></td><td class="left"> The 426 (Upgrade Required) status code has been incorporated from</td><td> </td><td class="right"> The 426 (Upgrade Required) status code has been incorporated from</td><td class="lineno" valign="top"></td></tr>1780 <tr><td><a name="diff0113" /></td></tr>1781 1775 <tr><td class="lineno" valign="top"></td><td class="lblock"> [RFC2817]<span class="delete">. (Section 6.5.15)</span></td><td> </td><td class="rblock"> [RFC2817]<span class="insert"> (Section 6.5.15).</span></td><td class="lineno" valign="top"></td></tr> 1782 1776 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1783 1777 <tr><td class="lineno" valign="top"></td><td class="left"> The target of requirements on HTTP-date and the Date header field</td><td> </td><td class="right"> The target of requirements on HTTP-date and the Date header field</td><td class="lineno" valign="top"></td></tr> 1784 1778 <tr><td class="lineno" valign="top"></td><td class="left"> have been reduced to those systems generating the date, rather than</td><td> </td><td class="right"> have been reduced to those systems generating the date, rather than</td><td class="lineno" valign="top"></td></tr> 1785 <tr><td><a name="diff011 4" /></td></tr>1779 <tr><td><a name="diff0112" /></td></tr> 1786 1780 <tr><td class="lineno" valign="top"></td><td class="lblock"> all systems sending a date<span class="delete">. (Section 7.1.1)</span></td><td> </td><td class="rblock"> all systems sending a date<span class="insert"> (Section 7.1.1).</span></td><td class="lineno" valign="top"></td></tr> 1787 1781 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1789 1783 <tr><td class="lineno" valign="top"></td><td class="left"> URI references, including relative references and fragments, along</td><td> </td><td class="right"> URI references, including relative references and fragments, along</td><td class="lineno" valign="top"></td></tr> 1790 1784 <tr><td class="lineno" valign="top"></td><td class="left"> with some clarifications as to when use of fragments would not be</td><td> </td><td class="right"> with some clarifications as to when use of fragments would not be</td><td class="lineno" valign="top"></td></tr> 1791 <tr><td><a name="diff011 5" /></td></tr>1785 <tr><td><a name="diff0113" /></td></tr> 1792 1786 <tr><td class="lineno" valign="top"></td><td class="lblock"> appropriate<span class="delete">. (Section 7.1.2)</span></td><td> </td><td class="rblock"> appropriate<span class="insert"> (Section 7.1.2).</span></td><td class="lineno" valign="top"></td></tr> 1793 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> … … 1795 1789 <tr><td class="lineno" valign="top"></td><td class="left"> option to specify it in a PUT request. Requirements relating to the</td><td> </td><td class="right"> option to specify it in a PUT request. Requirements relating to the</td><td class="lineno" valign="top"></td></tr> 1796 1790 <tr><td class="lineno" valign="top"></td><td class="left"> content of Allow have been relaxed; correspondingly, clients are not</td><td> </td><td class="right"> content of Allow have been relaxed; correspondingly, clients are not</td><td class="lineno" valign="top"></td></tr> 1791 <tr><td><a name="diff0114" /></td></tr> 1792 <tr><td class="lineno" valign="top"></td><td class="lblock"> required to always trust its value<span class="delete">. (Section 7.4.1)</span></td><td> </td><td class="rblock"> required to always trust its value<span class="insert"> (Section 7.4.1).</span></td><td class="lineno" valign="top"></td></tr> 1793 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1794 <tr><td><a name="diff0115" /></td></tr> 1795 <tr><td class="lineno" valign="top"></td><td class="lblock"> A Method Registry has been defined<span class="delete">. (Section 8.1)</span></td><td> </td><td class="rblock"> A Method Registry has been defined<span class="insert"> (Section 8.1).</span></td><td class="lineno" valign="top"></td></tr> 1796 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1797 <tr><td class="lineno" valign="top"></td><td class="left"> The Status Code Registry has been redefined by this specification;</td><td> </td><td class="right"> The Status Code Registry has been redefined by this specification;</td><td class="lineno" valign="top"></td></tr> 1797 1798 <tr><td><a name="diff0116" /></td></tr> 1798 <tr><td class="lineno" valign="top"></td><td class="lblock"> required to always trust its value<span class="delete">. (Section 7.4.1)</span></td><td> </td><td class="rblock"> required to always trust its value<span class="insert"> (Section 7.4.1).</span></td><td class="lineno" valign="top"></td></tr>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>1800 <tr><td><a name="diff0117" /></td></tr>1801 <tr><td class="lineno" valign="top"></td><td class="lblock"> A Method Registry has been defined<span class="delete">. (Section 8.1)</span></td><td> </td><td class="rblock"> A Method Registry has been defined<span class="insert"> (Section 8.1).</span></td><td class="lineno" valign="top"></td></tr>1802 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>1803 <tr><td class="lineno" valign="top"></td><td class="left"> The Status Code Registry has been redefined by this specification;</td><td> </td><td class="right"> The Status Code Registry has been redefined by this specification;</td><td class="lineno" valign="top"></td></tr>1804 <tr><td><a name="diff0118" /></td></tr>1805 1799 <tr><td class="lineno" valign="top"></td><td class="lblock"> previously, it was defined in Section 7.1 of <span class="delete">[RFC2817].</span></td><td> </td><td class="rblock"> previously, it was defined in Section 7.1 of <span class="insert">[RFC2817]</span> (Section <span class="insert">8.2).</span></td><td class="lineno" valign="top"></td></tr> 1806 1800 <tr><td class="lineno" valign="top"></td><td class="lblock"> </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> 1807 1801 <tr><td class="lineno" valign="top"></td><td class="lblock"> (Section <span class="delete">8.2)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr> 1808 1802 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> 1809 <tr><td><a name="diff011 9" /></td></tr>1803 <tr><td><a name="diff0117" /></td></tr> 1810 1804 <tr><td class="lineno" valign="top"></td><td class="lblock"> Registration of <span class="delete">Content Codings</span> has been changed to require IETF</td><td> </td><td class="rblock"> Registration of <span class="insert">content codings</span> has been changed to require IETF</td><td class="lineno" valign="top"></td></tr> 1811 1805 <tr><td class="lineno" valign="top"></td><td class="lblock"> <span class="delete">Review.</span> (Section <span class="delete">8.4)</span></td><td> </td><td class="rblock"> <span class="insert">Review</span> (Section <span class="insert">8.4).</span></td><td class="lineno" valign="top"></td></tr> … … 1832 1826 <tr><td class="lineno" valign="top"></td><td class="left"> M</td><td> </td><td class="right"> M</td><td class="lineno" valign="top"></td></tr> 1833 1827 <tr><td class="lineno" valign="top"></td><td class="left"> Max-Forwards header field 36</td><td> </td><td class="right"> Max-Forwards header field 36</td><td class="lineno" valign="top"></td></tr> 1834 <tr><td><a name="diff01 20" /></td></tr>1828 <tr><td><a name="diff0118" /></td></tr> 1835 1829 <tr><td class="lineno" valign="top"></td><td class="lblock"> MIME-Version header field 8<span class="delete">9</span></td><td> </td><td class="rblock"> MIME-Version header field 8<span class="insert">8</span></td><td class="lineno" valign="top"></td></tr> 1836 1830 <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr> … … 1846 1840 1847 1841 <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr> 1848 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 1 20change blocks. </a></th></tr>1849 <tr class="stats"><td></td><th><i>2 93 lines changed or deleted</i></th><th><i> </i></th><th><i>269lines changed or added</i></th><td></td></tr>1842 <tr bgcolor="gray"><th colspan="5" align="center"><a name="end"> End of changes. 118 change blocks. </a></th></tr> 1843 <tr class="stats"><td></td><th><i>289 lines changed or deleted</i></th><th><i> </i></th><th><i>265 lines changed or added</i></th><td></td></tr> 1850 1844 <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> 1851 1845 </table> -
draft-ietf-httpbis/latest/p2-semantics.html
r2644 r2645 2268 2268 <div id="status.codes"> 2269 2269 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a href="#status.codes">Response Status Codes</a></h1> 2270 <p id="rfc.section.6.p.1">The status-code element is a 3-digit integer code giving the result of the attempt to understand and satisfy the request.</p>2270 <p id="rfc.section.6.p.1">The status-code element is a three-digit integer code giving the result of the attempt to understand and satisfy the request.</p> 2271 2271 <p id="rfc.section.6.p.2">HTTP status codes are extensible. HTTP clients are not required to understand the meaning of all registered status codes, 2272 2272 though such understanding is obviously desirable. However, a client <em class="bcp14">MUST</em> understand the class of any status code, as indicated by the first digit, and treat an unrecognized status code as being equivalent … … 2278 2278 </p> 2279 2279 <p id="rfc.section.6.p.4">The first digit of the status-code defines the class of response. The last two digits do not have any categorization role. 2280 There are 5values for the first digit:2280 There are five values for the first digit: 2281 2281 </p> 2282 2282 <ul> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2644 r2645 2601 2601 <section title="Response Status Codes" anchor="status.codes"> 2602 2602 <t> 2603 The status-code element is a 3-digit integer code giving the result of the2603 The status-code element is a three-digit integer code giving the result of the 2604 2604 attempt to understand and satisfy the request. 2605 2605 </t> … … 2621 2621 <t> 2622 2622 The first digit of the status-code defines the class of response. The 2623 last two digits do not have any categorization role. There are 52623 last two digits do not have any categorization role. There are five 2624 2624 values for the first digit: 2625 2625 <list style="symbols">
Note: See TracChangeset
for help on using the changeset viewer.