* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 784


Ignore:
Timestamp:
2010-03-10 00:45:16 (5 years ago)
Author:
julian.reschke@gmx.de
Message:

re-organize field descriptions for age calculation, preparing for work on #29.

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

Legend:

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

    r783 r784  
    854854      </p> 
    855855      <ul class="empty"> 
    856          <li>The term "age_value" denotes the value of the Age header, in a form appropriate for arithmetic operation; or 0, if not available.</li> 
     856         <li>The term "age_value" denotes the value of the Age header (<a href="#header.age" id="rfc.xref.header.age.2" title="Age">Section&nbsp;3.1</a>), in a form appropriate for arithmetic operation; or 0, if not available. 
     857         </li> 
    857858      </ul> 
    858859      <p id="rfc.section.2.3.2.p.4"> <dfn>date_value</dfn>   
     
    860861      <ul class="empty"> 
    861862         <li>HTTP/1.1 requires origin servers to send a Date header, if possible, with every response, giving the time at which the response 
    862             was generated (see <a href="p1-messaging.html#header.date" title="Date">Section 9.3</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The term "date_value" denotes the value of the Date header, in a form appropriate for arithmetic operations. See <a href="p1-messaging.html#clockless.origin.server.operation" title="Clockless Origin Server Operation">Section 9.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for requirements regarding responses without a Date response header.<span class="comment" id="TODO-checkref">[<a href="#TODO-checkref" class="smpl">TODO-checkref</a>: correct reference? --jre]</span>  
     863            was generated. The term "date_value" denotes the value of the Date header, in a form appropriate for arithmetic operations. 
     864            See <a href="p1-messaging.html#header.date" title="Date">Section 9.3</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the definition of the Date header, and for requirements regarding responses without a Date response header. 
    863865         </li> 
    864866      </ul> 
     
    893895      <div id="rfc.figure.u.5"></div><pre class="text">  corrected_initial_age = corrected_received_age  
    894896                          + (now - request_time) 
    895 </pre><p id="rfc.section.2.3.2.p.12">where "request_time" is the time (according to the local clock) when the request that elicited this response was sent.</p> 
    896       <p id="rfc.section.2.3.2.p.13">The current_age of a stored response can then be calculated by adding the amount of time (in seconds) since the stored response 
     897</pre><p id="rfc.section.2.3.2.p.12">The current_age of a stored response can then be calculated by adding the amount of time (in seconds) since the stored response 
    897898         was last validated by the origin server to the corrected_initial_age. 
    898899      </p> 
     
    972973      <ul> 
    973974         <li>adding or removing whitespace, where allowed in the header's syntax</li> 
    974          <li>combining multiple message-header fields with the same field name (see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) 
     975         <li>combining multiple message-header fields with the same field name (see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) 
    975976         </li> 
    976977         <li>normalizing both header values in a way that is known to have identical semantics, according to the header's specification 
     
    12471248         that time. 
    12481249      </p> 
    1249       <p id="rfc.section.3.3.p.3">The field-value is an absolute date and time as defined by HTTP-date in <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format. 
     1250      <p id="rfc.section.3.3.p.3">The field-value is an absolute date and time as defined by HTTP-date in <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format. 
    12501251      </p> 
    12511252      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#header.expires" class="smpl">Expires</a>   = "Expires" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expires" class="smpl">Expires-v</a> 
     
    14271428                  <td class="left">http</td> 
    14281429                  <td class="left">standard</td> 
    1429                   <td class="left"> <a href="#header.age" id="rfc.xref.header.age.2" title="Age">Section&nbsp;3.1</a>  
     1430                  <td class="left"> <a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section&nbsp;3.1</a>  
    14301431                  </td> 
    14311432               </tr> 
     
    17831784            <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind"> 
    17841785                  <li class="indline1">age&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1">1.2</a></li> 
    1785                   <li class="indline1">Age header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.age.1">2.2</a>, <a class="iref" href="#rfc.iref.a.2"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.header.age.2">5.1</a></li> 
     1786                  <li class="indline1">Age header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.age.1">2.2</a>, <a class="iref" href="#rfc.xref.header.age.2">2.3.2</a>, <a class="iref" href="#rfc.iref.a.2"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.header.age.3">5.1</a></li> 
    17861787               </ul> 
    17871788            </li> 
     
    18521853                  <li class="indline1">Headers&nbsp;&nbsp; 
    18531854                     <ul class="ind"> 
    1854                         <li class="indline1">Age&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.age.1">2.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.header.age.2">5.1</a></li> 
     1855                        <li class="indline1">Age&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.age.1">2.2</a>, <a class="iref" href="#rfc.xref.header.age.2">2.3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.header.age.3">5.1</a></li> 
    18551856                        <li class="indline1">Cache-Control&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.cache-control.1">2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.2">2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.3">2.2</a>, <a class="iref" href="#rfc.iref.h.3"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.cache-control.4">5.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.5">A.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.6">A.1</a></li> 
    18561857                        <li class="indline1">Expires&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.expires.1">2.1</a>, <a class="iref" href="#rfc.xref.header.expires.2">2.3</a>, <a class="iref" href="#rfc.xref.header.expires.3">2.3.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>3.3</b></a>, <a class="iref" href="#rfc.xref.header.expires.4">5.1</a></li> 
     
    19131914            </li> 
    19141915            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 
    1915                   <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.4</a>, <a class="iref" href="#rfc.xref.Part1.2">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.7">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.8">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.11">2.3.2</a>, <a class="iref" href="#rfc.xref.Part1.12">2.3.2</a>, <a class="iref" href="#rfc.xref.Part1.13">2.6</a>, <a class="iref" href="#rfc.xref.Part1.14">3.3</a>, <a class="iref" href="#Part1"><b>8.1</b></a><ul class="ind"> 
     1916                  <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.4</a>, <a class="iref" href="#rfc.xref.Part1.2">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.7">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.8">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.11">2.3.2</a>, <a class="iref" href="#rfc.xref.Part1.12">2.6</a>, <a class="iref" href="#rfc.xref.Part1.13">3.3</a>, <a class="iref" href="#Part1"><b>8.1</b></a><ul class="ind"> 
    19161917                        <li class="indline1"><em>Section 1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.4</a></li> 
    19171918                        <li class="indline1"><em>Section 1.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.4.1</a></li> 
    19181919                        <li class="indline1"><em>Section 2.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.8">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.4.2</a></li> 
    1919                         <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.6">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.13">2.6</a></li> 
    1920                         <li class="indline1"><em>Section 6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.7">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.14">3.3</a></li> 
     1920                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.6">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.12">2.6</a></li> 
     1921                        <li class="indline1"><em>Section 6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.7">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.13">3.3</a></li> 
    19211922                        <li class="indline1"><em>Section 9.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.11">2.3.2</a></li> 
    1922                         <li class="indline1"><em>Section 9.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.12">2.3.2</a></li> 
    19231923                        <li class="indline1"><em>Section 9.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.9">1.4.2</a></li> 
    19241924                     </ul> 
  • draft-ietf-httpbis/latest/p6-cache.xml

    r783 r784  
    1919  <!ENTITY uri                         "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
    2020  <!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'/>"> 
    2221  <!ENTITY conditional                 "<xref target='Part4' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
    2322  <!ENTITY partial                     "<xref target='Part5' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
     
    635634  <list> 
    636635    <t> 
    637       The term "age_value" denotes the value of the Age header, in a form 
    638       appropriate for arithmetic operation; or 0, if not available. 
     636      The term "age_value" denotes the value of the Age header (<xref target="header.age"/>), 
     637      in a form appropriate for arithmetic operation; or 0, if not available. 
    639638    </t> 
    640639  </list> 
     
    645644    <t> 
    646645      HTTP/1.1 requires origin servers to send a Date header, if possible, 
    647       with every response, giving the time at which the response was generated 
    648       (see &header-date;). The term "date_value" denotes the value of the Date 
    649       header, in a form appropriate for arithmetic operations. See 
    650       &clockless; for requirements regarding responses without a Date 
    651       response header.<cref source="jre" anchor="TODO-checkref">correct reference?</cref> 
     646      with every response, giving the time at which the response was generated. 
     647      The term "date_value" denotes the value of the Date header, in a form 
     648      appropriate for arithmetic operations. See &header-date; for the definition 
     649      of the Date header, and for requirements regarding responses without a 
     650      Date response header. 
    652651    </t> 
    653652  </list> 
     
    704703                          + (now - request_time) 
    705704</artwork></figure> 
    706 <t> 
    707   where "request_time" is the time (according to the local clock) when the request that 
    708   elicited this response was sent. 
    709 </t> 
    710705<t> 
    711706  The current_age of a stored response can then be calculated by adding the amount of 
Note: See TracChangeset for help on using the changeset viewer.