![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 1639 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 30/03/12 14:23:00 (9 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/latest/p2-semantics.html (modified) (16 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1635 r1639 460 460 } 461 461 @bottom-center { 462 content: "Expires September 30, 2012";462 content: "Expires October 1, 2012"; 463 463 } 464 464 @bottom-right { … … 504 504 <meta name="dct.creator" content="Reschke, J. F."> 505 505 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 506 <meta name="dct.issued" scheme="ISO8601" content="2012-03- 29">506 <meta name="dct.issued" scheme="ISO8601" content="2012-03-30"> 507 507 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 508 508 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext 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."> … … 535 535 </tr> 536 536 <tr> 537 <td class="left">Expires: September 30, 2012</td>537 <td class="left">Expires: October 1, 2012</td> 538 538 <td class="right">greenbytes</td> 539 539 </tr> 540 540 <tr> 541 541 <td class="left"></td> 542 <td class="right">March 29, 2012</td>542 <td class="right">March 30, 2012</td> 543 543 </tr> 544 544 </tbody> … … 570 570 in progress”. 571 571 </p> 572 <p>This Internet-Draft will expire on September 30, 2012.</p>572 <p>This Internet-Draft will expire on October 1, 2012.</p> 573 573 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 574 574 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2814 2814 <h2 id="rfc.references.1"><a href="#rfc.section.11.1" id="rfc.section.11.1">11.1</a> Normative References 2815 2815 </h2> 2816 <table> 2816 <table> 2817 2817 <tr> 2818 2818 <td class="reference"><b id="Part1">[Part1]</b></td> … … 2846 2846 </tr> 2847 2847 <tr> 2848 <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 2849 <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. 2850 </td> 2851 </tr> 2852 <tr> 2853 <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 2854 <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. 2855 </td> 2856 </tr> 2857 <tr> 2858 <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 2859 <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. 2860 </td> 2861 </tr> 2862 <tr> 2863 <td class="reference"><b id="RFC2045">[RFC2045]</b></td> 2864 <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>”, RFC 2045, November 1996. 2865 </td> 2866 </tr> 2867 <tr> 2868 <td class="reference"><b id="RFC2046">[RFC2046]</b></td> 2869 <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC 2046, November 1996. 2870 </td> 2871 </tr> 2872 <tr> 2848 2873 <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 2849 2874 <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997. … … 2856 2881 </tr> 2857 2882 <tr> 2883 <td class="reference"><b id="RFC4647">[RFC4647]</b></td> 2884 <td class="top"><a href="mailto:addison@inter-locale.com" title="Yahoo! Inc.">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@macchiato.com" title="Google">M. Davis, Ed.</a>, “<a href="http://tools.ietf.org/html/rfc4647">Matching of Language Tags</a>”, BCP 47, RFC 4647, September 2006. 2885 </td> 2886 </tr> 2887 <tr> 2858 2888 <td class="reference"><b id="RFC5234">[RFC5234]</b></td> 2859 2889 <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD 68, RFC 5234, January 2008. 2890 </td> 2891 </tr> 2892 <tr> 2893 <td class="reference"><b id="RFC5646">[RFC5646]</b></td> 2894 <td class="top"><a href="mailto:addison@inter-locale.com" title="Lab126">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@google.com" title="Google">M. Davis, Ed.</a>, “<a href="http://tools.ietf.org/html/rfc5646">Tags for Identifying Languages</a>”, BCP 47, RFC 5646, September 2009. 2860 2895 </td> 2861 2896 </tr> … … 2863 2898 <h2 id="rfc.references.2"><a href="#rfc.section.11.2" id="rfc.section.11.2">11.2</a> Informative References 2864 2899 </h2> 2865 <table> 2900 <table> 2866 2901 <tr> 2867 2902 <td class="reference"><b id="RFC1123">[RFC1123]</b></td> … … 2875 2910 </tr> 2876 2911 <tr> 2912 <td class="reference"><b id="RFC2049">[RFC2049]</b></td> 2913 <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC 2049, November 1996. 2914 </td> 2915 </tr> 2916 <tr> 2877 2917 <td class="reference"><b id="RFC2068">[RFC2068]</b></td> 2878 2918 <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a href="mailto:timbl@w3.org" title="MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2068, January 1997. 2919 </td> 2920 </tr> 2921 <tr> 2922 <td class="reference"><b id="RFC2076">[RFC2076]</b></td> 2923 <td class="top"><a href="mailto:jpalme@dsv.su.se" title="Stockholm University/KTH">Palme, J.</a>, “<a href="http://tools.ietf.org/html/rfc2076">Common Internet Message Headers</a>”, RFC 2076, February 1997. 2924 </td> 2925 </tr> 2926 <tr> 2927 <td class="reference"><b id="RFC2277">[RFC2277]</b></td> 2928 <td class="top"><a href="mailto:Harald.T.Alvestrand@uninett.no" title="UNINETT">Alvestrand, H.</a>, “<a href="http://tools.ietf.org/html/rfc2277">IETF Policy on Character Sets and Languages</a>”, BCP 18, RFC 2277, January 1998. 2929 </td> 2930 </tr> 2931 <tr> 2932 <td class="reference"><b id="RFC2295">[RFC2295]</b></td> 2933 <td class="top"><a href="mailto:koen@win.tue.nl" title="Technische Universiteit Eindhoven">Holtman, K.</a> and <a href="mailto:mutz@hpl.hp.com" title="Hewlett-Packard Company">A. Mutz</a>, “<a href="http://tools.ietf.org/html/rfc2295">Transparent Content Negotiation in HTTP</a>”, RFC 2295, March 1998. 2934 </td> 2935 </tr> 2936 <tr> 2937 <td class="reference"><b id="RFC2388">[RFC2388]</b></td> 2938 <td class="top"><a href="mailto:masinter@parc.xerox.com" 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. 2939 </td> 2940 </tr> 2941 <tr> 2942 <td class="reference"><b id="RFC2557">[RFC2557]</b></td> 2943 <td class="top"><a href="mailto:jpalme@dsv.su.se" title="Stockholm University and KTH">Palme, F.</a>, <a href="mailto:alexhop@microsoft.com" title="Microsoft Corporation">Hopmann, A.</a>, <a href="mailto:Shelness@lotus.com" title="Lotus Development Corporation">Shelness, N.</a>, and <a href="mailto:stef@nma.com">E. Stefferud</a>, “<a href="http://tools.ietf.org/html/rfc2557">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC 2557, March 1999. 2879 2944 </td> 2880 2945 </tr> … … 2890 2955 </tr> 2891 2956 <tr> 2957 <td class="reference"><b id="RFC3629">[RFC3629]</b></td> 2958 <td class="top"><a href="mailto:fyergeau@alis.com" title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, STD 63, RFC 3629, November 2003. 2959 </td> 2960 </tr> 2961 <tr> 2892 2962 <td class="reference"><b id="RFC3864">[RFC3864]</b></td> 2893 2963 <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP 90, RFC 3864, September 2004. 2964 </td> 2965 </tr> 2966 <tr> 2967 <td class="reference"><b id="RFC4288">[RFC4288]</b></td> 2968 <td class="top"><a href="mailto:ned.freed@mrochek.com" title="Sun Microsystems">Freed, N.</a> and <a href="mailto:klensin+ietf@jck.com">J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP 13, RFC 4288, December 2005. 2894 2969 </td> 2895 2970 </tr> … … 2912 2987 <td class="reference"><b id="RFC5987">[RFC5987]</b></td> 2913 2988 <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http://tools.ietf.org/html/rfc5987">Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters</a>”, RFC 5987, August 2010. 2989 </td> 2990 </tr> 2991 <tr> 2992 <td class="reference"><b id="RFC6151">[RFC6151]</b></td> 2993 <td class="top">Turner, S. and L. Chen, “<a href="http://tools.ietf.org/html/rfc6151">Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms</a>”, RFC 6151, March 2011. 2994 </td> 2995 </tr> 2996 <tr> 2997 <td class="reference"><b id="RFC6266">[RFC6266]</b></td> 2998 <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http://tools.ietf.org/html/rfc6266">Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a>”, RFC 6266, June 2011. 2914 2999 </td> 2915 3000 </tr> … … 3672 3757 </ul> 3673 3758 </li> 3759 <li><em>RFC1950</em> <a href="#RFC1950"><b>11.1</b></a></li> 3760 <li><em>RFC1951</em> <a href="#RFC1951"><b>11.1</b></a></li> 3761 <li><em>RFC1952</em> <a href="#RFC1952"><b>11.1</b></a></li> 3762 <li><em>RFC2045</em> <a href="#RFC2045"><b>11.1</b></a></li> 3763 <li><em>RFC2046</em> <a href="#RFC2046"><b>11.1</b></a></li> 3764 <li><em>RFC2049</em> <a href="#RFC2049"><b>11.2</b></a></li> 3674 3765 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">4.5</a>, <a href="#rfc.xref.RFC2068.2">4.5</a>, <a href="#RFC2068"><b>11.2</b></a><ul> 3675 3766 <li><em>Section 10.3</em> <a href="#rfc.xref.RFC2068.2">4.5</a></li> … … 3677 3768 </ul> 3678 3769 </li> 3770 <li><em>RFC2076</em> <a href="#RFC2076"><b>11.2</b></a></li> 3679 3771 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>11.1</b></a></li> 3772 <li><em>RFC2277</em> <a href="#RFC2277"><b>11.2</b></a></li> 3773 <li><em>RFC2295</em> <a href="#RFC2295"><b>11.2</b></a></li> 3774 <li><em>RFC2388</em> <a href="#RFC2388"><b>11.2</b></a></li> 3775 <li><em>RFC2557</em> <a href="#RFC2557"><b>11.2</b></a></li> 3680 3776 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">4.5</a>, <a href="#RFC2616"><b>11.2</b></a>, <a href="#rfc.xref.RFC2616.3">C.1</a><ul> 3681 3777 <li><em>Section 10.3.8</em> <a href="#rfc.xref.RFC2616.2">4.5</a></li> … … 3686 3782 </ul> 3687 3783 </li> 3784 <li><em>RFC3629</em> <a href="#RFC3629"><b>11.2</b></a></li> 3688 3785 <li><em>RFC3864</em> <a href="#rfc.xref.RFC3864.1">3.1</a>, <a href="#rfc.xref.RFC3864.2">3.1</a>, <a href="#rfc.xref.RFC3864.3">8.3</a>, <a href="#RFC3864"><b>11.2</b></a><ul> 3689 3786 <li><em>Section 4.1</em> <a href="#rfc.xref.RFC3864.2">3.1</a></li> … … 3695 3792 </ul> 3696 3793 </li> 3794 <li><em>RFC4288</em> <a href="#RFC4288"><b>11.2</b></a></li> 3795 <li><em>RFC4647</em> <a href="#RFC4647"><b>11.1</b></a></li> 3697 3796 <li><em>RFC5226</em> <a href="#rfc.xref.RFC5226.1">2.2</a>, <a href="#rfc.xref.RFC5226.2">4.2</a>, <a href="#RFC5226"><b>11.2</b></a><ul> 3698 3797 <li><em>Section 4.1</em> <a href="#rfc.xref.RFC5226.1">2.2</a>, <a href="#rfc.xref.RFC5226.2">4.2</a></li> … … 3709 3808 </ul> 3710 3809 </li> 3810 <li><em>RFC5646</em> <a href="#RFC5646"><b>11.1</b></a></li> 3711 3811 <li><em>RFC5789</em> <a href="#rfc.xref.RFC5789.1">2.3.5</a>, <a href="#RFC5789"><b>11.2</b></a></li> 3712 3812 <li><em>RFC5987</em> <a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#RFC5987"><b>11.2</b></a></li> 3813 <li><em>RFC6151</em> <a href="#RFC6151"><b>11.2</b></a></li> 3814 <li><em>RFC6266</em> <a href="#RFC6266"><b>11.2</b></a></li> 3713 3815 </ul> 3714 3816 </li>
Note: See TracChangeset
for help on using the changeset viewer.
