Ignore:
Timestamp:
Dec 8, 2012, 12:06:03 AM (7 years ago)
Author:
fielding@…
Message:

clarify description of 304 status code; addresses #384

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r2027 r2042  
    929929<t>
    930930   The 304 status code indicates that a conditional GET request has been
    931    received and would have resulted in a <x:ref>200 (OK)</x:ref> response if it were not
    932    for the fact that the condition has evaluated to false.  In other words,
    933    there is no need for the server to transfer a representation of the
    934    target resource because the client's request indicates that it already
    935    has a valid representation, as indicated by the 304 response header
    936    fields, and is therefore redirecting the client to make use of that
    937    stored representation as if it were the payload of a 200 response.
     931   received and would have resulted in a <x:ref>200 (OK)</x:ref> response
     932   if it were not for the fact that the condition has evaluated to false.
     933   In other words, there is no need for the server to transfer a
     934   representation of the target resource because the request indicates that
     935   the client which made the request conditional already has a valid
     936   representation; the server is therefore redirecting that client to make
     937   use of that stored representation as if it were the payload of a
     938   <x:ref>200 (OK)</x:ref> response.
     939</t>
     940<t>
    938941   The 304 response &MUST-NOT; contain a message-body, and thus is always
    939942   terminated by the first empty line after the header fields.
Note: See TracChangeset for help on using the changeset viewer.