Changeset 1727 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

05/07/12 17:06:19 (10 years ago)

Author:

julian.reschke@…

Message:

Work-in-progress: hyperlink status code range definitions

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (13 diffs)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -898 +898 @@
 </artwork></figure>
 <t>
-   Any successful (2xx) response to a CONNECT request indicates that the
+   Any <x:ref>2xx (Successful)</x:ref> response to a CONNECT request indicates that the
    proxy has established a connection to the requested host and port,
    and has switched to tunneling the current connection to that server
@@ -940 +940 @@
    origin server through another proxy.  In this case, the first proxy
    &SHOULD; make a CONNECT request of that next proxy, requesting a tunnel
-   to the authority.  A proxy &MUST-NOT; respond with any 2xx status code
+   to the authority.  A proxy &MUST-NOT; respond with any <x:ref>2xx</x:ref> status code
    unless it has either a direct or tunnel connection established to the
    authority.
@@ -953 +953 @@
 <t>
    An origin server which receives a CONNECT request for itself &MAY;
-   respond with a 2xx status code to indicate that a connection is
+   respond with a <x:ref>2xx</x:ref> status code to indicate that a connection is
    established.  However, most origin servers do not implement CONNECT.
 </t>
@@ -1138 +1138 @@
   <list style="symbols">
     <t>
-      1xx: Informational - Request received, continuing process
-    </t>
-    <t>
-      2xx: Success - The action was successfully received,
+      <x:ref>1xx (Informational)</x:ref>: Request received, continuing process
+    </t>
+    <t>
+      <x:ref>2xx (Successful)</x:ref>: The action was successfully received,
         understood, and accepted
     </t>
     <t>
-      3xx: Redirection - Further action needs to be taken in order to
+      <x:ref>3xx (Redirection)</x:ref>: Further action needs to be taken in order to
         complete the request
     </t>
     <t>
-      4xx: Client Error - The request contains bad syntax or cannot
+      <x:ref>4xx (Client Error)</x:ref>: The request contains bad syntax or cannot
         be fulfilled
     </t>
     <t>
-      5xx: Server Error - The server failed to fulfill an apparently
+      <x:ref>5xx (Server Error)</x:ref>: The server failed to fulfill an apparently
         valid request
     </t>
@@ -1281 +1281 @@
 
 <section title="Informational 1xx" anchor="status.1xx">
+  <x:anchor-alias value="1xx"/>
+  <x:anchor-alias value="1xx (Informational)"/>
+  <iref primary="true" item="1xx Informational (status code class)" x:for-anchor=""/>
+  <iref primary="true" item="Status Codes Classes" subitem="1xx Informational" x:for-anchor=""/>
 <t>
    This class of status code indicates a provisional response,
@@ -1343 +1347 @@
 
 <section title="Successful 2xx" anchor="status.2xx">
+  <x:anchor-alias value="2xx"/>
+  <x:anchor-alias value="2xx (Successful)"/>
+  <iref primary="true" item="2xx Successful (status code class)" x:for-anchor=""/>
+  <iref primary="true" item="Status Codes Classes" subitem="2xx Successful" x:for-anchor=""/>
 <t>
    This class of status code indicates that the client's request was
@@ -1508 +1516 @@
 
 <section title="Redirection 3xx" anchor="status.3xx">
+  <x:anchor-alias value="3xx"/>
+  <x:anchor-alias value="3xx (Redirection)"/>
+  <iref primary="true" item="3xx Redirection (status code class)" x:for-anchor=""/>
+  <iref primary="true" item="Status Codes Classes" subitem="3xx Redirection" x:for-anchor=""/>
 <t>
    This class of status code indicates that further action needs to be
@@ -1767 +1779 @@
 
 <section title="Client Error 4xx" anchor="status.4xx">
+  <x:anchor-alias value="4xx"/>
+  <x:anchor-alias value="4xx (Client Error)"/>
+  <iref primary="true" item="4xx Client Error (status code class)" x:for-anchor=""/>
+  <iref primary="true" item="Status Codes Classes" subitem="4xx Client Error" x:for-anchor=""/>
 <t>
    The 4xx class of status code is intended for cases in which the
@@ -2036 +2052 @@
 
 <section title="Server Error 5xx" anchor="status.5xx">
+  <x:anchor-alias value="5xx"/>
+  <x:anchor-alias value="5xx (Server Error)"/>
+  <iref primary="true" item="5xx Server Error (status code class)" x:for-anchor=""/>
+  <iref primary="true" item="Status Codes Classes" subitem="5xx Server Error" x:for-anchor=""/>
 <t>
    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
    recipient of a syntactically invalid Expectation header field &MUST; respond
-   with a 4xx status code other than 417.
+   with a <x:ref>4xx</x:ref> status code other than 417.
 </t>
 <t>
@@ -3698 +3718 @@
 <t>
    For <x:ref>201 (Created)</x:ref> responses, the Location is the URI of the
-   new resource which was created by the request. For 3xx responses, the
+   new resource which was created by the request. For <x:ref>3xx</x:ref> responses, the
    location &SHOULD; indicate the server's preferred URI for automatic
    redirection to the resource.
@@ -3829 +3849 @@
    Unavailable)</x:ref> response to indicate how long the service is expected to
    be unavailable to the requesting client. This field &MAY; also be used
-   with any 3xx (Redirection) response to indicate the minimum time the
+   with any <x:ref>3xx (Redirection)</x:ref> response to indicate the minimum time the
    user-agent is asked to wait before issuing the redirected request.
 </t>
@@ -6243 +6263 @@
     <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/10"/>:
-      "Safe Methods vs Redirection" (we missed the introduction to the 3xx
+      "Safe Methods vs Redirection" (we missed the introduction to the <x:ref>3xx</x:ref>
       status codes when fixing this previously)
     </t>