Ignore:
Timestamp:
Jul 4, 2012, 1:15:19 PM (7 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1715 r1716  
    30913091<section title="Use of the 100 (Continue) Status" anchor="use.of.the.100.status">
    30923092<t>
    3093    The purpose of the 100 (Continue) status code (see &status-100;) is to
    3094    allow a client that is sending a request message with a request body
     3093   The purpose of the <x:ref>100 (Continue)</x:ref> status code (see &status-100;)
     3094   is to allow a client that is sending a request message with a request body
    30953095   to determine if the origin server is willing to accept the request
    30963096   (based on the request header fields) before the client sends the request
     
    31033103  <list style="symbols">
    31043104    <t>
    3105         If a client will wait for a 100 (Continue) response before
     3105        If a client will wait for a <x:ref>100 (Continue)</x:ref> response before
    31063106        sending the request body, it &MUST; send an Expect header
    31073107        field (&header-expect;) with the "100-continue" expectation.
     
    31183118   ambiguous situations in which a client might send "Expect: 100-continue"
    31193119   without receiving either a <x:ref>417 (Expectation Failed)</x:ref>
    3120    or a 100 (Continue) status code. Therefore, when a client sends this
     3120   or a <x:ref>100 (Continue)</x:ref> status code. Therefore, when a client sends this
    31213121   header field to an origin server (possibly via a proxy) from which it
    3122    has never seen a 100 (Continue) status code, the client &SHOULD-NOT; 
     3122   has never seen a <x:ref>100 (Continue)</x:ref> status code, the client &SHOULD-NOT; 
    31233123   wait for an indefinite period before sending the request body.
    31243124</t>
     
    31283128    <t> Upon receiving a request which includes an Expect header
    31293129        field with the "100-continue" expectation, an origin server &MUST;
    3130         either respond with 100 (Continue) status code and continue to read
     3130        either respond with <x:ref>100 (Continue)</x:ref> status code and continue to read
    31313131        from the input stream, or respond with a final status code. The
    31323132        origin server &MUST-NOT; wait for the request body before sending
    3133         the 100 (Continue) response. If it responds with a final status
     3133        the <x:ref>100 (Continue)</x:ref> response. If it responds with a final status
    31343134        code, it &MAY; close the transport connection or it &MAY; continue
    31353135        to read and discard the rest of the request.  It &MUST-NOT;
    31363136        perform the request method if it returns a final status code.
    31373137    </t>
    3138     <t> An origin server &SHOULD-NOT;  send a 100 (Continue) response if
     3138    <t> An origin server &SHOULD-NOT;  send a <x:ref>100 (Continue)</x:ref> response if
    31393139        the request message does not include an Expect header
    31403140        field with the "100-continue" expectation, and &MUST-NOT; send a
    3141         100 (Continue) response if such a request comes from an HTTP/1.0
     3141        <x:ref>100 (Continue)</x:ref> response if such a request comes from an HTTP/1.0
    31423142        (or earlier) client. There is an exception to this rule: for
    3143         compatibility with <xref target="RFC2068"/>, a server &MAY; send a 100 (Continue)
     3143        compatibility with <xref target="RFC2068"/>, a server &MAY; send a <x:ref>100 (Continue)</x:ref>
    31443144        status code in response to an HTTP/1.1 PUT or POST request that does
    31453145        not include an Expect header field with the "100-continue"
    31463146        expectation. This exception, the purpose of which is
    31473147        to minimize any client processing delays associated with an
    3148         undeclared wait for 100 (Continue) status code, applies only to
     3148        undeclared wait for <x:ref>100 (Continue)</x:ref> status code, applies only to
    31493149        HTTP/1.1 requests, and not to requests with any other HTTP-version
    31503150        value.
    31513151    </t>
    3152     <t> An origin server &MAY; omit a 100 (Continue) response if it has
     3152    <t> An origin server &MAY; omit a <x:ref>100 (Continue)</x:ref> response if it has
    31533153        already received some or all of the request body for the
    31543154        corresponding request.
    31553155    </t>
    3156     <t> An origin server that sends a 100 (Continue) response &MUST;
     3156    <t> An origin server that sends a <x:ref>100 (Continue)</x:ref> response &MUST;
    31573157        ultimately send a final status code, once the request body is
    31583158        received and processed, unless it terminates the transport
     
    31903190        numbers received from recently-referenced next-hop servers.
    31913191    </t>
    3192     <t> A proxy &MUST-NOT; forward a 100 (Continue) response if the
     3192    <t> A proxy &MUST-NOT; forward a <x:ref>100 (Continue)</x:ref> response if the
    31933193        request message was received from an HTTP/1.0 (or earlier)
    31943194        client and did not include an Expect header field with
     
    32753275</t>
    32763276<t>
    3277    Servers &MUST; include the "Upgrade" header field in 101 (Switching
    3278    Protocols) responses to indicate which protocol(s) are being switched to,
     3277   Servers &MUST; include the "Upgrade" header field in <x:ref>101 (Switching
     3278   Protocols)</x:ref> responses to indicate which protocol(s) are being switched to,
    32793279   and &MUST; include it in <x:ref>426 (Upgrade Required)</x:ref> responses to indicate
    32803280   acceptable protocols to upgrade to. Servers &MAY; include it in any other
     
    41094109  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
    41104110  <x:source href="p2-semantics.xml" basename="p2-semantics">
     4111    <x:defines>100 (Continue)</x:defines>
     4112    <x:defines>101 (Switching Protocols)</x:defines>
    41114113    <x:defines>200 (OK)</x:defines>
    41124114    <x:defines>204 (No Content)</x:defines>
Note: See TracChangeset for help on using the changeset viewer.