Changeset 2042

Timestamp:

08/12/12 08:06:03 (10 years ago)

Author:

fielding@…

Message:

clarify description of 304 status code; addresses #384

File:

• draft-ietf-httpbis/latest/p4-conditional.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p4-conditional.xml

@@ -929 +929 @@
 <t>
    The 304 status code indicates that a conditional GET request has been
-   received and would have resulted in a <x:ref>200 (OK)</x:ref> response if it were not
-   for the fact that the condition has evaluated to false.  In other words,
-   there is no need for the server to transfer a representation of the
-   target resource because the client's request indicates that it already
-   has a valid representation, as indicated by the 304 response header
-   fields, and is therefore redirecting the client to make use of that
-   stored representation as if it were the payload of a 200 response.
+   received and would have resulted in a <x:ref>200 (OK)</x:ref> response
+   if it were not for the fact that the condition has evaluated to false.
+   In other words, there is no need for the server to transfer a
+   representation of the target resource because the request indicates that
+   the client which made the request conditional already has a valid
+   representation; the server is therefore redirecting that client to make
+   use of that stored representation as if it were the payload of a
+   <x:ref>200 (OK)</x:ref> response.
+</t>
+<t>
    The 304 response &MUST-NOT; contain a message-body, and thus is always
    terminated by the first empty line after the header fields.