Ignore:
Timestamp:
07/05/14 15:47:43 (6 years ago)
Author:
julian.reschke@…
Message:

expand a few status code mentions (#553)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/auth48/p2-semantics.unpg.txt

    r2654 r2655  
    14361436   POST request; almost all of the status codes defined by this
    14371437   specification might be received in a response to POST (the exceptions
    1438    being 206, 304, and 416).
     1438   being 206 (Partial Content), 304 (Not Modified), and 416 (Range Not
     1439   Satisfiable)).
    14391440
    14401441   If one or more resources has been created on the origin server as a
     
    14741475   might be acted upon by other user agents in parallel, or might be
    14751476   subject to dynamic processing by the origin server, before any
     1477
     1478
     1479
     1480Fielding & Reschke      Expires November 8, 2014               [Page 26]
     1481
     1482
     1483Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     1484
     1485
    14761486   subsequent GET is received.  A successful response only implies that
    1477 
    1478 
    1479 
    1480 Fielding & Reschke      Expires November 8, 2014               [Page 26]
    1481 
    1482 
    1483 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    1484 
    1485 
    14861487   the user agent's intent was achieved at the time of its processing by
    14871488   the origin server.
     
    15311532   agent request and the semantics of the origin server response.  It
    15321533   does not define what a resource might be, in any sense of that word,
     1534
     1535
     1536
     1537Fielding & Reschke      Expires November 8, 2014               [Page 27]
     1538
     1539
     1540Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     1541
     1542
    15331543   beyond the interface provided via HTTP.  It does not define how
    1534 
    1535 
    1536 
    1537 Fielding & Reschke      Expires November 8, 2014               [Page 27]
    1538 
    1539 
    1540 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    1541 
    1542 
    15431544   resource state is "stored", nor how such storage might change as a
    15441545   result of a change in resource state, nor how the origin server
     
    15881589   might therefore create a new version resource in addition to changing
    15891590   the state of the target resource, and might also cause links to be
     1591
     1592
     1593
     1594Fielding & Reschke      Expires November 8, 2014               [Page 28]
     1595
     1596
     1597Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     1598
     1599
    15901600   added between the related resources.
    1591 
    1592 
    1593 
    1594 Fielding & Reschke      Expires November 8, 2014               [Page 28]
    1595 
    1596 
    1597 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    1598 
    15991601
    16001602   An origin server that allows PUT on a given target resource MUST send
     
    16451647   repository.
    16461648
     1649
     1650
     1651Fielding & Reschke      Expires November 8, 2014               [Page 29]
     1652
     1653
     1654Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     1655
     1656
    16471657   If a DELETE method is successfully applied, the origin server SHOULD
    1648 
    1649 
    1650 
    1651 Fielding & Reschke      Expires November 8, 2014               [Page 29]
    1652 
    1653 
    1654 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    1655 
    1656 
    16571658   send a 202 (Accepted) status code if the action will likely succeed
    16581659   but has not yet been enacted, a 204 (No Content) status code if the
     
    16821683   CONNECT is intended only for use in requests to a proxy.  An origin
    16831684   server that receives a CONNECT request for itself MAY respond with a
    1684    2xx status code to indicate that a connection is established.
    1685    However, most origin servers do not implement CONNECT.
     1685   2xx (Successful) status code to indicate that a connection is
     1686   established.  However, most origin servers do not implement CONNECT.
    16861687
    16871688   A client sending a CONNECT request MUST send the authority form of
     
    17021703   data received after that blank line is from the server identified by
    17031704   the request-target.  Any response other than a successful response
     1705
     1706
     1707
     1708Fielding & Reschke      Expires November 8, 2014               [Page 30]
     1709
     1710
     1711Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     1712
     1713
    17041714   indicates that the tunnel has not yet been formed and that the
    1705 
    1706 
    1707 
    1708 Fielding & Reschke      Expires November 8, 2014               [Page 30]
    1709 
    1710 
    1711 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    1712 
    1713 
    17141715   connection remains governed by HTTP.
    17151716
     
    17591760   An OPTIONS request with an asterisk ("*") as the request-target
    17601761   (Section 5.3 of [RFC7230]) applies to the server in general rather
     1762
     1763
     1764
     1765Fielding & Reschke      Expires November 8, 2014               [Page 31]
     1766
     1767
     1768Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     1769
     1770
    17611771   than to a specific resource.  Since a server's communication options
    1762 
    1763 
    1764 
    1765 Fielding & Reschke      Expires November 8, 2014               [Page 31]
    1766 
    1767 
    1768 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    1769 
    1770 
    17711772   typically depend on the resource, the "*" request is only useful as a
    17721773   "ping" or "no-op" type of method; it does nothing beyond allowing the
     
    18161817
    18171818   A client MUST NOT generate header fields in a TRACE request
     1819
     1820
     1821
     1822Fielding & Reschke      Expires November 8, 2014               [Page 32]
     1823
     1824
     1825Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     1826
     1827
    18181828   containing sensitive data that might be disclosed by the response.
    1819 
    1820 
    1821 
    1822 Fielding & Reschke      Expires November 8, 2014               [Page 32]
    1823 
    1824 
    1825 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    1826 
    1827 
    18281829   For example, it would be foolish for a user agent to send stored user
    18291830   credentials [RFC7235] or cookies [RFC6265] in a TRACE request.  The
     
    18761877
    18771878
    1878 
    18791879Fielding & Reschke      Expires November 8, 2014               [Page 33]
    18801880
     
    20052005      Note: The Expect header field was added after the original
    20062006      publication of HTTP/1.1 [RFC2068] as both the means to request an
    2007       interim 100 response and the general mechanism for indicating
    2008       must-understand extensions.  However, the extension mechanism has
    2009       not been used by clients and the must-understand requirements have
    2010       not been implemented by many servers, rendering the extension
    2011       mechanism useless.  This specification has removed the extension
    2012       mechanism in order to simplify the definition and processing of
    2013       100-continue.
     2007      interim 100 (Continue) response and the general mechanism for
     2008      indicating must-understand extensions.  However, the extension
     2009      mechanism has not been used by clients and the must-understand
     2010      requirements have not been implemented by many servers, rendering
     2011      the extension mechanism useless.  This specification has removed
     2012      the extension mechanism in order to simplify the definition and
     2013      processing of 100-continue.
    20142014
    201520155.1.2.  Max-Forwards
     
    26462646   For example, if an unrecognized status code of 471 is received by a
    26472647   client, the client can assume that there was something wrong with its
    2648    request and treat the response as if it had received a 400 status
    2649    code.  The response message will usually contain a representation
    2650    that explains the status.
     2648   request and treat the response as if it had received a 400 (Bad
     2649   Request) status code.  The response message will usually contain a
     2650   representation that explains the status.
    26512651
    26522652   The first digit of the status-code defines the class of response.
     
    40494049
    40504050
    4051    For example, an ETag header field in a 201 response communicates the
    4052    entity-tag of the newly created resource's representation, so that it
    4053    can be used in later conditional requests to prevent the "lost
    4054    update" problem [RFC7232].
     4051   For example, an ETag header field in a 201 (Created) response
     4052   communicates the entity-tag of the newly created resource's
     4053   representation, so that it can be used in later conditional requests
     4054   to prevent the "lost update" problem [RFC7232].
    40554055
    40564056   +-------------------+--------------------------+
Note: See TracChangeset for help on using the changeset viewer.