Ignore:
Timestamp:
03/02/09 11:03:36 (11 years ago)
Author:
julian.reschke@…
Message:

reorganize header introductions consistent (related to #36, see also [364])

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

Legend:

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

    r442 r444  
    11891189      <div id="rfc.iref.h.4"></div>
    11901190      <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>
    1191       <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 expiration model.
     1191      <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 expiration model.
    11921192      </p>
    11931193      <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
  • draft-ietf-httpbis/latest-roy/p6-cache.xml

    r442 r444  
    10941094        <x:anchor-alias value="Expires"/>
    10951095        <x:anchor-alias value="Expires-v"/>
    1096         <t>The Expires entity-header field gives the date/time after which the response is
     1096        <t>The entity-header field "Expires" gives the date/time after which the response is
    10971097          considered stale. See <xref target="expiration.model" /> for further discussion of the
    10981098          expiration model.</t>
Note: See TracChangeset for help on using the changeset viewer.