Changeset 446 for draft-ietf-httpbis/latest/p3-payload.html
- Timestamp:
- 20/02/09 14:59:11 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r443 r446 69 69 page-break-after: avoid; 70 70 } 71 h2 a { 72 color: black; 73 } 74 h3 { 71 h3, h4, h5, h6 { 75 72 font-size: 10pt; 76 73 page-break-after: avoid; 77 74 } 78 h3 a { 79 color: black; 80 } 81 h4 { 82 font-size: 10pt; 83 page-break-after: avoid; 84 } 85 h4 a { 86 color: black; 87 } 88 h5 { 89 font-size: 10pt; 90 page-break-after: avoid; 91 } 92 h5 a { 75 h2 a, h3 a, h4 a, h5 a, h6 a { 93 76 color: black; 94 77 } … … 389 372 <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 390 373 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 391 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.4 15, 2009-01-29 15:06:08, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">374 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.421, 2009-02-20 13:12:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 392 375 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 393 376 <meta name="DC.Creator" content="Fielding, R."> … … 485 468 <tr> 486 469 <td class="header left"></td> 487 <td class="header right">February 2 , 2009</td>470 <td class="header right">February 20, 2009</td> 488 471 </tr> 489 472 </table> 490 473 <p class="title">HTTP/1.1, part 3: Message Payload and Content Negotiation<br><span class="filename">draft-ietf-httpbis-p3-payload-latest</span></p> 491 474 <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1> 492 <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she 493 is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 494 6 of BCP 79. 475 <p>This Internet-Draft is submitted to IETF pursuant to, and in full conformance with, the provisions of BCP 78 and BCP 79. This 476 document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 477 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to 478 allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) 479 controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative 480 works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate 481 it into languages other than English. 495 482 </p> 496 483 <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note … … 506 493 </p> 507 494 <p>This Internet-Draft will expire in August 2009.</p> 495 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 496 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 497 <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date 498 of publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. 499 </p> 508 500 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 509 501 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information … … 618 610 </ul> 619 611 </li> 620 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>621 612 <li class="tocline0"><a href="#rfc.index">Index</a></li> 622 613 </ul> … … 1411 1402 <tr> 1412 1403 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> 1413 <td class="top">International Organization for Standardization, “ 1414 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 1415 ”, ISO/IEC 8859-1:1998, 1998. 1416 </td> 1404 <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1”, ISO/IEC 8859-1:1998, 1998.</td> 1417 1405 </tr> 1418 1406 <tr> … … 1535 1523 <tr> 1536 1524 <td class="reference"><b id="RFC2388">[RFC2388]</b></td> 1537 <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms: 1525 <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC 2388, August 1998. 1538 1526 </td> 1539 1527 </tr> … … 1893 1881 <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> 1894 1882 </ul> 1895 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>1896 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the1897 authors retain all their rights.1898 </p>1899 <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION1900 HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE1901 DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN1902 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.1903 </p>1904 <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>1905 <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might1906 be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any1907 license under such rights might or might not be available; nor does it represent that it has made any independent effort to1908 identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and1909 BCP 79.1910 </p>1911 <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result1912 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users1913 of this specification can be obtained from the IETF on-line IPR repository at <<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>>.1914 </p>1915 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary1916 rights that may cover technology that may be required to implement this standard. Please address the information to the IETF1917 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.1918 </p>1919 1883 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1920 1884 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.U">U</a>
Note: See TracChangeset
for help on using the changeset viewer.