Changeset 444


Ignore:
Timestamp:
Feb 3, 2009, 3:03:36 AM (11 years ago)
Author:
julian.reschke@…
Message:

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

Location:
draft-ietf-httpbis
Files:
4 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>

  • draft-ietf-httpbis/latest/p6-cache.html

    r443 r444  
    486486         <tr>
    487487            <td class="header left"></td>
    488             <td class="header right">February 2, 2009</td>
     488            <td class="header right">February 3, 2009</td>
    489489         </tr>
    490490      </table>
    … …  
    15721572      <div id="rfc.iref.h.4"></div>
    15731573      <h2 id="rfc.section.15.3"><a href="#rfc.section.15.3">15.3</a>&nbsp;<a id="header.expires" href="#header.expires">Expires</a></h2>
    1574       <p id="rfc.section.15.3.p.1">The Expires entity-header field gives the date/time after which the response is considered stale. A stale cache entry may
     1574      <p id="rfc.section.15.3.p.1">The entity-header field "Expires" gives the date/time after which the response is considered stale. A stale cache entry may
    15751575         not normally be returned by a cache (either a proxy cache or a user agent cache) unless it is first validated with the origin
    15761576         server (or with an intermediate cache that has a fresh copy of the entity). See <a href="#expiration.model" title="Expiration Model">Section&nbsp;3</a> for further discussion of the expiration model.

  • draft-ietf-httpbis/latest/p6-cache.xml

    r443 r444  
    21112111  <x:anchor-alias value="Expires-v"/>
    21122112<t>
    2113    The Expires entity-header field gives the date/time after which the
     2113   The entity-header field "Expires" gives the date/time after which the
    21142114   response is considered stale. A stale cache entry may not normally be
    21152115   returned by a cache (either a proxy cache or a user agent cache)
Note: See TracChangeset for help on using the changeset viewer.