Changeset 1727 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 05/07/12 17:06:19 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1726 r1727 898 898 </artwork></figure> 899 899 <t> 900 Any successful (2xx)response to a CONNECT request indicates that the900 Any <x:ref>2xx (Successful)</x:ref> response to a CONNECT request indicates that the 901 901 proxy has established a connection to the requested host and port, 902 902 and has switched to tunneling the current connection to that server … … 940 940 origin server through another proxy. In this case, the first proxy 941 941 &SHOULD; make a CONNECT request of that next proxy, requesting a tunnel 942 to the authority. A proxy &MUST-NOT; respond with any 2xxstatus code942 to the authority. A proxy &MUST-NOT; respond with any <x:ref>2xx</x:ref> status code 943 943 unless it has either a direct or tunnel connection established to the 944 944 authority. … … 953 953 <t> 954 954 An origin server which receives a CONNECT request for itself &MAY; 955 respond with a 2xxstatus code to indicate that a connection is955 respond with a <x:ref>2xx</x:ref> status code to indicate that a connection is 956 956 established. However, most origin servers do not implement CONNECT. 957 957 </t> … … 1138 1138 <list style="symbols"> 1139 1139 <t> 1140 1xx: Informational -Request received, continuing process1141 </t> 1142 <t> 1143 2xx: Success -The action was successfully received,1140 <x:ref>1xx (Informational)</x:ref>: Request received, continuing process 1141 </t> 1142 <t> 1143 <x:ref>2xx (Successful)</x:ref>: The action was successfully received, 1144 1144 understood, and accepted 1145 1145 </t> 1146 1146 <t> 1147 3xx: Redirection -Further action needs to be taken in order to1147 <x:ref>3xx (Redirection)</x:ref>: Further action needs to be taken in order to 1148 1148 complete the request 1149 1149 </t> 1150 1150 <t> 1151 4xx: Client Error -The request contains bad syntax or cannot1151 <x:ref>4xx (Client Error)</x:ref>: The request contains bad syntax or cannot 1152 1152 be fulfilled 1153 1153 </t> 1154 1154 <t> 1155 5xx: Server Error -The server failed to fulfill an apparently1155 <x:ref>5xx (Server Error)</x:ref>: The server failed to fulfill an apparently 1156 1156 valid request 1157 1157 </t> … … 1281 1281 1282 1282 <section title="Informational 1xx" anchor="status.1xx"> 1283 <x:anchor-alias value="1xx"/> 1284 <x:anchor-alias value="1xx (Informational)"/> 1285 <iref primary="true" item="1xx Informational (status code class)" x:for-anchor=""/> 1286 <iref primary="true" item="Status Codes Classes" subitem="1xx Informational" x:for-anchor=""/> 1283 1287 <t> 1284 1288 This class of status code indicates a provisional response, … … 1343 1347 1344 1348 <section title="Successful 2xx" anchor="status.2xx"> 1349 <x:anchor-alias value="2xx"/> 1350 <x:anchor-alias value="2xx (Successful)"/> 1351 <iref primary="true" item="2xx Successful (status code class)" x:for-anchor=""/> 1352 <iref primary="true" item="Status Codes Classes" subitem="2xx Successful" x:for-anchor=""/> 1345 1353 <t> 1346 1354 This class of status code indicates that the client's request was … … 1508 1516 1509 1517 <section title="Redirection 3xx" anchor="status.3xx"> 1518 <x:anchor-alias value="3xx"/> 1519 <x:anchor-alias value="3xx (Redirection)"/> 1520 <iref primary="true" item="3xx Redirection (status code class)" x:for-anchor=""/> 1521 <iref primary="true" item="Status Codes Classes" subitem="3xx Redirection" x:for-anchor=""/> 1510 1522 <t> 1511 1523 This class of status code indicates that further action needs to be … … 1767 1779 1768 1780 <section title="Client Error 4xx" anchor="status.4xx"> 1781 <x:anchor-alias value="4xx"/> 1782 <x:anchor-alias value="4xx (Client Error)"/> 1783 <iref primary="true" item="4xx Client Error (status code class)" x:for-anchor=""/> 1784 <iref primary="true" item="Status Codes Classes" subitem="4xx Client Error" x:for-anchor=""/> 1769 1785 <t> 1770 1786 The 4xx class of status code is intended for cases in which the … … 2036 2052 2037 2053 <section title="Server Error 5xx" anchor="status.5xx"> 2054 <x:anchor-alias value="5xx"/> 2055 <x:anchor-alias value="5xx (Server Error)"/> 2056 <iref primary="true" item="5xx Server Error (status code class)" x:for-anchor=""/> 2057 <iref primary="true" item="Status Codes Classes" subitem="5xx Server Error" x:for-anchor=""/> 2038 2058 <t> 2039 2059 Response status codes beginning with the digit "5" indicate cases in … … 3608 3628 the recipient &MUST; respond with a <x:ref>417 (Expectation Failed)</x:ref> status code. A 3609 3629 recipient of a syntactically invalid Expectation header field &MUST; respond 3610 with a 4xxstatus code other than 417.3630 with a <x:ref>4xx</x:ref> status code other than 417. 3611 3631 </t> 3612 3632 <t> … … 3698 3718 <t> 3699 3719 For <x:ref>201 (Created)</x:ref> responses, the Location is the URI of the 3700 new resource which was created by the request. For 3xxresponses, the3720 new resource which was created by the request. For <x:ref>3xx</x:ref> responses, the 3701 3721 location &SHOULD; indicate the server's preferred URI for automatic 3702 3722 redirection to the resource. … … 3829 3849 Unavailable)</x:ref> response to indicate how long the service is expected to 3830 3850 be unavailable to the requesting client. This field &MAY; also be used 3831 with any 3xx (Redirection)response to indicate the minimum time the3851 with any <x:ref>3xx (Redirection)</x:ref> response to indicate the minimum time the 3832 3852 user-agent is asked to wait before issuing the redirected request. 3833 3853 </t> … … 6243 6263 <t> 6244 6264 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/10"/>: 6245 "Safe Methods vs Redirection" (we missed the introduction to the 3xx6265 "Safe Methods vs Redirection" (we missed the introduction to the <x:ref>3xx</x:ref> 6246 6266 status codes when fixing this previously) 6247 6267 </t>
Note: See TracChangeset
for help on using the changeset viewer.