Changeset 1364
- Timestamp:
- 27/07/11 19:23:29 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 14 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1361 r1364 681 681 </ul> 682 682 </li> 683 <li>12. <a href="#ack ">Acknowledgments</a></li>683 <li>12. <a href="#acks">Acknowledgments</a></li> 684 684 <li>13. <a href="#rfc.references">References</a><ul> 685 685 <li>13.1 <a href="#rfc.references.1">Normative References</a></li> … … 2784 2784 <h2 id="rfc.section.11.7"><a href="#rfc.section.11.7">11.7</a> <a id="attack.DoS" href="#attack.DoS">Denial of Service Attacks on Proxies</a></h2> 2785 2785 <p id="rfc.section.11.7.p.1">They exist. They are hard to defend against. Research continues. Beware.</p> 2786 <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> 2787 <p id="rfc.section.12.p.1">HTTP has evolved considerably over the years. It has benefited from a large and active developer community — the many people 2788 who have participated on the www-talk mailing list — and it is that community which has been most responsible for the success 2789 of HTTP and of the World-Wide Web in general. Marc Andreessen, Robert Cailliau, Daniel W. Connolly, Bob Denny, John Franks, 2790 Jean-Francois Groff, Phillip M. Hallam-Baker, Hakon W. Lie, Ari Luotonen, Rob McCool, Lou Montulli, Dave Raggett, Tony Sanders, 2791 and Marc VanHeyningen deserve special recognition for their efforts in defining early aspects of the protocol. 2792 </p> 2793 <p id="rfc.section.12.p.2">This document has benefited greatly from the comments of all those participating in the HTTP-WG. In addition to those already 2794 mentioned, the following individuals have contributed to this specification: 2795 </p> 2796 <p id="rfc.section.12.p.3">Gary Adams, Harald Tveit Alvestrand, Keith Ball, Brian Behlendorf, Paul Burchard, Maurizio Codogno, Josh Cohen, Mike Cowlishaw, 2797 Roman Czyborra, Michael A. Dolan, Daniel DuBois, David J. Fiander, Alan Freier, Marc Hedlund, Greg Herlihy, Koen Holtman, 2798 Alex Hopmann, Bob Jernigan, Shel Kaphan, Rohit Khare, John Klensin, Martijn Koster, Alexei Kosut, David M. Kristol, Daniel 2799 LaLiberte, Ben Laurie, Paul J. Leach, Albert Lunde, John C. Mallery, Jean-Philippe Martin-Flatin, Mitra, David Morris, Gavin 2800 Nicol, Ross Patterson, Bill Perry, Jeffrey Perry, Scott Powers, Owen Rees, Luigi Rizzo, David Robinson, Marc Salomon, Rich 2801 Salz, Allan M. Schiffman, Jim Seidman, Chuck Shotton, Eric W. Sink, Simon E. Spero, Richard N. Taylor, Robert S. Thau, Bill 2802 (BearHeart) Weinman, Francois Yergeau, Mary Ellen Zurko. 2803 </p> 2804 <p id="rfc.section.12.p.4">Thanks to the "cave men" of Palo Alto. You know who you are.</p> 2805 <p id="rfc.section.12.p.5">Jim Gettys (the editor of <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>) wishes particularly to thank Roy Fielding, the editor of <a href="#RFC2068" id="rfc.xref.RFC2068.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, along with John Klensin, Jeff Mogul, Paul Leach, Dave Kristol, Koen Holtman, John Franks, Josh Cohen, Alex Hopmann, Scott 2806 Lawrence, and Larry Masinter for their help. And thanks go particularly to Jeff Mogul and Scott Lawrence for performing the 2807 "MUST/MAY/SHOULD" audit. 2808 </p> 2809 <p id="rfc.section.12.p.6">The Apache Group, Anselm Baird-Smith, author of Jigsaw, and Henrik Frystyk implemented RFC 2068 early, and we wish to thank 2810 them for the discovery of many of the problems that this document attempts to rectify. 2811 </p> 2812 <p id="rfc.section.12.p.7">This specification makes heavy use of the augmented BNF and generic constructs defined by David H. Crocker for <a href="#RFC5234" id="rfc.xref.RFC5234.4"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>. Similarly, it reuses many of the definitions provided by Nathaniel Borenstein and Ned Freed for MIME <a href="#RFC2045" id="rfc.xref.RFC2045.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>. We hope that their inclusion in this specification will help reduce past confusion over the relationship between HTTP and 2813 Internet mail message formats. 2786 <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> 2787 <p id="rfc.section.12.p.1">This document revision builds on the work that went into <a href="#RFC2616" id="rfc.xref.RFC2616.3">RFC 2616</a> and its predecessors. See <a href="http://tools.ietf.org/html/rfc2616#section-16">Section 16</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> for detailed acknowledgements. 2788 </p> 2789 <p id="rfc.section.12.p.2"> <span class="comment" id="todoacks">[<a href="#todoacks" class="smpl">todoacks</a>: Insert HTTPbis-specific acknowledgements here.]</span> 2814 2790 </p> 2815 2791 <h1 id="rfc.references"><a id="rfc.section.13" href="#rfc.section.13">13.</a> References … … 2840 2816 <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 2841 2817 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC 1950, May 1996.<br>RFC 1950 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 2842 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068. 5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.2818 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 2843 2819 </td> 2844 2820 </tr> … … 2846 2822 <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 2847 2823 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC 1951, May 1996.<br>RFC 1951 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 2848 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068. 6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.2824 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 2849 2825 </td> 2850 2826 </tr> … … 2852 2828 <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 2853 2829 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC 1952, May 1996.<br>RFC 1952 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 2854 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068. 7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.2830 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 2855 2831 </td> 2856 2832 </tr> … … 3091 3067 <p id="rfc.section.B.1.2.p.1">For most implementations of HTTP/1.0, each connection is established by the client prior to the request and closed by the 3092 3068 server after sending the response. However, some implementations implement the Keep-Alive version of persistent connections 3093 described in <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068. 8"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.3069 described in <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 3094 3070 </p> 3095 3071 <p id="rfc.section.B.1.2.p.2">Some clients and servers might wish to be compatible with some previous implementations of persistent connections in HTTP/1.0 … … 3326 3302 <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a> Since RFC 2616 3327 3303 </h2> 3328 <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616. 4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.3304 <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. 3329 3305 </p> 3330 3306 <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a> Since draft-ietf-httpbis-p1-messaging-00 … … 3928 3904 <li><em>RFC1951</em> <a href="#rfc.xref.RFC1951.1">6.2.2.2</a>, <a href="#rfc.xref.RFC1951.2">10.4</a>, <a href="#RFC1951"><b>13.1</b></a></li> 3929 3905 <li><em>RFC1952</em> <a href="#rfc.xref.RFC1952.1">6.2.2.3</a>, <a href="#rfc.xref.RFC1952.2">10.4</a>, <a href="#RFC1952"><b>13.1</b></a></li> 3930 <li><em>RFC2045</em> <a href="#rfc.xref.RFC2045.1">1</a>, <a href="#rfc.xref.RFC2045.2">6.2</a>, <a href="# rfc.xref.RFC2045.3">12</a>, <a href="#RFC2045"><b>13.2</b></a><ul>3906 <li><em>RFC2045</em> <a href="#rfc.xref.RFC2045.1">1</a>, <a href="#rfc.xref.RFC2045.2">6.2</a>, <a href="#RFC2045"><b>13.2</b></a><ul> 3931 3907 <li><em>Section 6</em> <a href="#rfc.xref.RFC2045.2">6.2</a></li> 3932 3908 </ul> 3933 3909 </li> 3934 3910 <li><em>RFC2047</em> <a href="#rfc.xref.RFC2047.1">3.2</a>, <a href="#RFC2047"><b>13.2</b></a></li> 3935 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">2.6</a>, <a href="#rfc.xref.RFC2068.2">7.1.3</a>, <a href="#rfc.xref.RFC2068.3">7.2.3</a>, <a href="#rfc.xref.RFC2068.4">1 2</a>, <a href="#rfc.xref.RFC2068.5">13.1</a>, <a href="#rfc.xref.RFC2068.6">13.1</a>, <a href="#rfc.xref.RFC2068.7">13.1</a>, <a href="#RFC2068"><b>13.2</b></a>, <a href="#rfc.xref.RFC2068.8">B.1.2</a><ul>3936 <li><em>Section 19.7.1</em> <a href="#rfc.xref.RFC2068.2">7.1.3</a>, <a href="#rfc.xref.RFC2068. 8">B.1.2</a></li>3911 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">2.6</a>, <a href="#rfc.xref.RFC2068.2">7.1.3</a>, <a href="#rfc.xref.RFC2068.3">7.2.3</a>, <a href="#rfc.xref.RFC2068.4">13.1</a>, <a href="#rfc.xref.RFC2068.5">13.1</a>, <a href="#rfc.xref.RFC2068.6">13.1</a>, <a href="#RFC2068"><b>13.2</b></a>, <a href="#rfc.xref.RFC2068.7">B.1.2</a><ul> 3912 <li><em>Section 19.7.1</em> <a href="#rfc.xref.RFC2068.2">7.1.3</a>, <a href="#rfc.xref.RFC2068.7">B.1.2</a></li> 3937 3913 </ul> 3938 3914 </li> 3939 3915 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>13.1</b></a></li> 3940 3916 <li><em>RFC2145</em> <a href="#rfc.xref.RFC2145.1">1</a>, <a href="#RFC2145"><b>13.2</b></a></li> 3941 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">2.6</a>, <a href="#rfc.xref.RFC2616.3">12</a>, <a href="#RFC2616"><b>13.2</b></a>, <a href="#rfc.xref.RFC2616.4">D.1</a></li> 3917 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">2.6</a>, <a href="#rfc.xref.RFC2616.3">12</a>, <a href="#rfc.xref.RFC2616.4">12</a>, <a href="#RFC2616"><b>13.2</b></a>, <a href="#rfc.xref.RFC2616.5">D.1</a><ul> 3918 <li><em>Section 16</em> <a href="#rfc.xref.RFC2616.4">12</a></li> 3919 </ul> 3920 </li> 3942 3921 <li><em>RFC2817</em> <a href="#rfc.xref.RFC2817.1">10.5</a>, <a href="#RFC2817"><b>13.2</b></a>, <a href="#rfc.xref.RFC2817.2">B.2</a><ul> 3943 3922 <li><em>Section 7.2</em> <a href="#rfc.xref.RFC2817.1">10.5</a></li> … … 3970 3949 </ul> 3971 3950 </li> 3972 <li><em>RFC5234</em> <a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#rfc.xref.RFC5234.3">1.2.1</a>, <a href="# rfc.xref.RFC5234.4">12</a>, <a href="#RFC5234"><b>13.1</b></a><ul>3951 <li><em>RFC5234</em> <a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#rfc.xref.RFC5234.3">1.2.1</a>, <a href="#RFC5234"><b>13.1</b></a><ul> 3973 3952 <li><em>Appendix B.1</em> <a href="#rfc.xref.RFC5234.2">1.2</a></li> 3974 3953 </ul> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1361 r1364 4121 4121 </section> 4122 4122 4123 <section title="Acknowledgments" anchor="ack"> 4124 <t> 4125 HTTP has evolved considerably over the years. It has 4126 benefited from a large and active developer community — the many 4127 people who have participated on the www-talk mailing list — and it is 4128 that community which has been most responsible for the success of 4129 HTTP and of the World-Wide Web in general. Marc Andreessen, Robert 4130 Cailliau, Daniel W. Connolly, Bob Denny, John Franks, Jean-Francois 4131 Groff, Phillip M. Hallam-Baker, Hakon W. Lie, Ari Luotonen, Rob 4132 McCool, Lou Montulli, Dave Raggett, Tony Sanders, and Marc 4133 VanHeyningen deserve special recognition for their efforts in 4134 defining early aspects of the protocol. 4135 </t> 4136 <t> 4137 This document has benefited greatly from the comments of all those 4138 participating in the HTTP-WG. In addition to those already mentioned, 4139 the following individuals have contributed to this specification: 4140 </t> 4141 <t> 4142 Gary Adams, Harald Tveit Alvestrand, Keith Ball, Brian Behlendorf, 4143 Paul Burchard, Maurizio Codogno, Josh Cohen, Mike Cowlishaw, Roman Czyborra, 4144 Michael A. Dolan, Daniel DuBois, David J. Fiander, Alan Freier, Marc Hedlund, Greg Herlihy, 4145 Koen Holtman, Alex Hopmann, Bob Jernigan, Shel Kaphan, Rohit Khare, 4146 John Klensin, Martijn Koster, Alexei Kosut, David M. Kristol, 4147 Daniel LaLiberte, Ben Laurie, Paul J. Leach, Albert Lunde, 4148 John C. Mallery, Jean-Philippe Martin-Flatin, Mitra, David Morris, 4149 Gavin Nicol, Ross Patterson, Bill Perry, Jeffrey Perry, Scott Powers, Owen Rees, 4150 Luigi Rizzo, David Robinson, Marc Salomon, Rich Salz, 4151 Allan M. Schiffman, Jim Seidman, Chuck Shotton, Eric W. Sink, 4152 Simon E. Spero, Richard N. Taylor, Robert S. Thau, 4153 Bill (BearHeart) Weinman, Francois Yergeau, Mary Ellen Zurko. 4154 </t> 4155 <t> 4156 Thanks to the "cave men" of Palo Alto. You know who you are. 4157 </t> 4158 <t> 4159 Jim Gettys (the editor of <xref target="RFC2616"/>) wishes particularly 4160 to thank Roy Fielding, the editor of <xref target="RFC2068"/>, along 4161 with John Klensin, Jeff Mogul, Paul Leach, Dave Kristol, Koen 4162 Holtman, John Franks, Josh Cohen, Alex Hopmann, Scott Lawrence, and 4163 Larry Masinter for their help. And thanks go particularly to Jeff 4164 Mogul and Scott Lawrence for performing the "MUST/MAY/SHOULD" audit. 4165 </t> 4166 <t> 4167 The Apache Group, Anselm Baird-Smith, author of Jigsaw, and Henrik 4168 Frystyk implemented RFC 2068 early, and we wish to thank them for the 4169 discovery of many of the problems that this document attempts to 4170 rectify. 4171 </t> 4172 <t> 4173 This specification makes heavy use of the augmented BNF and generic 4174 constructs defined by David H. Crocker for <xref target="RFC5234"/>. Similarly, it 4175 reuses many of the definitions provided by Nathaniel Borenstein and 4176 Ned Freed for MIME <xref target="RFC2045"/>. We hope that their inclusion in this 4177 specification will help reduce past confusion over the relationship 4178 between HTTP and Internet mail message formats. 4123 <section title="Acknowledgments" anchor="acks"> 4124 <t> 4125 This document revision builds on the work that went into 4126 <xref target="RFC2616" format="none">RFC 2616</xref> and its predecessors. 4127 See <xref target="RFC2616" x:fmt="of" x:sec="16"/> for detailed 4128 acknowledgements. 4129 </t> 4130 <t> 4131 <cref anchor="todoacks">Insert HTTPbis-specific acknowledgements here.</cref> 4179 4132 </t> 4180 4133 <!-- -
draft-ietf-httpbis/latest/p2-semantics.html
r1345 r1364 359 359 } 360 360 @bottom-center { 361 content: "Expires January 2 6, 2012";361 content: "Expires January 28, 2012"; 362 362 } 363 363 @bottom-right { … … 409 409 <meta name="dct.creator" content="Reschke, J. F."> 410 410 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 411 <meta name="dct.issued" scheme="ISO8601" content="2011-07-2 5">411 <meta name="dct.issued" scheme="ISO8601" content="2011-07-27"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 413 413 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields."> … … 440 440 </tr> 441 441 <tr> 442 <td class="left">Expires: January 2 6, 2012</td>442 <td class="left">Expires: January 28, 2012</td> 443 443 <td class="right">HP</td> 444 444 </tr> … … 493 493 <tr> 494 494 <td class="left"></td> 495 <td class="right">July 2 5, 2011</td>495 <td class="right">July 27, 2011</td> 496 496 </tr> 497 497 </tbody> … … 522 522 in progress”. 523 523 </p> 524 <p>This Internet-Draft will expire on January 2 6, 2012.</p>524 <p>This Internet-Draft will expire on January 28, 2012.</p> 525 525 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 526 526 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 675 675 </ul> 676 676 </li> 677 <li>12. <a href="#ack ">Acknowledgments</a></li>677 <li>12. <a href="#acks">Acknowledgments</a></li> 678 678 <li>13. <a href="#rfc.references">References</a><ul> 679 679 <li>13.1 <a href="#rfc.references.1">Normative References</a></li> … … 2591 2591 A HTTP client CONNECTing to port 25 could relay spam via SMTP, for example. As such, proxies <em class="bcp14">SHOULD</em> restrict CONNECT access to a small number of known ports. 2592 2592 </p> 2593 <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> 2593 <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> 2594 <p id="rfc.section.12.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 12</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 2595 </p> 2594 2596 <h1 id="rfc.references"><a id="rfc.section.13" href="#rfc.section.13">13.</a> References 2595 2597 </h1> … … 2739 2741 </p> 2740 2742 <p id="rfc.section.A.p.14">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated 2741 correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.3 7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 9.8</a>)2743 correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 9.8</a>) 2742 2744 </p> 2743 2745 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 3221 3223 </li> 3222 3224 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 3223 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a>, <a href="#rfc.xref.Part1.8">1.2.1</a>, <a href="#rfc.xref.Part1.9">1.2.2</a>, <a href="#rfc.xref.Part1.10">1.2.2</a>, <a href="#rfc.xref.Part1.11">1.2.2</a>, <a href="#rfc.xref.Part1.12">1.2.2</a>, <a href="#rfc.xref.Part1.13">1.2.2</a>, <a href="#rfc.xref.Part1.14">1.2.2</a>, <a href="#rfc.xref.Part1.15">2</a>, <a href="#rfc.xref.Part1.16">2.2.1</a>, <a href="#rfc.xref.Part1.17">3</a>, <a href="#rfc.xref.Part1.18">3</a>, <a href="#rfc.xref.Part1.19">5</a>, <a href="#rfc.xref.Part1.20">6</a>, <a href="#rfc.xref.Part1.21">6.1</a>, <a href="#rfc.xref.Part1.22">7.8</a>, <a href="#rfc.xref.Part1.23">7.8</a>, <a href="#rfc.xref.Part1.24">7.9</a>, <a href="#rfc.xref.Part1.25">8.1.1</a>, <a href="#rfc.xref.Part1.26">8.1.2</a>, <a href="#rfc.xref.Part1.27">8.2.4</a>, <a href="#rfc.xref.Part1.28">8.2.6</a>, <a href="#rfc.xref.Part1.29">8.4.19</a>, <a href="#rfc.xref.Part1.30">8.5.6</a>, <a href="#rfc.xref.Part1.31">9.2</a>, <a href="#rfc.xref.Part1.32">9.8</a>, <a href="#rfc.xref.Part1.33">9.8</a>, <a href="#rfc.xref.Part1.34">9.8</a>, <a href="#rfc.xref.Part1.35">9.9</a>, <a href="#rfc.xref.Part1.36">9.9</a>, <a href="# Part1"><b>13.1</b></a>, <a href="#rfc.xref.Part1.37">A</a><ul>3225 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a>, <a href="#rfc.xref.Part1.8">1.2.1</a>, <a href="#rfc.xref.Part1.9">1.2.2</a>, <a href="#rfc.xref.Part1.10">1.2.2</a>, <a href="#rfc.xref.Part1.11">1.2.2</a>, <a href="#rfc.xref.Part1.12">1.2.2</a>, <a href="#rfc.xref.Part1.13">1.2.2</a>, <a href="#rfc.xref.Part1.14">1.2.2</a>, <a href="#rfc.xref.Part1.15">2</a>, <a href="#rfc.xref.Part1.16">2.2.1</a>, <a href="#rfc.xref.Part1.17">3</a>, <a href="#rfc.xref.Part1.18">3</a>, <a href="#rfc.xref.Part1.19">5</a>, <a href="#rfc.xref.Part1.20">6</a>, <a href="#rfc.xref.Part1.21">6.1</a>, <a href="#rfc.xref.Part1.22">7.8</a>, <a href="#rfc.xref.Part1.23">7.8</a>, <a href="#rfc.xref.Part1.24">7.9</a>, <a href="#rfc.xref.Part1.25">8.1.1</a>, <a href="#rfc.xref.Part1.26">8.1.2</a>, <a href="#rfc.xref.Part1.27">8.2.4</a>, <a href="#rfc.xref.Part1.28">8.2.6</a>, <a href="#rfc.xref.Part1.29">8.4.19</a>, <a href="#rfc.xref.Part1.30">8.5.6</a>, <a href="#rfc.xref.Part1.31">9.2</a>, <a href="#rfc.xref.Part1.32">9.8</a>, <a href="#rfc.xref.Part1.33">9.8</a>, <a href="#rfc.xref.Part1.34">9.8</a>, <a href="#rfc.xref.Part1.35">9.9</a>, <a href="#rfc.xref.Part1.36">9.9</a>, <a href="#rfc.xref.Part1.37">12</a>, <a href="#Part1"><b>13.1</b></a>, <a href="#rfc.xref.Part1.38">A</a><ul> 3224 3226 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.2">1.2</a></li> 3225 3227 <li><em>Section 1.2.2</em> <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a>, <a href="#rfc.xref.Part1.8">1.2.1</a></li> … … 3237 3239 <li><em>Section 9.5</em> <a href="#rfc.xref.Part1.18">3</a></li> 3238 3240 <li><em>Section 9.8</em> <a href="#rfc.xref.Part1.26">8.1.2</a>, <a href="#rfc.xref.Part1.29">8.4.19</a></li> 3239 <li><em>Section 9.9</em> <a href="#rfc.xref.Part1.22">7.8</a>, <a href="#rfc.xref.Part1.34">9.8</a>, <a href="#rfc.xref.Part1.3 7">A</a></li>3241 <li><em>Section 9.9</em> <a href="#rfc.xref.Part1.22">7.8</a>, <a href="#rfc.xref.Part1.34">9.8</a>, <a href="#rfc.xref.Part1.38">A</a></li> 3240 3242 <li><em>Section 10.3.1</em> <a href="#rfc.xref.Part1.23">7.8</a></li> 3243 <li><em>Section 12</em> <a href="#rfc.xref.Part1.37">12</a></li> 3241 3244 </ul> 3242 3245 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1345 r1364 17 17 <!ENTITY mdash "—"> 18 18 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 <!ENTITY acks "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 20 <!ENTITY messaging "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 20 21 <!ENTITY payload "<xref target='Part3' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 2986 2987 </section> 2987 2988 2988 <section title="Acknowledgments" anchor="ack"> 2989 <section title="Acknowledgments" anchor="acks"> 2990 <t> 2991 See &acks;. 2992 </t> 2989 2993 </section> 2990 2994 </middle> -
draft-ietf-httpbis/latest/p3-payload.html
r1350 r1364 359 359 } 360 360 @bottom-center { 361 content: "Expires January 2 6, 2012";361 content: "Expires January 28, 2012"; 362 362 } 363 363 @bottom-right { … … 408 408 <meta name="dct.creator" content="Reschke, J. F."> 409 409 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 410 <meta name="dct.issued" scheme="ISO8601" content="2011-07-2 5">410 <meta name="dct.issued" scheme="ISO8601" content="2011-07-27"> 411 411 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 412 412 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: January 2 6, 2012</td>436 <td class="left">Expires: January 28, 2012</td> 437 437 <td class="right">J. Mogul</td> 438 438 </tr> … … 491 491 <tr> 492 492 <td class="left"></td> 493 <td class="right">July 2 5, 2011</td>493 <td class="right">July 27, 2011</td> 494 494 </tr> 495 495 </tbody> … … 519 519 in progress”. 520 520 </p> 521 <p>This Internet-Draft will expire on January 2 6, 2012.</p>521 <p>This Internet-Draft will expire on January 28, 2012.</p> 522 522 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 523 523 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 596 596 </ul> 597 597 </li> 598 <li>9. <a href="#ack ">Acknowledgments</a></li>598 <li>9. <a href="#acks">Acknowledgments</a></li> 599 599 <li>10. <a href="#rfc.references">References</a><ul> 600 600 <li>10.1 <a href="#rfc.references.1">Normative References</a></li> … … 1481 1481 filter the accept header fields in relayed requests. General purpose user agents which provide a high degree of header configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved. 1482 1482 </p> 1483 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> 1483 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> 1484 <p id="rfc.section.9.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 12</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 1485 </p> 1484 1486 <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References 1485 1487 </h1> … … 1701 1703 </p> 1702 1704 <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a> <a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h2> 1703 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<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.2 3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.1705 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<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.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary. 1704 1706 </p> 1705 1707 <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a> <a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2> … … 1718 1720 </p> 1719 1721 <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2> 1720 <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 9.7</a> of <a href="#Part1" id="rfc.xref.Part1.2 4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol.1722 <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 9.7</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol. 1721 1723 </p> 1722 1724 <h2 id="rfc.section.A.7"><a href="#rfc.section.A.7">A.7</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2> … … 2122 2124 </li> 2123 2125 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 2124 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.3</a>, <a href="#rfc.xref.Part1.2">1.3.1</a>, <a href="#rfc.xref.Part1.3">1.3.1</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.2</a>, <a href="#rfc.xref.Part1.7">1.3.2</a>, <a href="#rfc.xref.Part1.8">1.3.2</a>, <a href="#rfc.xref.Part1.9">2.2</a>, <a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.12">2.2.1</a>, <a href="#rfc.xref.Part1.13">2.2.1</a>, <a href="#rfc.xref.Part1.14">3.1</a>, <a href="#rfc.xref.Part1.15">3.2</a>, <a href="#rfc.xref.Part1.16">5.1</a>, <a href="#rfc.xref.Part1.17">6.1</a>, <a href="#rfc.xref.Part1.18">6.3</a>, <a href="#rfc.xref.Part1.19">6.7</a>, <a href="#rfc.xref.Part1.20">7.2</a>, <a href="#rfc.xref.Part1.21">7.2</a>, <a href="#rfc.xref.Part1.22">7.2</a>, <a href="# Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.23">A.3</a>, <a href="#rfc.xref.Part1.24">A.6</a><ul>2126 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.3</a>, <a href="#rfc.xref.Part1.2">1.3.1</a>, <a href="#rfc.xref.Part1.3">1.3.1</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.2</a>, <a href="#rfc.xref.Part1.7">1.3.2</a>, <a href="#rfc.xref.Part1.8">1.3.2</a>, <a href="#rfc.xref.Part1.9">2.2</a>, <a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.12">2.2.1</a>, <a href="#rfc.xref.Part1.13">2.2.1</a>, <a href="#rfc.xref.Part1.14">3.1</a>, <a href="#rfc.xref.Part1.15">3.2</a>, <a href="#rfc.xref.Part1.16">5.1</a>, <a href="#rfc.xref.Part1.17">6.1</a>, <a href="#rfc.xref.Part1.18">6.3</a>, <a href="#rfc.xref.Part1.19">6.7</a>, <a href="#rfc.xref.Part1.20">7.2</a>, <a href="#rfc.xref.Part1.21">7.2</a>, <a href="#rfc.xref.Part1.22">7.2</a>, <a href="#rfc.xref.Part1.23">9</a>, <a href="#Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.24">A.3</a>, <a href="#rfc.xref.Part1.25">A.6</a><ul> 2125 2127 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.1">1.3</a></li> 2126 2128 <li><em>Section 1.2.2</em> <a href="#rfc.xref.Part1.2">1.3.1</a>, <a href="#rfc.xref.Part1.3">1.3.1</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a></li> … … 2128 2130 <li><em>Section 3.3</em> <a href="#rfc.xref.Part1.15">3.2</a></li> 2129 2131 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.19">6.7</a></li> 2130 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.2 3">A.3</a></li>2132 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.24">A.3</a></li> 2131 2133 <li><em>Section 6.2</em> <a href="#rfc.xref.Part1.12">2.2.1</a></li> 2132 2134 <li><em>Section 6.2.2.1</em> <a href="#rfc.xref.Part1.9">2.2</a>, <a href="#rfc.xref.Part1.20">7.2</a></li> … … 2136 2138 <li><em>Section 6.4</em> <a href="#rfc.xref.Part1.8">1.3.2</a>, <a href="#rfc.xref.Part1.16">5.1</a>, <a href="#rfc.xref.Part1.17">6.1</a>, <a href="#rfc.xref.Part1.18">6.3</a></li> 2137 2139 <li><em>Section 9.2</em> <a href="#rfc.xref.Part1.14">3.1</a></li> 2138 <li><em>Section 9.7</em> <a href="#rfc.xref.Part1.24">A.6</a></li> 2140 <li><em>Section 9.7</em> <a href="#rfc.xref.Part1.25">A.6</a></li> 2141 <li><em>Section 12</em> <a href="#rfc.xref.Part1.23">9</a></li> 2139 2142 </ul> 2140 2143 </li> -
draft-ietf-httpbis/latest/p3-payload.xml
r1335 r1364 18 18 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 19 <!ENTITY notation-abnf "<xref target='Part1' x:rel='#notation.abnf' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 20 <!ENTITY acks "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 20 21 <!ENTITY basic-rules "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 21 22 <!ENTITY caching-neg-resp "<xref target='Part6' x:rel='#caching.negotiated.responses' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 1618 1619 </section> 1619 1620 1620 <section title="Acknowledgments" anchor="ack"> 1621 <section title="Acknowledgments" anchor="acks"> 1622 <t> 1623 See &acks;. 1624 </t> 1621 1625 </section> 1622 1626 </middle> -
draft-ietf-httpbis/latest/p4-conditional.html
r1350 r1364 359 359 } 360 360 @bottom-center { 361 content: "Expires January 2 6, 2012";361 content: "Expires January 28, 2012"; 362 362 } 363 363 @bottom-right { … … 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2011-07-2 5">406 <meta name="dct.issued" scheme="ISO8601" content="2011-07-27"> 407 407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 408 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> … … 430 430 </tr> 431 431 <tr> 432 <td class="left">Expires: January 2 6, 2012</td>432 <td class="left">Expires: January 28, 2012</td> 433 433 <td class="right">J. Mogul</td> 434 434 </tr> … … 487 487 <tr> 488 488 <td class="left"></td> 489 <td class="right">July 2 5, 2011</td>489 <td class="right">July 27, 2011</td> 490 490 </tr> 491 491 </tbody> … … 515 515 in progress”. 516 516 </p> 517 <p>This Internet-Draft will expire on January 2 6, 2012.</p>517 <p>This Internet-Draft will expire on January 28, 2012.</p> 518 518 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 519 519 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 573 573 </li> 574 574 <li>6. <a href="#security.considerations">Security Considerations</a></li> 575 <li>7. <a href="#ack ">Acknowledgments</a></li>575 <li>7. <a href="#acks">Acknowledgments</a></li> 576 576 <li>8. <a href="#rfc.references">References</a><ul> 577 577 <li>8.1 <a href="#rfc.references.1">Normative References</a></li> … … 1181 1181 <p id="rfc.section.6.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 1182 1182 </p> 1183 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> 1183 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> 1184 <p id="rfc.section.7.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 12</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 1185 </p> 1184 1186 <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References 1185 1187 </h1> … … 1466 1468 </li> 1467 1469 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 1468 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">1.2</a>, <a href="#rfc.xref.Part1.5">2.2.5</a>, <a href="#rfc.xref.Part1.6">4.1</a>, <a href="#rfc.xref.Part1.7">4.1</a>, <a href="#rfc.xref.Part1.8">6</a>, <a href="# Part1"><b>8.1</b></a><ul>1470 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">1.2</a>, <a href="#rfc.xref.Part1.5">2.2.5</a>, <a href="#rfc.xref.Part1.6">4.1</a>, <a href="#rfc.xref.Part1.7">4.1</a>, <a href="#rfc.xref.Part1.8">6</a>, <a href="#rfc.xref.Part1.9">7</a>, <a href="#Part1"><b>8.1</b></a><ul> 1469 1471 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.1">1.2</a></li> 1470 1472 <li><em>Section 1.2.2</em> <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.2</a></li> … … 1473 1475 <li><em>Section 9.3</em> <a href="#rfc.xref.Part1.6">4.1</a></li> 1474 1476 <li><em>Section 9.3.1</em> <a href="#rfc.xref.Part1.7">4.1</a></li> 1477 <li><em>Section 12</em> <a href="#rfc.xref.Part1.9">7</a></li> 1475 1478 </ul> 1476 1479 </li> -
draft-ietf-httpbis/latest/p4-conditional.xml
r1339 r1364 17 17 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 18 18 <!ENTITY notation-abnf "<xref target='Part1' x:rel='#notation.abnf' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 <!ENTITY acks "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 20 <!ENTITY basic-rules "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 20 21 <!ENTITY header-date "<xref target='Part1' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 1179 1180 </section> 1180 1181 1181 <section title="Acknowledgments" anchor="ack"> 1182 <section title="Acknowledgments" anchor="acks"> 1183 <t> 1184 See &acks;. 1185 </t> 1182 1186 </section> 1183 1187 </middle> -
draft-ietf-httpbis/latest/p5-range.html
r1355 r1364 359 359 } 360 360 @bottom-center { 361 content: "Expires January 2 7, 2012";361 content: "Expires January 28, 2012"; 362 362 } 363 363 @bottom-right { … … 406 406 <meta name="dct.creator" content="Reschke, J. F."> 407 407 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 408 <meta name="dct.issued" scheme="ISO8601" content="2011-07-2 6">408 <meta name="dct.issued" scheme="ISO8601" content="2011-07-27"> 409 409 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 410 410 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> … … 432 432 </tr> 433 433 <tr> 434 <td class="left">Expires: January 2 7, 2012</td>434 <td class="left">Expires: January 28, 2012</td> 435 435 <td class="right">J. Mogul</td> 436 436 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right">July 2 6, 2011</td>491 <td class="right">July 27, 2011</td> 492 492 </tr> 493 493 </tbody> … … 517 517 in progress”. 518 518 </p> 519 <p>This Internet-Draft will expire on January 2 7, 2012.</p>519 <p>This Internet-Draft will expire on January 28, 2012.</p> 520 520 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 521 521 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 575 575 </ul> 576 576 </li> 577 <li>8. <a href="#ack ">Acknowledgments</a></li>577 <li>8. <a href="#acks">Acknowledgments</a></li> 578 578 <li>9. <a href="#rfc.references">References</a><ul> 579 579 <li>9.1 <a href="#rfc.references.1">Normative References</a></li> … … 1043 1043 of the complete resource representation. 1044 1044 </p> 1045 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> 1046 <p id="rfc.section.8.p.1">Most of the specification of ranges is based on work originally done by Ari Luotonen and John Franks, with additional input 1047 from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach, 1048 Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl. 1045 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> 1046 <p id="rfc.section.8.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 12</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 1049 1047 </p> 1050 1048 <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References … … 1481 1479 </li> 1482 1480 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 1483 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.2</a>, <a href="# Part1"><b>9.1</b></a><ul>1481 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.2</a>, <a href="#rfc.xref.Part1.6">8</a>, <a href="#Part1"><b>9.1</b></a><ul> 1484 1482 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.1">1.2</a></li> 1485 1483 <li><em>Section 1.2.2</em> <a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a></li> 1486 1484 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.5">1.2.2</a></li> 1485 <li><em>Section 12</em> <a href="#rfc.xref.Part1.6">8</a></li> 1487 1486 </ul> 1488 1487 </li> -
draft-ietf-httpbis/latest/p5-range.xml
r1355 r1364 17 17 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 18 18 <!ENTITY notation-abnf "<xref target='Part1' x:rel='#notation.abnf' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 <!ENTITY acks "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 20 <!ENTITY basic-rules "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 20 21 <!ENTITY full-date "<xref target='Part1' x:rel='#date.time.formats.full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 999 1000 </section> 1000 1001 1001 <section title="Acknowledgments" anchor="ack"> 1002 <t> 1003 Most of the specification of ranges is based on work originally done 1004 by Ari Luotonen and John Franks, with additional input from Steve 1005 Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, 1006 Koen Holtman, Shel Kaplan, Paul Leach, Alex Lopez-Ortiz, Larry Masinter, 1007 Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl. 1002 <section title="Acknowledgments" anchor="acks"> 1003 <t> 1004 See &acks;. 1008 1005 </t> 1009 1006 </section> -
draft-ietf-httpbis/latest/p6-cache.html
r1350 r1364 362 362 } 363 363 @bottom-center { 364 content: "Expires January 2 6, 2012";364 content: "Expires January 28, 2012"; 365 365 } 366 366 @bottom-right { … … 408 408 <meta name="dct.creator" content="Reschke, J. F."> 409 409 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 410 <meta name="dct.issued" scheme="ISO8601" content="2011-07-2 5">410 <meta name="dct.issued" scheme="ISO8601" content="2011-07-27"> 411 411 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 412 412 <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."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: January 2 6, 2012</td>436 <td class="left">Expires: January 28, 2012</td> 437 437 <td class="right">J. Mogul</td> 438 438 </tr> … … 495 495 <tr> 496 496 <td class="left"></td> 497 <td class="right">July 2 5, 2011</td>497 <td class="right">July 27, 2011</td> 498 498 </tr> 499 499 </tbody> … … 523 523 in progress”. 524 524 </p> 525 <p>This Internet-Draft will expire on January 2 6, 2012.</p>525 <p>This Internet-Draft will expire on January 28, 2012.</p> 526 526 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 527 527 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 596 596 </li> 597 597 <li>6. <a href="#security.considerations">Security Considerations</a></li> 598 <li>7. <a href="#ack ">Acknowledgments</a></li>598 <li>7. <a href="#acks">Acknowledgments</a></li> 599 599 <li>8. <a href="#rfc.references">References</a><ul> 600 600 <li>8.1 <a href="#rfc.references.1">Normative References</a></li> … … 1616 1616 as sensitive information. 1617 1617 </p> 1618 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> 1619 <p id="rfc.section.7.p.1">Much of the content and presentation of the caching design is due to suggestions and comments from individuals including: 1620 Shel Kaphan, Paul Leach, Koen Holtman, David Morris, and Larry Masinter. 1618 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> 1619 <p id="rfc.section.7.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 12</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 1621 1620 </p> 1622 1621 <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References … … 2113 2112 </li> 2114 2113 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 2115 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.4</a>, <a href="#rfc.xref.Part1.2">1.4.1</a>, <a href="#rfc.xref.Part1.3">1.4.1</a>, <a href="#rfc.xref.Part1.4">1.4.1</a>, <a href="#rfc.xref.Part1.5">1.4.1</a>, <a href="#rfc.xref.Part1.6">1.4.2</a>, <a href="#rfc.xref.Part1.7">1.4.2</a>, <a href="#rfc.xref.Part1.8">1.4.2</a>, <a href="#rfc.xref.Part1.9">1.4.2</a>, <a href="#rfc.xref.Part1.10">1.4.2</a>, <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.12">2.3.2</a>, <a href="#rfc.xref.Part1.13">2.5</a>, <a href="#rfc.xref.Part1.14">2.5</a>, <a href="#rfc.xref.Part1.15">2.5</a>, <a href="#rfc.xref.Part1.16">2.7</a>, <a href="#rfc.xref.Part1.17">3.3</a>, <a href="# Part1"><b>8.1</b></a><ul>2114 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.4</a>, <a href="#rfc.xref.Part1.2">1.4.1</a>, <a href="#rfc.xref.Part1.3">1.4.1</a>, <a href="#rfc.xref.Part1.4">1.4.1</a>, <a href="#rfc.xref.Part1.5">1.4.1</a>, <a href="#rfc.xref.Part1.6">1.4.2</a>, <a href="#rfc.xref.Part1.7">1.4.2</a>, <a href="#rfc.xref.Part1.8">1.4.2</a>, <a href="#rfc.xref.Part1.9">1.4.2</a>, <a href="#rfc.xref.Part1.10">1.4.2</a>, <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.12">2.3.2</a>, <a href="#rfc.xref.Part1.13">2.5</a>, <a href="#rfc.xref.Part1.14">2.5</a>, <a href="#rfc.xref.Part1.15">2.5</a>, <a href="#rfc.xref.Part1.16">2.7</a>, <a href="#rfc.xref.Part1.17">3.3</a>, <a href="#rfc.xref.Part1.18">7</a>, <a href="#Part1"><b>8.1</b></a><ul> 2116 2115 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.1">1.4</a></li> 2117 2116 <li><em>Section 1.2.2</em> <a href="#rfc.xref.Part1.2">1.4.1</a>, <a href="#rfc.xref.Part1.3">1.4.1</a>, <a href="#rfc.xref.Part1.4">1.4.1</a>, <a href="#rfc.xref.Part1.5">1.4.1</a></li> … … 2122 2121 <li><em>Section 9.3</em> <a href="#rfc.xref.Part1.12">2.3.2</a></li> 2123 2122 <li><em>Section 9.9</em> <a href="#rfc.xref.Part1.9">1.4.2</a></li> 2123 <li><em>Section 12</em> <a href="#rfc.xref.Part1.18">7</a></li> 2124 2124 </ul> 2125 2125 </li> -
draft-ietf-httpbis/latest/p6-cache.xml
r1333 r1364 16 16 <!ENTITY ID-YEAR "2011"> 17 17 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 18 <!ENTITY acks "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 18 19 <!ENTITY basic-rules "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 20 <!ENTITY uri "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 1933 1934 </section> 1934 1935 1935 <section anchor="ack" title="Acknowledgments"> 1936 <t> 1937 Much of the content and presentation of the caching design is due to 1938 suggestions and comments from individuals including: Shel Kaphan, Paul 1939 Leach, Koen Holtman, David Morris, and Larry Masinter. 1936 <section title="Acknowledgments" anchor="acks"> 1937 <t> 1938 See &acks;. 1940 1939 </t> 1941 1940 </section> -
draft-ietf-httpbis/latest/p7-auth.html
r1363 r1364 573 573 </ul> 574 574 </li> 575 <li>7. <a href="#ack ">Acknowledgments</a></li>575 <li>7. <a href="#acks">Acknowledgments</a></li> 576 576 <li>8. <a href="#rfc.references">References</a><ul> 577 577 <li>8.1 <a href="#rfc.references.1">Normative References</a></li> … … 926 926 for discarding cached credentials under user control. 927 927 </p> 928 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="ack " href="#ack">Acknowledgments</a></h1>928 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> 929 929 <p id="rfc.section.7.p.1">This specification takes over the definition of the HTTP Authentication Framework, previously defined in <cite title="HTTP Authentication: Basic and Digest Access Authentication" id="rfc.xref.RFC2617.3">RFC 2617</cite>. We thank John Franks, Phillip M. Hallam-Baker, Jeffery L. Hostetler, Scott D. Lawrence, Paul J. Leach, Ari Luotonen, and 930 930 Lawrence C. Stewart for their work on that specification. See <a href="http://tools.ietf.org/html/rfc2617#section-6">Section 6</a> of <a href="#RFC2617" id="rfc.xref.RFC2617.4"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a> for further acknowledgements. 931 </p> 932 <p id="rfc.section.7.p.2">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 12</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the Acknowledgments related to this document revision. 931 933 </p> 932 934 <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References … … 1173 1175 </li> 1174 1176 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 1175 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">2.2</a>, <a href="#rfc.xref.Part1.7">2.3.1</a>, <a href="#rfc.xref.Part1.8">4.2</a>, <a href="#rfc.xref.Part1.9">4.4</a>, <a href="# Part1"><b>8.1</b></a><ul>1177 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">2.2</a>, <a href="#rfc.xref.Part1.7">2.3.1</a>, <a href="#rfc.xref.Part1.8">4.2</a>, <a href="#rfc.xref.Part1.9">4.4</a>, <a href="#rfc.xref.Part1.10">7</a>, <a href="#Part1"><b>8.1</b></a><ul> 1176 1178 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.1">1.2</a></li> 1177 1179 <li><em>Section 1.2.2</em> <a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a></li> 1178 1180 <li><em>Section 2.2</em> <a href="#rfc.xref.Part1.7">2.3.1</a></li> 1179 1181 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.6">2.2</a>, <a href="#rfc.xref.Part1.8">4.2</a>, <a href="#rfc.xref.Part1.9">4.4</a></li> 1182 <li><em>Section 12</em> <a href="#rfc.xref.Part1.10">7</a></li> 1180 1183 </ul> 1181 1184 </li> -
draft-ietf-httpbis/latest/p7-auth.xml
r1363 r1364 18 18 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 19 <!ENTITY notation-abnf "<xref target='Part1' x:rel='#notation.abnf' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 20 <!ENTITY acks "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 20 21 <!ENTITY basic-rules "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 21 22 <!ENTITY effective-request-uri "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 788 789 </section> 789 790 790 <section title="Acknowledgments" anchor="ack ">791 <section title="Acknowledgments" anchor="acks"> 791 792 <t> 792 793 This specification takes over the definition of the HTTP Authentication … … 796 797 on that specification. See <xref target="RFC2617" x:format="of" x:sec="6"/> 797 798 for further acknowledgements. 799 </t> 800 <t> 801 See &acks; for the Acknowledgments related to this document revision. 798 802 </t> 799 803 </section>
Note: See TracChangeset
for help on using the changeset viewer.