Changeset 1275 for draft-ietf-httpbis
- Timestamp:
- 28/04/11 06:24:11 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1271 r1275 359 359 } 360 360 @bottom-center { 361 content: "Expires October 20, 2011";361 content: "Expires October 30, 2011"; 362 362 } 363 363 @bottom-right { … … 410 410 <meta name="dct.creator" content="Reschke, J. F."> 411 411 <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"> 413 413 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 414 414 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 442 442 </tr> 443 443 <tr> 444 <td class="left">Expires: October 20, 2011</td>444 <td class="left">Expires: October 30, 2011</td> 445 445 <td class="right">HP</td> 446 446 </tr> … … 495 495 <tr> 496 496 <td class="left"></td> 497 <td class="right">April 18, 2011</td>497 <td class="right">April 28, 2011</td> 498 498 </tr> 499 499 </tbody> … … 525 525 in progress”. 526 526 </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> 528 528 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 529 529 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1149 1149 indicate the same authority (the same host listening to the same TCP port). They are distinct name spaces and are considered 1150 1150 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. 1152 1152 </p> 1153 1153 <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>. … … 1240 1240 <div class="note" id="rfc.section.3.2.p.7"> 1241 1241 <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. 1243 1243 </p> 1244 1244 </div> … … 2933 2933 </tr> 2934 2934 <tr> 2935 <td class="reference"><b id="RFC6265">[RFC6265]</b></td> 2936 <td class="top"><a href="mailto:abarth@eecs.berkeley.edu" title="
 University of California, Berkeley
 ">Barth, A.</a>, “<a href="http://tools.ietf.org/html/rfc6265">HTTP State Management Mechanism</a>”, RFC 6265, April 2011. 2937 </td> 2938 </tr> 2939 <tr> 2935 2940 <td class="reference"><b id="Spe">[Spe]</b></td> 2936 2941 <td class="top">Spero, S., “<a href="http://sunsite.unc.edu/mdma-release/http-prob.html">Analysis of HTTP Performance Problems</a>”, <<a href="http://sunsite.unc.edu/mdma-release/http-prob.html">http://sunsite.unc.edu/mdma-release/http-prob.html</a>>. … … 2940 2945 <td class="reference"><b id="Tou1998">[Tou1998]</b></td> 2941 2946 <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 ISI/RR-98-463, Aug 1998, <<a href="http://www.isi.edu/touch/pubs/http-perf96/">http://www.isi.edu/touch/pubs/http-perf96/</a>>.<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="
 University of California, Berkeley
 ">Barth, A.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpstate-cookie-23">HTTP State Management Mechanism</a>”, Internet-Draft draft-ietf-httpstate-cookie-23 (work in progress), March 2011.2947 2947 </td> 2948 2948 </tr> … … 3622 3622 <li>deflate (Coding Format) <a href="#rfc.iref.d.2">6.2.2.2</a></li> 3623 3623 <li>downstream <a href="#rfc.iref.d.1"><b>2.3</b></a></li> 3624 <li><em>draft-ietf-httpstate-cookie</em> <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>3625 3624 </ul> 3626 3625 </li> … … 3895 3894 </ul> 3896 3895 </li> 3896 <li><em>RFC6265</em> <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> 3897 3897 </ul> 3898 3898 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1271 r1275 1102 1102 distinct origin servers. However, an extension to HTTP that is 1103 1103 defined to apply to entire host domains, such as the Cookie protocol 1104 <xref target=" draft-ietf-httpstate-cookie"/>, can allow information1104 <xref target="RFC6265"/>, can allow information 1105 1105 set by one service to impact communication with other services 1106 1106 within a matching group of host domains. … … 1292 1292 <x:h>Note:</x:h> The "Set-Cookie" header field as implemented in 1293 1293 practice can occur multiple times, but does not use the list syntax, and 1294 thus cannot be combined into a single line (<xref target=" draft-ietf-httpstate-cookie"/>). (See Appendix A.2.3 of <xref target="Kri2001"/>1294 thus cannot be combined into a single line (<xref target="RFC6265"/>). (See Appendix A.2.3 of <xref target="Kri2001"/> 1295 1295 for details.) Also note that the Set-Cookie2 header field specified in 1296 1296 <xref target="RFC2965"/> does not share this problem. … … 4764 4764 </reference> 4765 4765 4766 <reference anchor= 'draft-ietf-httpstate-cookie'>4766 <reference anchor="RFC6265"> 4767 4767 <front> 4768 4768 <title>HTTP State Management Mechanism</title> … … 4773 4773 <address><email>abarth@eecs.berkeley.edu</email></address> 4774 4774 </author> 4775 <date year= '2011' month='March'/>4775 <date year="2011" month="April" /> 4776 4776 </front> 4777 <seriesInfo name=" Internet-Draft" value="draft-ietf-httpstate-cookie-23"/>4777 <seriesInfo name="RFC" value="6265"/> 4778 4778 </reference> 4779 4779
Note: See TracChangeset
for help on using the changeset viewer.