Changeset 779 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 09/03/10 13:11:58 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r778 r779 19 19 <!ENTITY uri "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 20 20 <!ENTITY messaging "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 21 <!ENTITY clockless "<xref target='Part1' x:rel='#clockless.origin.server.operation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 21 22 <!ENTITY conditional "<xref target='Part4' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 22 23 <!ENTITY partial "<xref target='Part5' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 631 632 </t> 632 633 <t> 633 The term "age_value" denotes the value of the Age header, in a form appropriate for 634 arithmetic operations. 635 </t> 636 <t> 637 HTTP/1.1 requires origin servers to send a Date header, if possible, with every 638 response, giving the time at which the response was generated (see &header-date;). 639 The term "date_value" denotes the value of the Date header, in a form appropriate for 640 arithmetic operations. 641 </t> 642 <t> 643 The term "now" means "the current value of the clock at the host performing the 644 calculation." Hosts that use HTTP, but especially hosts running origin servers and 645 caches, &SHOULD; use NTP <xref target="RFC1305" /> or some similar protocol to 646 synchronize their clocks to a globally accurate time standard. 634 The following data is used for the age calculation: 635 </t> 636 <t> 637 <x:dfn>age_value</x:dfn> 638 <list> 639 <t> 640 The term "age_value" denotes the value of the Age header, in a form 641 appropriate for arithmetic operation; or 0, if not available. 642 </t> 643 </list> 644 </t> 645 <t> 646 <x:dfn>date_value</x:dfn> 647 <list> 648 <t> 649 HTTP/1.1 requires origin servers to send a Date header, if possible, 650 with every response, giving the time at which the response was generated 651 (see &header-date;). The term "date_value" denotes the value of the Date 652 header, in a form appropriate for arithmetic operations. See 653 &clockless; for requirements regarding responses without a Date 654 response header.<cref source="jre" anchor="TODO-checkref">correct reference?</cref> 655 </t> 656 </list> 657 </t> 658 <t> 659 <x:dfn>now</x:dfn> 660 <list> 661 <t> 662 The term "now" means "the current value of the clock at the host 663 performing the calculation". Hosts that use HTTP, but especially hosts 664 running origin servers and caches, &SHOULD; use NTP 665 (<xref target="RFC1305"/>) or some similar protocol to synchronize their 666 clocks to a globally accurate time standard. 667 </t> 668 </list> 669 </t> 670 <t> 671 <x:dfn>request_time</x:dfn> 672 <list> 673 <t> 674 The current value of the clock at the host at the time the request 675 resulting in the stored response was made. 676 </t> 677 </list> 678 </t> 679 <t> 680 <x:dfn>response_time</x:dfn> 681 <list> 682 <t> 683 The current value of the clock at the host at the time the response was 684 received. 685 </t> 686 </list> 647 687 </t> 648 688 <t> … … 675 715 time (in seconds) since the stored response was last validated by the origin server to 676 716 the corrected_initial_age. 677 </t>678 <t>679 In summary:680 </t>681 <t>682 age_value683 <list>684 <t>Age header field-value received with the response.</t>685 </list>686 </t>687 <t>688 date_value689 <list>690 <t>Date header field-value received with the response.</t>691 </list>692 </t>693 <t>694 request_time695 <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_time701 <list>702 <t>Local time when the cache received the response.</t>703 </list>704 </t>705 <t>706 now707 <list>708 <t>Current local time.</t>709 </list>710 717 </t> 711 718 <figure>
Note: See TracChangeset
for help on using the changeset viewer.