Ignore:
Timestamp:
Dec 23, 2007, 5:22:38 AM (12 years ago)
Author:
julian.reschke@…
Message:

Cleanup references after switch to symbolic references (removing duplicated RFC numbers), clean up some of the references XML code.

File:
1 edited

Legend:

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

    r96 r97  
    224224   This document will define aspects of HTTP related to caching response
    225225   messages.  Right now it only includes the extracted relevant sections
    226    of <xref target="RFC2616">RFC 2616</xref> without edit.
     226   of <xref target="RFC2616" x:fmt="none">RFC 2616</xref> without edit.
    227227</t>
    228228
     
    458458   A correct cache &MUST; respond to a request with the most up-to-date
    459459   response held by the cache that is appropriate to the request (see
    460    sections <xref target="disambiguating.expiration.values" format="counter"/>,
     460   Sections <xref target="disambiguating.expiration.values" format="counter"/>,
    461461   <xref target="disambiguating.multiple.responses" format="counter"/>,
    462462   and <xref target="cache.replacement" format="counter"/>) which meets one of the following
     
    477477         origin server, in carefully considered circumstances the cache
    478478         &MAY; still return the response with the appropriate Warning
    479          header (see section <xref target="exceptions.to.the.rules.and.warnings" format="counter"/>
     479         header (see Sections <xref target="exceptions.to.the.rules.and.warnings" format="counter"/>
    480480         and <xref target="header.warning" format="counter"/>), unless such a response
    481481         is prohibited (e.g., by a "no-store" cache-directive, or by a
     
    14801480<section title="Cache Replacement" anchor="cache.replacement">
    14811481<t>
    1482    If a new cacheable (see sections <xref target="what.may.be.stored.by.caches" format="counter"/>,
     1482   If a new cacheable (see Sections <xref target="what.may.be.stored.by.caches" format="counter"/>,
    14831483   <xref target="disambiguating.expiration.values" format="counter"/>,
    14841484   <xref target="disambiguating.multiple.responses" format="counter"/>
     
    23142314<t>
    23152315   If a character set other than ISO-8859-1 is used, it &MUST; be encoded
    2316    in the warn-text using the method described in RFC 2047 <xref target="RFC2047"/>.
     2316   in the warn-text using the method described in <xref target="RFC2047"/>.
    23172317</t>
    23182318<t>
     
    27782778
    27792779<reference anchor="RFC2047">
    2780 <front>
    2781 <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</title>
    2782 <author initials="K." surname="Moore" fullname="Keith Moore">
    2783 <organization>University of Tennessee</organization>
    2784 <address>
    2785 <postal>
    2786 <street>107 Ayres Hall</street>
    2787 <street>Knoxville TN 37996-1301</street></postal>
    2788 <email>moore@cs.utk.edu</email></address></author>
    2789 <date month="November" year="1996"/>
    2790 <area>Applications</area>
    2791 <keyword>Amercian Standard Code for Information Interchange</keyword>
    2792 <keyword>mail</keyword>
    2793 <keyword>multipurpose internet mail extensions</keyword>
    2794 </front>
    2795 <seriesInfo name="RFC" value="2047"/>
     2780  <front>
     2781    <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</title>
     2782    <author initials="K." surname="Moore" fullname="Keith Moore">
     2783      <organization>University of Tennessee</organization>
     2784      <address><email>moore@cs.utk.edu</email></address>
     2785    </author>
     2786    <date month="November" year="1996"/>
     2787  </front>
     2788  <seriesInfo name="RFC" value="2047"/>
    27962789</reference>
    27972790
Note: See TracChangeset for help on using the changeset viewer.