Ignore:
Timestamp:
Apr 27, 2011, 11:24:11 PM (8 years ago)
Author:
julian.reschke@…
Message:

draft-ietf-httpstate-cookie published as RFC 6265

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1271 r1275  
    359359  }
    360360  @bottom-center {
    361        content: "Expires October 20, 2011";
     361       content: "Expires October 30, 2011";
    362362  }
    363363  @bottom-right {
     
    410410      <meta name="dct.creator" content="Reschke, J. F.">
    411411      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    412       <meta name="dct.issued" scheme="ISO8601" content="2011-04-18">
     412      <meta name="dct.issued" scheme="ISO8601" content="2011-04-28">
    413413      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    414414      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    442442            </tr>
    443443            <tr>
    444                <td class="left">Expires: October 20, 2011</td>
     444               <td class="left">Expires: October 30, 2011</td>
    445445               <td class="right">HP</td>
    446446            </tr>
     
    495495            <tr>
    496496               <td class="left"></td>
    497                <td class="right">April 18, 2011</td>
     497               <td class="right">April 28, 2011</td>
    498498            </tr>
    499499         </tbody>
     
    525525         in progress”.
    526526      </p>
    527       <p>This Internet-Draft will expire on October 20, 2011.</p>
     527      <p>This Internet-Draft will expire on October 30, 2011.</p>
    528528      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    529529      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    11491149         indicate the same authority (the same host listening to the same TCP port). They are distinct name spaces and are considered
    11501150         to be distinct origin servers. However, an extension to HTTP that is defined to apply to entire host domains, such as the
    1151          Cookie protocol <a href="#draft-ietf-httpstate-cookie" id="rfc.xref.draft-ietf-httpstate-cookie.1"><cite title="HTTP State Management Mechanism">[draft-ietf-httpstate-cookie]</cite></a>, can allow information set by one service to impact communication with other services within a matching group of host domains.
     1151         Cookie protocol <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>, can allow information set by one service to impact communication with other services within a matching group of host domains.
    11521152      </p>
    11531153      <p id="rfc.section.2.6.2.p.6">The process for authoritative access to an "https" identified resource is defined in <a href="#RFC2818" id="rfc.xref.RFC2818.1"><cite title="HTTP Over TLS">[RFC2818]</cite></a>.
     
    12401240      <div class="note" id="rfc.section.3.2.p.7">
    12411241         <p> <b>Note:</b> The "Set-Cookie" header field as implemented in practice can occur multiple times, but does not use the list syntax, and thus
    1242             cannot be combined into a single line (<a href="#draft-ietf-httpstate-cookie" id="rfc.xref.draft-ietf-httpstate-cookie.2"><cite title="HTTP State Management Mechanism">[draft-ietf-httpstate-cookie]</cite></a>). (See Appendix A.2.3 of <a href="#Kri2001" id="rfc.xref.Kri2001.1"><cite title="HTTP Cookies: Standards, Privacy, and Politics">[Kri2001]</cite></a> for details.) Also note that the Set-Cookie2 header field specified in <a href="#RFC2965" id="rfc.xref.RFC2965.1"><cite title="HTTP State Management Mechanism">[RFC2965]</cite></a> does not share this problem.
     1242            cannot be combined into a single line (<a href="#RFC6265" id="rfc.xref.RFC6265.2"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>). (See Appendix A.2.3 of <a href="#Kri2001" id="rfc.xref.Kri2001.1"><cite title="HTTP Cookies: Standards, Privacy, and Politics">[Kri2001]</cite></a> for details.) Also note that the Set-Cookie2 header field specified in <a href="#RFC2965" id="rfc.xref.RFC2965.1"><cite title="HTTP State Management Mechanism">[RFC2965]</cite></a> does not share this problem.
    12431243         </p>
    12441244      </div>
     
    29332933         </tr>
    29342934         <tr>
     2935            <td class="reference"><b id="RFC6265">[RFC6265]</b></td>
     2936            <td class="top"><a href="mailto:abarth@eecs.berkeley.edu" title="&#xA;        University of California, Berkeley&#xA;      ">Barth, A.</a>, “<a href="http://tools.ietf.org/html/rfc6265">HTTP State Management Mechanism</a>”, RFC&nbsp;6265, April&nbsp;2011.
     2937            </td>
     2938         </tr>
     2939         <tr>
    29352940            <td class="reference"><b id="Spe">[Spe]</b></td>
    29362941            <td class="top">Spero, S., “<a href="http://sunsite.unc.edu/mdma-release/http-prob.html">Analysis of HTTP Performance Problems</a>”, &lt;<a href="http://sunsite.unc.edu/mdma-release/http-prob.html">http://sunsite.unc.edu/mdma-release/http-prob.html</a>&gt;.
     
    29402945            <td class="reference"><b id="Tou1998">[Tou1998]</b></td>
    29412946            <td class="top"><a href="mailto:touch@isi.edu" title="USC/Information Sciences Institute">Touch, J.</a>, <a href="mailto:johnh@isi.edu" title="USC/Information Sciences Institute">Heidemann, J.</a>, and <a href="mailto:katia@isi.edu" title="USC/Information Sciences Institute">K. Obraczka</a>, “<a href="http://www.isi.edu/touch/pubs/http-perf96/">Analysis of HTTP Performance</a>”, ISI Research Report&nbsp;ISI/RR-98-463, Aug&nbsp;1998, &lt;<a href="http://www.isi.edu/touch/pubs/http-perf96/">http://www.isi.edu/touch/pubs/http-perf96/</a>&gt;.<br>(original report dated Aug. 1996)
    2942             </td>
    2943          </tr>
    2944          <tr>
    2945             <td class="reference"><b id="draft-ietf-httpstate-cookie">[draft-ietf-httpstate-cookie]</b></td>
    2946             <td class="top"><a href="mailto:abarth@eecs.berkeley.edu" title="&#xA;        University of California, Berkeley&#xA;      ">Barth, A.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpstate-cookie-23">HTTP State Management Mechanism</a>”, Internet-Draft&nbsp;draft-ietf-httpstate-cookie-23 (work in progress), March&nbsp;2011.
    29472947            </td>
    29482948         </tr>
     
    36223622                  <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.2">6.2.2.2</a></li>
    36233623                  <li>downstream&nbsp;&nbsp;<a href="#rfc.iref.d.1"><b>2.3</b></a></li>
    3624                   <li><em>draft-ietf-httpstate-cookie</em>&nbsp;&nbsp;<a href="#rfc.xref.draft-ietf-httpstate-cookie.1">2.6.2</a>, <a href="#rfc.xref.draft-ietf-httpstate-cookie.2">3.2</a>, <a href="#draft-ietf-httpstate-cookie"><b>13.2</b></a></li>
    36253624               </ul>
    36263625            </li>
     
    38953894                     </ul>
    38963895                  </li>
     3896                  <li><em>RFC6265</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC6265.1">2.6.2</a>, <a href="#rfc.xref.RFC6265.2">3.2</a>, <a href="#RFC6265"><b>13.2</b></a></li>
    38973897               </ul>
    38983898            </li>
Note: See TracChangeset for help on using the changeset viewer.