Ignore:
Timestamp:
Sep 25, 2009, 7:43:16 AM (10 years ago)
Author:
julian.reschke@…
Message:

editorial: rephrase header introductions ("the *-header field 'foobar'" -> "the "foobar" *-header field")

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.html

    r694 r697  
    398398      <meta name="DC.Creator" content="Reschke, J. F.">
    399399      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    400       <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09-16">
     400      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09-25">
    401401      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    402402      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     
    430430         </tr>
    431431         <tr>
    432             <td class="header left">Expires: March 20, 2010</td>
     432            <td class="header left">Expires: March 29, 2010</td>
    433433            <td class="header right">HP</td>
    434434         </tr>
     
    487487         <tr>
    488488            <td class="header left"></td>
    489             <td class="header right">September 16, 2009</td>
     489            <td class="header right">September 25, 2009</td>
    490490         </tr>
    491491      </table>
     
    511511      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    512512      </p>
    513       <p>This Internet-Draft will expire in March 20, 2010.</p>
     513      <p>This Internet-Draft will expire in March 29, 2010.</p>
    514514      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    515515      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    974974      <div id="rfc.iref.h.2"></div>
    975975      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="header.age" href="#header.age">Age</a></h2>
    976       <p id="rfc.section.3.1.p.1">The response-header field "Age" conveys the sender's estimate of the amount of time since the response (or its validation)
     976      <p id="rfc.section.3.1.p.1">The "Age" response-header field conveys the sender's estimate of the amount of time since the response (or its validation)
    977977         was generated at the origin server. Age values are calculated as specified in <a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>.
    978978      </p>
     
    992992      <div id="rfc.iref.h.3"></div>
    993993      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="header.cache-control" href="#header.cache-control">Cache-Control</a></h2>
    994       <p id="rfc.section.3.2.p.1">The general-header field "Cache-Control" is used to specify directives that <em class="bcp14">MUST</em> be obeyed by all caches along the request/response chain. The directives specify behavior intended to prevent caches from
     994      <p id="rfc.section.3.2.p.1">The "Cache-Control" general-header field is used to specify directives that <em class="bcp14">MUST</em> be obeyed by all caches along the request/response chain. The directives specify behavior intended to prevent caches from
    995995         adversely interfering with the request or response. Cache directives are unidirectional in that the presence of a directive
    996996         in a request does not imply that the same directive is to be given in the response.
     
    11951195      <div id="rfc.iref.h.4"></div>
    11961196      <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="header.expires" href="#header.expires">Expires</a></h2>
    1197       <p id="rfc.section.3.3.p.1">The entity-header field "Expires" gives the date/time after which the response is considered stale. See <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a> for further discussion of the freshness model.
     1197      <p id="rfc.section.3.3.p.1">The "Expires" entity-header field gives the date/time after which the response is considered stale. See <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a> for further discussion of the freshness model.
    11981198      </p>
    11991199      <p id="rfc.section.3.3.p.2">The presence of an Expires field does not imply that the original resource will change or cease to exist at, before, or after
     
    12171217      <div id="rfc.iref.h.5"></div>
    12181218      <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="header.pragma" href="#header.pragma">Pragma</a></h2>
    1219       <p id="rfc.section.3.4.p.1">The general-header field "Pragma" is used to include implementation-specific directives that might apply to any recipient
     1219      <p id="rfc.section.3.4.p.1">The "Pragma" general-header field is used to include implementation-specific directives that might apply to any recipient
    12201220         along the request/response chain. All pragma directives specify optional behavior from the viewpoint of the protocol; however,
    12211221         some systems <em class="bcp14">MAY</em> require that behavior be consistent with the directives.
     
    12611261      <div id="rfc.iref.h.7"></div>
    12621262      <h2 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a>&nbsp;<a id="header.warning" href="#header.warning">Warning</a></h2>
    1263       <p id="rfc.section.3.6.p.1">The general-header field "Warning" is used to carry additional information about the status or transformation of a message
     1263      <p id="rfc.section.3.6.p.1">The "Warning" general-header field is used to carry additional information about the status or transformation of a message
    12641264         that might not be reflected in the message. This information is typically used to warn about possible incorrectness introduced
    12651265         by caching operations or transformations applied to the entity body of the message.
Note: See TracChangeset for help on using the changeset viewer.