Ignore:
Timestamp:
Dec 29, 2012, 2:14:11 AM (7 years ago)
Author:
fielding@…
Message:

(editorial) rephrasing to better target the subject of requirements

File:
1 edited

Legend:

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

    r2052 r2066  
    928928  <x:anchor-alias value="304 (Not Modified)"/>
    929929<t>
    930    The 304 status code indicates that a conditional GET request has been
     930   The <x:dfn>304 (Not Modified)</x:dfn> status code indicates that a conditional GET request has been
    931931   received and would have resulted in a <x:ref>200 (OK)</x:ref> response
    932932   if it were not for the fact that the condition has evaluated to false.
     
    939939</t>
    940940<t>
    941    The 304 response &MUST-NOT; contain a message-body, and thus is always
     941   A 304 response cannot contain a message-body; it is always
    942942   terminated by the first empty line after the header fields.
    943943</t>
    944944<t>
    945    A 304 response &MUST; include a <x:ref>Date</x:ref> header field
    946    (&header-date;) unless the origin server does not have a clock that can
    947    provide a reasonable approximation of the current time.  If a <x:ref>200
    948    (OK)</x:ref> response to the same request would have included any of the
    949    header fields <x:ref>Cache-Control</x:ref>, <x:ref>Content-Location</x:ref>,
    950    <x:ref>ETag</x:ref>, <x:ref>Expires</x:ref>, or <x:ref>Vary</x:ref>, then
    951    those same header fields &MUST; be sent in a 304 response.
     945   If a <x:ref>200 (OK)</x:ref> response to the same request would have
     946   included any of the header fields
     947   <x:ref>Cache-Control</x:ref>,
     948   <x:ref>Content-Location</x:ref>,
     949   <x:ref>ETag</x:ref>,
     950   <x:ref>Expires</x:ref>, or
     951   <x:ref>Vary</x:ref>, then
     952   the sender &MUST; generate those same header fields in a 304 response.
    952953</t>
    953954<t>
    954955   Since the goal of a 304 response is to minimize information transfer
    955956   when the recipient already has one or more cached representations,
    956    the response &SHOULD-NOT; include representation metadata other
     957   a sender &SHOULD-NOT; generate representation metadata other
    957958   than the above listed fields unless said metadata exists for the
    958959   purpose of guiding cache updates (e.g., future HTTP extensions).
     
    978979  <x:anchor-alias value="412 (Precondition Failed)"/>
    979980<t>
    980    The 412 status code indicates that one or more preconditions given in
     981   The <x:dfn>412 (Precondition Failed)</x:dfn> status code indicates that one or more preconditions given in
    981982   the request header fields evaluated to false when tested on the server.
    982983   This response code allows the client to place preconditions on the
Note: See TracChangeset for help on using the changeset viewer.