Changeset 1545


Ignore:
Timestamp:
Feb 20, 2012, 10:43:15 PM (8 years ago)
Author:
fielding@…
Message:

#345 Revert the inclusion of Last-Modified in 304 responses from [860]
since it is a new requirement and would unlikely to be useful for 304.
Note that the similar change for 206 responses in p5 has not been reverted
because LM is needed when there is no ETag.

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

Legend:

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

    r1528 r1545  
    460460  }
    461461  @bottom-center {
    462        content: "Expires August 10, 2012";
     462       content: "Expires August 23, 2012";
    463463  }
    464464  @bottom-right {
     
    507507      <meta name="dct.creator" content="Reschke, J. F.">
    508508      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    509       <meta name="dct.issued" scheme="ISO8601" content="2012-02-07">
     509      <meta name="dct.issued" scheme="ISO8601" content="2012-02-20">
    510510      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    511511      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.">
     
    533533            </tr>
    534534            <tr>
    535                <td class="left">Expires: August 10, 2012</td>
     535               <td class="left">Expires: August 23, 2012</td>
    536536               <td class="right">J. Mogul</td>
    537537            </tr>
     
    590590            <tr>
    591591               <td class="left"></td>
    592                <td class="right">February 7, 2012</td>
     592               <td class="right">February 20, 2012</td>
    593593            </tr>
    594594         </tbody>
     
    620620         in progress”.
    621621      </p>
    622       <p>This Internet-Draft will expire on August 10, 2012.</p>
     622      <p>This Internet-Draft will expire on August 23, 2012.</p>
    623623      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    624624      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    10031003         <p> <b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation must be distinct
    10041004            from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings
    1005             (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 5.1</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) apply only during message transfer and do not require distinct entity-tags.
     1005            (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 5</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) apply only during message transfer and do not require distinct entity-tags.
    10061006         </p>
    10071007      </div>
     
    11961196         as if it were the payload of a 200 response. The 304 response <em class="bcp14">MUST NOT</em> contain a message-body, and thus is always terminated by the first empty line after the header fields.
    11971197      </p>
    1198       <p id="rfc.section.4.1.p.2">A 304 response <em class="bcp14">MUST</em> include a Date header field (<a href="p2-semantics.html#header.date" title="Date">Section 9.2</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) unless the origin server does not have a clock that can provide a reasonable approximation of the current time. If a 200
     1198      <p id="rfc.section.4.1.p.2">A 304 response <em class="bcp14">MUST</em> include a Date header field (<a href="p2-semantics.html#header.date" title="Date">Section 10.2</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) unless the origin server does not have a clock that can provide a reasonable approximation of the current time. If a 200
    11991199         response to the same request would have included any of the header fields Cache-Control, Content-Location, ETag, Expires,
    1200          Last-Modified, or Vary, then those same header fields <em class="bcp14">MUST</em> be sent in a 304 response.
     1200         or Vary, then those same header fields <em class="bcp14">MUST</em> be sent in a 304 response.
    12011201      </p>
    12021202      <p id="rfc.section.4.1.p.3">Since the goal of a 304 response is to minimize information transfer when the recipient already has one or more cached representations,
     
    16261626                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">1.2</a></li>
    16271627                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.2</a></li>
    1628                         <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">2.3.3</a></li>
     1628                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">2.3.3</a></li>
    16291629                        <li><em>Section 11</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">7</a></li>
    16301630                     </ul>
     
    16321632                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1.2</a>, <a href="#rfc.xref.Part2.2">1.2</a>, <a href="#rfc.xref.Part2.3">4.1</a>, <a href="#Part2"><b>8.1</b></a><ul>
    16331633                        <li><em>Section 8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">1.2</a></li>
    1634                         <li><em>Section 9.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">4.1</a></li>
     1634                        <li><em>Section 10.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">4.1</a></li>
    16351635                     </ul>
    16361636                  </li>
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r1523 r1545  
    10941094   reasonable approximation of the current time.  If a 200 response
    10951095   to the same request would have included any of the header fields
    1096    Cache-Control, Content-Location, ETag, Expires, Last-Modified, or
    1097    Vary, then those same header fields &MUST; be sent in a 304 response.
     1096   Cache-Control, Content-Location, ETag, Expires, or Vary, then
     1097   those same header fields &MUST; be sent in a 304 response.
    10981098</t>
    10991099<t>
Note: See TracChangeset for help on using the changeset viewer.