Ignore:
Timestamp:
22/09/12 08:24:07 (8 years ago)
Author:
fielding@…
Message:

fix recently added intro text that incorrectly implied that a HEAD response's representation header fields would be the same as a 200 response for GET; they are the headers for any status code.

File:
1 edited

Legend:

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

    r1910 r1912  
    308308  <x:anchor-alias value="representation-header"/>
    309309<t>
    310    Representation header fields define metadata about the representation data
    311    enclosed in the message body or, if no message body is present, about
    312    the representation that would have been transferred in a <x:ref>200 (OK)</x:ref>
    313    response to a simultaneous GET request with the same effective request URI.
     310   Representation header fields provide metadata about the representation.
     311   When a message includes a payload body, the representation header fields
     312   describe how to interpret the representation data enclosed in the payload
     313   body.  In a response to a HEAD request, the representation header fields
     314   describe the representation data that would have been enclosed in the
     315   payload body if the same request had been a GET.
    314316</t>
    315317<t>
Note: See TracChangeset for help on using the changeset viewer.