Changeset 732


Ignore:
Timestamp:
Dec 7, 2009, 9:46:53 AM (10 years ago)
Author:
julian.reschke@…
Message:

typos fixed (editorial change)

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

Legend:

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

    r729 r732  
    402402      <meta name="DC.Creator" content="Reschke, J. F.">
    403403      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    404       <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-12-01">
     404      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-12-07">
    405405      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    406406      <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.">
     
    435435            </tr>
    436436            <tr>
    437                <td class="left">Expires: June 4, 2010</td>
     437               <td class="left">Expires: June 10, 2010</td>
    438438               <td class="right">HP</td>
    439439            </tr>
     
    492492            <tr>
    493493               <td class="left"></td>
    494                <td class="right">December 1, 2009</td>
     494               <td class="right">December 7, 2009</td>
    495495            </tr>
    496496         </tbody>
     
    522522      <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;.
    523523      </p>
    524       <p>This Internet-Draft will expire in June 4, 2010.</p>
     524      <p>This Internet-Draft will expire in June 10, 2010.</p>
    525525      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    526526      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    771771      <p id="rfc.section.2.2.p.3">When a stored response is used to satisfy a request, caches <em class="bcp14">MUST</em> include a single Age header field (<a href="#header.age" id="rfc.xref.header.age.1" title="Age">Section&nbsp;3.1</a>) in the response with a value equal to the stored response's current_age; see <a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>. <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: DISCUSS: this currently includes successfully validated responses.]</span>
    772772      </p>
    773       <p id="rfc.section.2.2.p.4">Requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) <em class="bcp14">MUST</em> be written through the cache to the origin server; i.e., A cache must not reply to such a request before having forwarded
     773      <p id="rfc.section.2.2.p.4">Requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) <em class="bcp14">MUST</em> be written through the cache to the origin server; i.e., a cache must not reply to such a request before having forwarded
    774774         the request and having received a corresponding response.
    775775      </p>
     
    11111111         <li> <b>Note:</b> This usage of the word private only controls where the response may be stored, and cannot ensure the privacy of the message
    11121112            content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
    1113             directive was recieved; i.e., the special handling for the qualified form is not widely implemented.
     1113            directive was received; i.e., the special handling for the qualified form is not widely implemented.
    11141114         </li>
    11151115      </ul>
     
    12491249      <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="header.vary" href="#header.vary">Vary</a></h2>
    12501250      <p id="rfc.section.3.5.p.1">The "Vary" response-header field conveys the set of request-header fields that were used to select the representation.</p>
    1251       <p id="rfc.section.3.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satisdy a given request; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.6</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request
     1251      <p id="rfc.section.3.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satisfy a given request; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.6</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request
    12521252         without validation; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.6</a>.
    12531253      </p>
     
    12781278      </p>
    12791279      <p id="rfc.section.3.6.p.2">Warnings can be used for other purposes, both cache-related and otherwise. The use of a warning, rather than an error status
    1280          code, distinguish these responses from true failures.
     1280         code, distinguishes these responses from true failures.
    12811281      </p>
    12821282      <p id="rfc.section.3.6.p.3">Warning headers can in general be applied to any message, however some warn-codes are specific to caches and can only be applied
  • draft-ietf-httpbis/latest/p6-cache.xml

    r729 r732  
    495495<t>
    496496  Requests with methods that are unsafe (&safe-methods;) &MUST; be written through the cache to
    497   the origin server; i.e., A cache must not reply to such a request before having forwarded the request and having received a
     497  the origin server; i.e., a cache must not reply to such a request before having forwarded the request and having received a
    498498  corresponding response.
    499499</t>
     
    11041104      be stored, and cannot ensure the privacy of the message content.
    11051105      Also, private response directives with field-names are often handled by
    1106       implementations as if an unqualified private directive was recieved; i.e.,
     1106      implementations as if an unqualified private directive was received; i.e.,
    11071107      the special handling for the qualified form is not widely implemented.
    11081108</t>
     
    13451345<t>
    13461346  Caches use this information, in part, to determine whether a stored response
    1347   can be used to satisdy a given request; see
     1347  can be used to satisfy a given request; see
    13481348  <xref target="caching.negotiated.responses" />.
    13491349  determines, while the response is fresh, whether a cache is permitted to use the
     
    14031403<t>
    14041404  Warnings can be used for other purposes, both cache-related and otherwise. The use of a
    1405   warning, rather than an error status code, distinguish these responses from true failures.
     1405  warning, rather than an error status code, distinguishes these responses from true failures.
    14061406</t>
    14071407<t>
Note: See TracChangeset for help on using the changeset viewer.