Changeset 778 for draft-ietf-httpbis
- Timestamp:
- 09/03/10 12:20:08 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r776 r778 402 402 <meta name="dct.creator" content="Reschke, J. F."> 403 403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2010-03-0 8">404 <meta name="dct.issued" scheme="ISO8601" content="2010-03-09"> 405 405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406 406 <meta name="dct.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 "HTTP/1.1" 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."> … … 428 428 </tr> 429 429 <tr> 430 <td class="left">Expires: September 9, 2010</td>430 <td class="left">Expires: September 10, 2010</td> 431 431 <td class="right">J. Mogul</td> 432 432 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right">March 8, 2010</td>491 <td class="right">March 9, 2010</td> 492 492 </tr> 493 493 </tbody> … … 519 519 <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>. 520 520 </p> 521 <p>This Internet-Draft will expire in September 9, 2010.</p>521 <p>This Internet-Draft will expire in September 10, 2010.</p> 522 522 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 523 523 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 867 867 </ol> 868 868 <div id="rfc.figure.u.4"></div> 869 <p>These are combined as</p> <pre class="text"> 869 <p>These are combined as</p> <pre class="text"> corrected_received_age = max(now - date_value, age_value) 870 870 </pre><p id="rfc.section.2.3.2.p.7">When an Age value is received, it <em class="bcp14">MUST</em> be interpreted relative to the time the request was initiated, not the time that the response was received. 871 871 </p> 872 <div id="rfc.figure.u.5"></div><pre class="text"> corrected_initial_age = corrected_received_age873 + (now - request_time)872 <div id="rfc.figure.u.5"></div><pre class="text"> corrected_initial_age = corrected_received_age 873 + (now - request_time) 874 874 </pre><p id="rfc.section.2.3.2.p.9">where "request_time" is the time (according to the local clock) when the request that elicited this response was sent.</p> 875 875 <p id="rfc.section.2.3.2.p.10">The current_age of a stored response can then be calculated by adding the amount of time (in seconds) since the stored response … … 877 877 </p> 878 878 <p id="rfc.section.2.3.2.p.11">In summary:</p> 879 <div id="rfc.figure.u.6"></div><pre class="text"> age_value - Age header field-value received with the response 880 date_value - Date header field-value received with the response 881 request_time - local time when the cache made the request 882 resulting in the stored response 883 response_time - local time when the cache received the response 884 now - current local time 885 886 apparent_age = max(0, response_time - date_value); 879 <p id="rfc.section.2.3.2.p.12">age_value </p> 880 <ul class="empty"> 881 <li>Age header field-value received with the response.</li> 882 </ul> 883 <p id="rfc.section.2.3.2.p.13">date_value </p> 884 <ul class="empty"> 885 <li>Date header field-value received with the response.</li> 886 </ul> 887 <p id="rfc.section.2.3.2.p.14">request_time </p> 888 <ul class="empty"> 889 <li>Local time when the cache made the request resulting in the stored response.</li> 890 </ul> 891 <p id="rfc.section.2.3.2.p.15">response_time </p> 892 <ul class="empty"> 893 <li>Local time when the cache received the response.</li> 894 </ul> 895 <p id="rfc.section.2.3.2.p.16">now </p> 896 <ul class="empty"> 897 <li>Current local time.</li> 898 </ul> 899 <div id="rfc.figure.u.6"></div> 900 <p>With these definitions, the current_age can be calculated as per:</p> <pre class="text"> apparent_age = max(0, response_time - date_value); 887 901 corrected_received_age = max(apparent_age, age_value); 888 902 response_delay = response_time - request_time; … … 1761 1775 </ul> 1762 1776 <h2 id="rfc.section.C.11"><a href="#rfc.section.C.11">C.11</a> <a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p6-cache-09</a></h2> 1763 <p id="rfc.section.C.11.p.1">No ne yet.</p>1777 <p id="rfc.section.C.11.p.1">No significant changes.</p> 1764 1778 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1765 1779 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a> -
draft-ietf-httpbis/latest/p6-cache.xml
r773 r778 560 560 </artwork> 561 561 </figure> 562 563 562 <t> 564 563 The freshness_lifetime is defined in <xref target="calculating.freshness.lifetime" />; … … 658 657 <preamble>These are combined as</preamble> 659 658 <artwork type="code"> 660 659 corrected_received_age = max(now - date_value, age_value) 661 660 </artwork></figure> 662 661 <t> … … 665 664 </t> 666 665 <figure><artwork type="code"> 667 corrected_initial_age = corrected_received_age668 + (now - request_time)666 corrected_initial_age = corrected_received_age 667 + (now - request_time) 669 668 </artwork></figure> 670 669 <t> … … 680 679 In summary: 681 680 </t> 682 <figure><artwork type="code"> 683 age_value - Age header field-value received with the response 684 date_value - Date header field-value received with the response 685 request_time - local time when the cache made the request 686 resulting in the stored response 687 response_time - local time when the cache received the response 688 now - current local time 689 681 <t> 682 age_value 683 <list> 684 <t>Age header field-value received with the response.</t> 685 </list> 686 </t> 687 <t> 688 date_value 689 <list> 690 <t>Date header field-value received with the response.</t> 691 </list> 692 </t> 693 <t> 694 request_time 695 <list> 696 <t>Local time when the cache made the request resulting in the stored response.</t> 697 </list> 698 </t> 699 <t> 700 response_time 701 <list> 702 <t>Local time when the cache received the response.</t> 703 </list> 704 </t> 705 <t> 706 now 707 <list> 708 <t>Current local time.</t> 709 </list> 710 </t> 711 <figure> 712 <preamble>With these definitions, the current_age can be calculated as per:</preamble> 713 <artwork type="code"> 690 714 apparent_age = max(0, response_time - date_value); 691 715 corrected_received_age = max(apparent_age, age_value); … … 2312 2336 <section title="Since draft-ietf-httpbis-p6-cache-09" anchor="changes.since.09"> 2313 2337 <t> 2314 No ne yet.2338 No significant changes. 2315 2339 </t> 2316 2340 </section>
Note: See TracChangeset
for help on using the changeset viewer.