Changeset 1960


Ignore:
Timestamp:
Oct 31, 2012, 12:33:04 AM (7 years ago)
Author:
julian.reschke@…
Message:

re-gen HTML for [1959]

File:
1 edited

Legend:

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

    r1945 r1960  
    452452  }
    453453  @bottom-center {
    454        content: "Expires April 25, 2013";
     454       content: "Expires May 4, 2013";
    455455  }
    456456  @bottom-right {
     
    498498      <meta name="dct.creator" content="Reschke, J. F.">
    499499      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    500       <meta name="dct.issued" scheme="ISO8601" content="2012-10-22">
     500      <meta name="dct.issued" scheme="ISO8601" content="2012-10-31">
    501501      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    502502      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     
    524524            </tr>
    525525            <tr>
    526                <td class="left">Expires: April 25, 2013</td>
     526               <td class="left">Expires: May 4, 2013</td>
    527527               <td class="right">J. Reschke, Editor</td>
    528528            </tr>
     
    533533            <tr>
    534534               <td class="left"></td>
    535                <td class="right">October 22, 2012</td>
     535               <td class="right">October 31, 2012</td>
    536536            </tr>
    537537         </tbody>
     
    559559         in progress”.
    560560      </p>
    561       <p>This Internet-Draft will expire on April 25, 2013.</p>
     561      <p>This Internet-Draft will expire on May 4, 2013.</p>
    562562      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    563563      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    17871787         as sensitive information.
    17881788      </p>
    1789       <p id="rfc.section.10.p.2">Implementation flaws might allow attackers to insert content into a cache ("cache poisoning"), leading to compromise of clients
     1789      <p id="rfc.section.10.p.2">Furthermore, the very use of a cache can bring about privacy concerns. For example, if two users share a cache, and the first
     1790         one browses to a site, the second may be able to detect that the other has been to that site, because the resources from it
     1791         load more quickly, thanks to the cache.
     1792      </p>
     1793      <p id="rfc.section.10.p.3">Implementation flaws might allow attackers to insert content into a cache ("cache poisoning"), leading to compromise of clients
    17901794         that trust that content. Because of their nature, these attacks are difficult to mitigate.
    17911795      </p>
    1792       <p id="rfc.section.10.p.3">Likewise, implementation flaws (as well as misunderstanding of cache operation) might lead to caching of sensitive information
     1796      <p id="rfc.section.10.p.4">Likewise, implementation flaws (as well as misunderstanding of cache operation) might lead to caching of sensitive information
    17931797         (e.g., authentication credentials) that is thought to be private, exposing it to unauthorized parties.
    17941798      </p>
    1795       <p id="rfc.section.10.p.4">Note that the Set-Cookie response header <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a> does not inhibit caching; a cacheable response with a Set-Cookie header can be (and often is) used to satisfy subsequent requests
     1799      <p id="rfc.section.10.p.5">Note that the Set-Cookie response header <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a> does not inhibit caching; a cacheable response with a Set-Cookie header can be (and often is) used to satisfy subsequent requests
    17961800         to caches. Servers who wish to control caching of these responses are encouraged to emit appropriate Cache-Control response
    17971801         headers.
Note: See TracChangeset for help on using the changeset viewer.