Changeset 2325


Ignore:
Timestamp:
Jul 29, 2013, 1:45:07 PM (6 years ago)
Author:
fielding@…
Message:

For 400, note that the error is perceived to be from the client, and supply at least the minimum examples that cover what we require a 400 to be sent in p1; updates [2316] which addresses #303

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r2324 r2325  
    26772677      <div id="rfc.iref.76"></div>
    26782678      <h3 id="rfc.section.6.5.1"><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
    2679       <p id="rfc.section.6.5.1.p.1">The <dfn>400 (Bad Request)</dfn> status code indicates that the server cannot or will not process the request, due to a client error (e.g., malformed syntax).
     2679      <p id="rfc.section.6.5.1.p.1">The <dfn>400 (Bad Request)</dfn> status code indicates that the server cannot or will not process the request due to something which is perceived to be a client
     2680         error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
    26802681      </p>
    26812682      <div id="rfc.iref.76"></div>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2324 r2325  
    32753275<t>
    32763276   The <x:dfn>400 (Bad Request)</x:dfn> status code indicates that the server
    3277    cannot or will not process the request, due to a client error (e.g.,
    3278    malformed syntax).
     3277   cannot or will not process the request due to something which is perceived
     3278   to be a client error (e.g., malformed request syntax, invalid request
     3279   message framing, or deceptive request routing).
    32793280</t>
    32803281</section>
Note: See TracChangeset for help on using the changeset viewer.