Changeset 1716 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

04/07/12 20:15:19 (10 years ago)

Author:

julian.reschke@…

Message:

Work-in-progress: hyperlink status codes definitions (1xx range)

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (7 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -3091 +3091 @@
 <section title="Use of the 100 (Continue) Status" anchor="use.of.the.100.status">
 <t>
-   The purpose of the 100 (Continue) status code (see &status-100;) is to
-   allow a client that is sending a request message with a request body
+   The purpose of the <x:ref>100 (Continue)</x:ref> status code (see &status-100;)
+   is to allow a client that is sending a request message with a request body
    to determine if the origin server is willing to accept the request
    (based on the request header fields) before the client sends the request
@@ -3103 +3103 @@
   <list style="symbols">
     <t>
-        If a client will wait for a 100 (Continue) response before
+        If a client will wait for a <x:ref>100 (Continue)</x:ref> response before
         sending the request body, it &MUST; send an Expect header
         field (&header-expect;) with the "100-continue" expectation.
@@ -3118 +3118 @@
    ambiguous situations in which a client might send "Expect: 100-continue"
    without receiving either a <x:ref>417 (Expectation Failed)</x:ref> 
-   or a 100 (Continue) status code. Therefore, when a client sends this
+   or a <x:ref>100 (Continue)</x:ref> status code. Therefore, when a client sends this
    header field to an origin server (possibly via a proxy) from which it
-   has never seen a 100 (Continue) status code, the client &SHOULD-NOT;  
+   has never seen a <x:ref>100 (Continue)</x:ref> status code, the client &SHOULD-NOT;  
    wait for an indefinite period before sending the request body.
 </t>
@@ -3128 +3128 @@
     <t> Upon receiving a request which includes an Expect header
         field with the "100-continue" expectation, an origin server &MUST;
-        either respond with 100 (Continue) status code and continue to read
+        either respond with <x:ref>100 (Continue)</x:ref> status code and continue to read
         from the input stream, or respond with a final status code. The
         origin server &MUST-NOT; wait for the request body before sending
-        the 100 (Continue) response. If it responds with a final status
+        the <x:ref>100 (Continue)</x:ref> response. If it responds with a final status
         code, it &MAY; close the transport connection or it &MAY; continue
         to read and discard the rest of the request.  It &MUST-NOT;
         perform the request method if it returns a final status code.
     </t>
-    <t> An origin server &SHOULD-NOT;  send a 100 (Continue) response if
+    <t> An origin server &SHOULD-NOT;  send a <x:ref>100 (Continue)</x:ref> response if
         the request message does not include an Expect header
         field with the "100-continue" expectation, and &MUST-NOT; send a
-        100 (Continue) response if such a request comes from an HTTP/1.0
+        <x:ref>100 (Continue)</x:ref> response if such a request comes from an HTTP/1.0
         (or earlier) client. There is an exception to this rule: for
-        compatibility with <xref target="RFC2068"/>, a server &MAY; send a 100 (Continue)
+        compatibility with <xref target="RFC2068"/>, a server &MAY; send a <x:ref>100 (Continue)</x:ref>
         status code in response to an HTTP/1.1 PUT or POST request that does
         not include an Expect header field with the "100-continue"
         expectation. This exception, the purpose of which is
         to minimize any client processing delays associated with an
-        undeclared wait for 100 (Continue) status code, applies only to
+        undeclared wait for <x:ref>100 (Continue)</x:ref> status code, applies only to
         HTTP/1.1 requests, and not to requests with any other HTTP-version
         value.
     </t>
-    <t> An origin server &MAY; omit a 100 (Continue) response if it has
+    <t> An origin server &MAY; omit a <x:ref>100 (Continue)</x:ref> response if it has
         already received some or all of the request body for the
         corresponding request.
     </t>
-    <t> An origin server that sends a 100 (Continue) response &MUST;
+    <t> An origin server that sends a <x:ref>100 (Continue)</x:ref> response &MUST;
         ultimately send a final status code, once the request body is
         received and processed, unless it terminates the transport
@@ -3190 +3190 @@
         numbers received from recently-referenced next-hop servers.
     </t>
-    <t> A proxy &MUST-NOT; forward a 100 (Continue) response if the
+    <t> A proxy &MUST-NOT; forward a <x:ref>100 (Continue)</x:ref> response if the
         request message was received from an HTTP/1.0 (or earlier)
         client and did not include an Expect header field with
@@ -3275 +3275 @@
 </t>
 <t>
-   Servers &MUST; include the "Upgrade" header field in 101 (Switching
-   Protocols) responses to indicate which protocol(s) are being switched to,
+   Servers &MUST; include the "Upgrade" header field in <x:ref>101 (Switching
+   Protocols)</x:ref> responses to indicate which protocol(s) are being switched to,
    and &MUST; include it in <x:ref>426 (Upgrade Required)</x:ref> responses to indicate
    acceptable protocols to upgrade to. Servers &MAY; include it in any other
@@ -4109 +4109 @@
   <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
   <x:source href="p2-semantics.xml" basename="p2-semantics">
+    <x:defines>100 (Continue)</x:defines>
+    <x:defines>101 (Switching Protocols)</x:defines>
     <x:defines>200 (OK)</x:defines>
     <x:defines>204 (No Content)</x:defines>