Ignore:
Timestamp:
20/12/13 21:22:55 (7 years ago)
Author:
fielding@…
Message:

(editorial) fix odd phrasing in [2502]

File:
1 edited

Legend:

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

    r2508 r2518  
    448448  }
    449449  @bottom-center {
    450        content: "Expires June 16, 2014";
     450       content: "Expires June 23, 2014";
    451451  }
    452452  @bottom-right {
     
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-12-13">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-12-20">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    495495      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.">
     
    517517            </tr>
    518518            <tr>
    519                <td class="left">Expires: June 16, 2014</td>
    520                <td class="right">December 13, 2013</td>
     519               <td class="left">Expires: June 23, 2014</td>
     520               <td class="right">December 20, 2013</td>
    521521            </tr>
    522522         </tbody>
     
    546546            in progress”.
    547547         </p>
    548          <p>This Internet-Draft will expire on June 16, 2014.</p>
     548         <p>This Internet-Draft will expire on June 23, 2014.</p>
    549549      </div>
    550550      <div id="rfc.copyrightnotice">
     
    826826               <p id="rfc.section.2.3.1.p.2">For example, a resource that has implementation-specific versioning applied to all changes might use an internal revision
    827827                  number, perhaps combined with a variance identifier for content negotiation, to accurately differentiate between representations.
    828                   Other implementations might use a collision-resistant hash of representation content, a combination of various files system
    829                   attributes, or a modification timestamp that has sub-second resolution.
     828                  Other implementations might use a collision-resistant hash of representation content, a combination of various file attributes,
     829                  or a modification timestamp that has sub-second resolution.
    830830               </p>
    831831               <p id="rfc.section.2.3.1.p.3">An origin server <em class="bcp14">SHOULD</em> send ETag for any selected representation for which detection of changes can be reasonably and consistently determined, since
Note: See TracChangeset for help on using the changeset viewer.