Changeset 1912


Ignore:
Timestamp:
Sep 22, 2012, 1:24:07 AM (7 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.

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

Legend:

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

    r1910 r1912  
    449449  }
    450450  @bottom-center {
    451        content: "Expires March 25, 2013";
     451       content: "Expires March 26, 2013";
    452452  }
    453453  @bottom-right {
     
    497497      <meta name="dct.creator" content="Reschke, J. F.">
    498498      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    499       <meta name="dct.issued" scheme="ISO8601" content="2012-09-21">
     499      <meta name="dct.issued" scheme="ISO8601" content="2012-09-22">
    500500      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    501501      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     
    528528            </tr>
    529529            <tr>
    530                <td class="left">Expires: March 25, 2013</td>
     530               <td class="left">Expires: March 26, 2013</td>
    531531               <td class="right">greenbytes</td>
    532532            </tr>
    533533            <tr>
    534534               <td class="left"></td>
    535                <td class="right">September 21, 2012</td>
     535               <td class="right">September 22, 2012</td>
    536536            </tr>
    537537         </tbody>
     
    560560         in progress”.
    561561      </p>
    562       <p>This Internet-Draft will expire on March 25, 2013.</p>
     562      <p>This Internet-Draft will expire on March 26, 2013.</p>
    563563      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    564564      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    884884      </p>
    885885      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="representation.header.fields" href="#representation.header.fields">Representation Header Fields</a></h2>
    886       <p id="rfc.section.3.1.p.1">Representation header fields define metadata about the representation data enclosed in the message body or, if no message
    887          body is present, about the representation that would have been transferred in a <a href="#status.200" class="smpl">200 (OK)</a> response to a simultaneous GET request with the same effective request URI.
     886      <p id="rfc.section.3.1.p.1">Representation header fields provide metadata about the representation. When a message includes a payload body, the representation
     887         header fields describe how to interpret the representation data enclosed in the payload body. In a response to a HEAD request,
     888         the representation header fields describe the representation data that would have been enclosed in the payload body if the
     889         same request had been a GET.
    888890      </p>
    889891      <p id="rfc.section.3.1.p.2">The following header fields are defined as representation metadata:</p>
  • 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.