Changeset 461 for draft-ietf-httpbis
- Timestamp:
- 02/03/09 12:42:53 (13 years ago)
- Location:
- draft-ietf-httpbis/latest-roy
- Files:
-
- 1 added
- 15 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest-roy/Makefile
r446 r461 5 5 stylesheet = ../myxml2rfc.xslt 6 6 reduction = ../../rfc2629xslt/clean-for-DTD.xslt 7 bap = ../../abnfparser/bap 7 8 8 9 TARGETS = p1-messaging.html \ … … 27 28 p6-cache.txt \ 28 29 p7-auth.txt \ 30 p1-messaging.abnf \ 31 p2-semantics.abnf \ 32 p3-payload.abnf \ 33 p4-conditional.abnf \ 34 p5-range.abnf \ 35 p6-cache.abnf \ 36 p7-auth.abnf \ 37 p1-messaging.parsed-abnf \ 38 p2-semantics.parsed-abnf \ 39 p3-payload.parsed-abnf \ 40 p4-conditional.parsed-abnf \ 41 p5-range.parsed-abnf \ 42 p6-cache.parsed-abnf \ 43 p7-auth.parsed-abnf \ 44 p1-messaging.abnf-appendix \ 45 p2-semantics.abnf-appendix \ 46 p3-payload.abnf-appendix \ 47 p4-conditional.abnf-appendix \ 48 p5-range.abnf-appendix \ 49 p6-cache.abnf-appendix \ 50 p7-auth.abnf-appendix \ 29 51 p1-messaging.iana-headers \ 30 52 p2-semantics.iana-headers \ … … 51 73 %.txt: %.redxml 52 74 $(xml2rfc) $< $@ 75 76 %.abnf: %.xml ../../rfc2629xslt/extract-artwork.xslt 77 $(saxon) $< ../../rfc2629xslt/extract-artwork.xslt type="abnf2616" >$@ 78 79 %.parsed-abnf: %.abnf 80 $(bap)/bap -i $(bap)/core.abnf < $< | sort | $(bap)/bap -i $(bap)/core.abnf -l 69 >$@ 81 82 %.abnf-appendix: %.parsed-abnf 83 $(saxon) $(basename $<).xml abnf2xml2rfc.xslt abnf="$<" >$@ 53 84 54 85 %.xhtml: %.xml ../../rfc2629xslt/rfc2629toXHTML.xslt -
draft-ietf-httpbis/latest-roy/p1-messaging.html
r446 r461 30 30 font-style: normal; 31 31 } 32 div.note { 33 margin-left: 2em; 34 } 32 35 dd { 33 36 margin-right: 2em; … … 146 149 border-width: 1px; 147 150 } 151 caption { 152 caption-side: bottom; 153 font-weight: bold; 154 font-size: 9pt; 155 margin-top: .5em; 156 } 157 148 158 table.header { 149 159 width: 95%; … … 317 327 } 318 328 @top-right { 319 content: " February2009";329 content: "March 2009"; 320 330 } 321 331 @top-center { … … 365 375 <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 366 376 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 367 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 1, 2009-02-20 13:12:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">377 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.424, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 368 378 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 369 379 <meta name="DC.Creator" content="Fielding, R."> … … 377 387 <meta name="DC.Creator" content="Reschke, J. F."> 378 388 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 379 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-0 2">389 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-03"> 380 390 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 381 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.">391 <meta name="DC.Description.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 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> 382 392 </head> 383 393 <body> … … 408 418 </tr> 409 419 <tr> 410 <td class="header left">Expires: August2009</td>420 <td class="header left">Expires: September 2009</td> 411 421 <td class="header right">HP</td> 412 422 </tr> … … 461 471 <tr> 462 472 <td class="header left"></td> 463 <td class="header right"> February 20, 2009</td>473 <td class="header right">March 2, 2009</td> 464 474 </tr> 465 475 </table> … … 485 495 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 486 496 </p> 487 <p>This Internet-Draft will expire in August2009.</p>497 <p>This Internet-Draft will expire in September 2009.</p> 488 498 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 489 499 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 492 502 </p> 493 503 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 494 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation504 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information 495 505 systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the 496 506 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part … … 521 531 <li class="tocline1">2.1 <a href="#uri">Uniform Resource Identifiers</a><ul class="toc"> 522 532 <li class="tocline1">2.1.1 <a href="#http.uri">http URI scheme</a></li> 523 <li class="tocline1">2.1.2 <a href="#uri.comparison">URI Comparison</a></li> 524 <li class="tocline1">2.1.3 <a href="#scheme.aliases">Scheme aliases considered harmful</a></li> 533 <li class="tocline1">2.1.2 <a href="#https.uri">https URI scheme</a></li> 534 <li class="tocline1">2.1.3 <a href="#uri.comparison">URI Comparison</a></li> 535 <li class="tocline1">2.1.4 <a href="#scheme.aliases">Scheme aliases considered harmful</a></li> 525 536 </ul> 526 537 </li> … … 543 554 </li> 544 555 <li class="tocline1">3.4 <a href="#product.tokens">Product Tokens</a></li> 556 <li class="tocline1">3.5 <a href="#quality.values">Quality Values</a></li> 545 557 </ul> 546 558 </li> … … 670 682 <p id="rfc.section.1.p.3">HTTP is also designed for use as a generic protocol for translating communication to and from other Internet information systems, 671 683 such as USENET news services via NNTP <a href="#RFC3977" id="rfc.xref.RFC3977.1"><cite title="Network News Transfer Protocol (NNTP)">[RFC3977]</cite></a>, file services via FTP <a href="#RFC959" id="rfc.xref.RFC959.1"><cite title="File Transfer Protocol">[RFC959]</cite></a>, Gopher <a href="#RFC1436" id="rfc.xref.RFC1436.1"><cite title="The Internet Gopher Protocol (a distributed document search and retrieval protocol)">[RFC1436]</cite></a>, and WAIS <a href="#WAIS" id="rfc.xref.WAIS.1"><cite title="WAIS Interface Protocol Prototype Functional Specification (v1.5)">[WAIS]</cite></a>. HTTP proxies and gateways provide access to alternative information services by translating their diverse protocols into 672 a hyper mediaformat that can be viewed and manipulated by clients in the same way as HTTP services.673 </p> 674 <p id="rfc.section.1.p.4">One consequence of HTTP flexibility is that we cannot define the protocol in terms of how to implement it behind the interface.675 Instead, we are limited to restricting the syntax of communication, defining the intent of received communication, and the676 expected behavior of recipients. If the communication is considered in isolation, then successful actions should be reflected677 in the observable interface provided by servers. However, since many clients are potentially acting in parallel and perhaps678 at cross-purposes,it would be meaningless to require that such behavior be observable.684 a hypertext format that can be viewed and manipulated by clients in the same way as HTTP services. 685 </p> 686 <p id="rfc.section.1.p.4">One consequence of HTTP flexibility is that the protocol cannot be defined in terms of what occurs behind the interface. Instead, 687 we are limited to defining the syntax of communication, the intent of received communication, and the expected behavior of 688 recipients. If the communication is considered in isolation, then successful actions should be reflected in the observable 689 interface provided by servers. However, since many clients are potentially acting in parallel and perhaps at cross-purposes, 690 it would be meaningless to require that such behavior be observable. 679 691 </p> 680 692 <p id="rfc.section.1.p.5">This document is Part 1 of the seven-part specification of HTTP, defining the protocol referred to as "HTTP/1.1" and obsoleting <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. Part 1 defines the URI schemes specific to HTTP-based resources, overall network operation, transport protocol connection … … 721 733 </pre><p id="rfc.section.1.2.1.p.6">For compatibility with legacy list rules, recipients <em class="bcp14">SHOULD</em> accept empty list elements. In other words, consumers would follow the list productions: 722 734 </p> 723 <div id="rfc.figure.u.4"></div><pre class="text"> #element => [ ( "," / element ) *( OWS "," [ OWS element ] ) ]724 725 1#element => *( "," OWS ) element *( OWS "," [ OWS element ] )735 <div id="rfc.figure.u.4"></div><pre class="text"> #element => [ ( "," / element ) *( OWS "," [ OWS element ] ) ] 736 737 1#element => *( "," OWS ) element *( OWS "," [ OWS element ] ) 726 738 </pre><p id="rfc.section.1.2.1.p.8"> <a href="#collected.abnf" title="Collected ABNF">Appendix D</a> shows the collected ABNF, with the list rules expanded as explained above. 727 739 </p> … … 781 793 <div id="rfc.figure.u.9"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">request-header</a> = <request-header, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a>> 782 794 <a href="#abnf.dependencies" class="smpl">response-header</a> = <response-header, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a>> 783 </pre><div id="rfc.figure.u.10"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">accept-params</a> = <accept-params, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 5.1</a>> 784 <a href="#abnf.dependencies" class="smpl">entity-body</a> = <entity-body, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.body" title="Entity Body">Section 3.2</a>> 785 <a href="#abnf.dependencies" class="smpl">entity-header</a> = <entity-header, defined in <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>> 795 </pre><div id="rfc.figure.u.10"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">entity-body</a> = <entity-body, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.body" title="Entity Body">Section 3.2</a>> 796 <a href="#abnf.dependencies" class="smpl">entity-header</a> = <entity-header, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>> 786 797 </pre><div id="rfc.figure.u.11"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Cache-Control</a> = <Cache-Control, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 3.4</a>> 787 798 <a href="#abnf.dependencies" class="smpl">Pragma</a> = <Pragma, defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 3.4</a>> … … 821 832 <div id="rfc.iref.h.1"></div> 822 833 <div id="rfc.iref.u.1"></div> 823 <p id="rfc.section.2.1.1.p.1">The "http" scheme is used to locate network resources via the HTTP protocol. This section defines the syntax and semantics 824 for identifiers using the http or https URI schemes. 825 </p> 834 <p id="rfc.section.2.1.1.p.1">The "http" scheme is used to locate network resources via the HTTP protocol.</p> 826 835 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.30"></span> <a href="#http.uri" class="smpl">http-URI</a> = "http:" "//" <a href="#uri" class="smpl">authority</a> <a href="#uri" class="smpl">path-abempty</a> [ "?" <a href="#uri" class="smpl">query</a> ] 827 836 </pre><p id="rfc.section.2.1.1.p.3">If the port is empty or not given, port 80 is assumed. The semantics are that the identified resource is located at the server 828 837 listening for TCP connections on that port of that host, and the request-target for the resource is path-absolute (<a href="#request-target" title="request-target">Section 5.1.2</a>). The use of IP addresses in URLs <em class="bcp14">SHOULD</em> be avoided whenever possible (see <a href="#RFC1900" id="rfc.xref.RFC1900.1"><cite title="Renumbering Needs Work">[RFC1900]</cite></a>). If the path-absolute is not present in the URL, it <em class="bcp14">MUST</em> be given as "/" when used as a request-target for a resource (<a href="#request-target" title="request-target">Section 5.1.2</a>). If a proxy receives a host name which is not a fully qualified domain name, it <em class="bcp14">MAY</em> add its domain to the host name it received. If a proxy receives a fully qualified domain name, the proxy <em class="bcp14">MUST NOT</em> change the host name. 829 838 </p> 839 <div id="rfc.iref.h.2"></div> 840 <div id="rfc.iref.u.2"></div> 841 <h3 id="rfc.section.2.1.2"><a href="#rfc.section.2.1.2">2.1.2</a> <a id="https.uri" href="#https.uri">https URI scheme</a></h3> 842 <p id="rfc.section.2.1.2.p.1"> <span class="comment">[rfc.comment.1: TBD: Define and explain purpose of https scheme.]</span> 843 </p> 830 844 <dl class="empty"> 831 <dd> < span id="rfc.iref.h.2"></span> <span id="rfc.iref.u.2"></span> <b>Note:</b> the "https" scheme is defined in <a href="#RFC2818" id="rfc.xref.RFC2818.1"><cite title="HTTP Over TLS">[RFC2818]</cite></a>.845 <dd> <b>Note:</b> the "https" scheme is defined in <a href="#RFC2818" id="rfc.xref.RFC2818.1"><cite title="HTTP Over TLS">[RFC2818]</cite></a>. 832 846 </dd> 833 847 </dl> 834 <h3 id="rfc.section.2.1. 2"><a href="#rfc.section.2.1.2">2.1.2</a> <a id="uri.comparison" href="#uri.comparison">URI Comparison</a></h3>835 <p id="rfc.section.2.1. 2.p.1">When comparing two URIs to decide if they match or not, a client <em class="bcp14">SHOULD</em> use a case-sensitive octet-by-octet comparison of the entire URIs, with these exceptions:848 <h3 id="rfc.section.2.1.3"><a href="#rfc.section.2.1.3">2.1.3</a> <a id="uri.comparison" href="#uri.comparison">URI Comparison</a></h3> 849 <p id="rfc.section.2.1.3.p.1">When comparing two URIs to decide if they match or not, a client <em class="bcp14">SHOULD</em> use a case-sensitive octet-by-octet comparison of the entire URIs, with these exceptions: 836 850 </p> 837 851 <ul> … … 841 855 <li>Comparisons of scheme names <em class="bcp14">MUST</em> be case-insensitive; 842 856 </li> 843 <li>An empty path-absolute is equivalent to an path-absolute of "/".</li> 857 <li>An empty path-absolute is equivalent to a path-absolute of "/".</li> 858 <li>Characters other than those in the "reserved" set are equivalent to their percent-encoded octets (see <a href="#RFC3986" id="rfc.xref.RFC3986.16"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>). 859 </li> 844 860 </ul> 845 <p id="rfc.section.2.1.2.p.2">Characters other than those in the "reserved" set (see <a href="#RFC3986" id="rfc.xref.RFC3986.16"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.2">Section 2.2</a>) are equivalent to their ""%" <a href="#core.rules" class="smpl">HEXDIG</a> <a href="#core.rules" class="smpl">HEXDIG</a>" encoding. 846 </p> 847 <p id="rfc.section.2.1.2.p.3">For example, the following three URIs are equivalent:</p> 861 <p id="rfc.section.2.1.3.p.2">For example, the following three URIs are equivalent:</p> 848 862 <div id="rfc.figure.u.14"></div><pre class="text"> http://example.com:80/~smith/home.html 849 863 http://EXAMPLE.com/%7Esmith/home.html 850 864 http://EXAMPLE.com:/%7esmith/home.html 851 </pre><h3 id="rfc.section.2.1. 3"><a href="#rfc.section.2.1.3">2.1.3</a> <a id="scheme.aliases" href="#scheme.aliases">Scheme aliases considered harmful</a></h3>865 </pre><h3 id="rfc.section.2.1.4"><a href="#rfc.section.2.1.4">2.1.4</a> <a id="scheme.aliases" href="#scheme.aliases">Scheme aliases considered harmful</a></h3> 852 866 <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a> <a id="intro.overall.operation" href="#intro.overall.operation">Overall Operation</a></h2> 853 867 <p id="rfc.section.2.2.p.1">HTTP is a request/response protocol. A client sends a request to the server in the form of a request method, URI, and protocol … … 910 924 </p> 911 925 <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a> <a id="http.proxy" href="#http.proxy">Use of HTTP for proxy communication</a></h2> 912 <p id="rfc.section.2.3.p.1"> <span class="comment">[rfc.comment. 1: TBD: Configured to use HTTP to proxy HTTP or other protocols.]</span>926 <p id="rfc.section.2.3.p.1"> <span class="comment">[rfc.comment.2: TBD: Configured to use HTTP to proxy HTTP or other protocols.]</span> 913 927 </p> 914 928 <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a> <a id="http.intercept" href="#http.intercept">Interception of HTTP for access control</a></h2> 915 <p id="rfc.section.2.4.p.1"> <span class="comment">[rfc.comment. 2: TBD: Interception of HTTP traffic for initiating access control.]</span>929 <p id="rfc.section.2.4.p.1"> <span class="comment">[rfc.comment.3: TBD: Interception of HTTP traffic for initiating access control.]</span> 916 930 </p> 917 931 <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a> <a id="http.others" href="#http.others">Use of HTTP by other protocols</a></h2> 918 <p id="rfc.section.2.5.p.1"> <span class="comment">[rfc.comment. 3: TBD: Profiles of HTTP defined by other protocol. Extensions of HTTP like WebDAV.]</span>932 <p id="rfc.section.2.5.p.1"> <span class="comment">[rfc.comment.4: TBD: Profiles of HTTP defined by other protocol. Extensions of HTTP like WebDAV.]</span> 919 933 </p> 920 934 <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a> <a id="http.media" href="#http.media">Use of HTTP by media type specification</a></h2> 921 <p id="rfc.section.2.6.p.1"> <span class="comment">[rfc.comment. 4: TBD: Instructions on composing HTTP requests via hypertext formats.]</span>935 <p id="rfc.section.2.6.p.1"> <span class="comment">[rfc.comment.5: TBD: Instructions on composing HTTP requests via hypertext formats.]</span> 922 936 </p> 923 937 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1> … … 956 970 <h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a> <a id="full.date" href="#full.date">Full Date</a></h3> 957 971 <p id="rfc.section.3.2.1.p.1">HTTP applications have historically allowed three different formats for the representation of date/time stamps:</p> 958 <div id="rfc.figure.u.19"></div><pre class="text"> 959 960 972 <div id="rfc.figure.u.19"></div><pre class="text"> Sun, 06 Nov 1994 08:49:37 GMT ; RFC 1123 973 Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format 974 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format 961 975 </pre><p id="rfc.section.3.2.1.p.3">The first format is preferred as an Internet standard and represents a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>. The other formats are described here only for compatibility with obsolete implementations. HTTP/1.1 clients and servers 962 976 that parse the date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields. See <a href="#tolerant.applications" title="Tolerant Applications">Appendix A</a> for further information. … … 1049 1063 </p> 1050 1064 <p id="rfc.section.3.3.p.8">The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry 1051 contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section 3.3.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3. 6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).1052 </p> 1053 <p id="rfc.section.3.3.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3. 7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).1065 contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section 3.3.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). 1066 </p> 1067 <p id="rfc.section.3.3.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). 1054 1068 </p> 1055 1069 <p id="rfc.section.3.3.p.10">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Not Implemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client. … … 1123 1137 <a href="#product.tokens" class="smpl">product-version</a> = <a href="#rule.token.separators" class="smpl">token</a> 1124 1138 </pre><p id="rfc.section.3.4.p.3">Examples:</p> 1125 <div id="rfc.figure.u.26"></div><pre class="text"> 1126 1139 <div id="rfc.figure.u.26"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 1140 Server: Apache/0.8.4 1127 1141 </pre><p id="rfc.section.3.4.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token character <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value). 1128 1142 </p> 1143 <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a> <a id="quality.values" href="#quality.values">Quality Values</a></h2> 1144 <p id="rfc.section.3.5.p.1">Both transfer codings (TE request header, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section 8.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight 1145 is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has 1146 a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion. 1147 </p> 1148 <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.61"></span> <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] ) 1149 / ( "1" [ "." 0*3("0") ] ) 1150 </pre><div class="note"> 1151 <p> <b>Note:</b> "Quality values" is a misnomer, since these values merely represent relative degradation in desired quality. 1152 </p> 1153 </div> 1129 1154 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="http.message" href="#http.message">HTTP Message</a></h1> 1130 1155 <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a> <a id="message.types" href="#message.types">Message Types</a></h2> 1131 1156 <p id="rfc.section.4.1.p.1">HTTP messages consist of requests from client to server and responses from server to client.</p> 1132 <div id="rfc.figure.u.2 7"></div><pre class="inline"><span id="rfc.iref.g.61"></span> <a href="#message.types" class="smpl">HTTP-message</a> = <a href="#request" class="smpl">Request</a> / <a href="#response" class="smpl">Response</a> ; HTTP/1.1 messages1157 <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.62"></span> <a href="#message.types" class="smpl">HTTP-message</a> = <a href="#request" class="smpl">Request</a> / <a href="#response" class="smpl">Response</a> ; HTTP/1.1 messages 1133 1158 </pre><p id="rfc.section.4.1.p.3">Request (<a href="#request" title="Request">Section 5</a>) and Response (<a href="#response" title="Response">Section 6</a>) messages use the generic message format of <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header 1134 1159 fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header 1135 1160 fields, and possibly a message-body. 1136 1161 </p> 1137 <div id="rfc.figure.u.2 8"></div><pre class="inline"><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span> <a href="#message.types" class="smpl">generic-message</a> = <a href="#message.types" class="smpl">start-line</a>1162 <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span> <a href="#message.types" class="smpl">generic-message</a> = <a href="#message.types" class="smpl">start-line</a> 1138 1163 *( <a href="#message.headers" class="smpl">message-header</a> <a href="#core.rules" class="smpl">CRLF</a> ) 1139 1164 <a href="#core.rules" class="smpl">CRLF</a> … … 1154 1179 case-insensitive. 1155 1180 </p> 1156 <div id="rfc.figure.u. 29"></div><pre class="inline"><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span><span id="rfc.iref.g.66"></span><span id="rfc.iref.g.67"></span> <a href="#message.headers" class="smpl">message-header</a> = <a href="#message.headers" class="smpl">field-name</a> ":" OWS [ <a href="#message.headers" class="smpl">field-value</a> ] OWS1181 <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.65"></span><span id="rfc.iref.g.66"></span><span id="rfc.iref.g.67"></span><span id="rfc.iref.g.68"></span> <a href="#message.headers" class="smpl">message-header</a> = <a href="#message.headers" class="smpl">field-name</a> ":" OWS [ <a href="#message.headers" class="smpl">field-value</a> ] OWS 1157 1182 <a href="#message.headers" class="smpl">field-name</a> = <a href="#rule.token.separators" class="smpl">token</a> 1158 1183 <a href="#message.headers" class="smpl">field-value</a> = *( <a href="#message.headers" class="smpl">field-content</a> / <a href="#rule.whitespace" class="smpl">OWS</a> ) … … 1179 1204 </p> 1180 1205 </div> 1181 <div id="rfc.figure.u.3 0"></div><pre class="inline"><span id="rfc.iref.g.68"></span><span id="rfc.iref.g.69"></span> <a href="#rule.comment" class="smpl">comment</a> = "(" *( <a href="#rule.comment" class="smpl">ctext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> / <a href="#rule.comment" class="smpl">comment</a> ) ")"1206 <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.69"></span><span id="rfc.iref.g.70"></span> <a href="#rule.comment" class="smpl">comment</a> = "(" *( <a href="#rule.comment" class="smpl">ctext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> / <a href="#rule.comment" class="smpl">comment</a> ) ")" 1182 1207 <a href="#rule.comment" class="smpl">ctext</a> = *( <a href="#rule.whitespace" class="smpl">OWS</a> / %x21-27 / %x2A-7E / <a href="#rule.quoted-string" class="smpl">obs-text</a> ) 1183 1208 </pre><p id="rfc.section.4.2.p.9">The order in which header fields with differing field names are received is not significant. However, it is "good practice" … … 1202 1227 header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.2" title="Transfer-Encoding">Section 8.7</a>). 1203 1228 </p> 1204 <div id="rfc.figure.u.3 1"></div><pre class="inline"><span id="rfc.iref.g.70"></span> <a href="#message.body" class="smpl">message-body</a> = <a href="#abnf.dependencies" class="smpl">entity-body</a>1229 <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.71"></span> <a href="#message.body" class="smpl">message-body</a> = <a href="#abnf.dependencies" class="smpl">entity-body</a> 1205 1230 / <entity-body encoded as per <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>> 1206 1231 </pre><p id="rfc.section.4.3.p.3">Transfer-Encoding <em class="bcp14">MUST</em> be used to indicate any transfer-codings applied by an application to ensure safe and proper transfer of the message. Transfer-Encoding … … 1270 1295 to the entity being transferred. These header fields apply only to the message being transmitted. 1271 1296 </p> 1272 <div id="rfc.figure.u.3 2"></div><pre class="inline"><span id="rfc.iref.g.71"></span> <a href="#general.header.fields" class="smpl">general-header</a> = <a href="#abnf.dependencies" class="smpl">Cache-Control</a> ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 3.2</a>1297 <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.72"></span> <a href="#general.header.fields" class="smpl">general-header</a> = <a href="#abnf.dependencies" class="smpl">Cache-Control</a> ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 3.2</a> 1273 1298 / <a href="#header.connection" class="smpl">Connection</a> ; <a href="#header.connection" id="rfc.xref.header.connection.1" title="Connection">Section 8.1</a> 1274 1299 / <a href="#header.date" class="smpl">Date</a> ; <a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section 8.3</a> … … 1287 1312 resource, the identifier of the resource, and the protocol version in use. 1288 1313 </p> 1289 <div id="rfc.figure.u.3 3"></div><pre class="inline"><span id="rfc.iref.g.72"></span> <a href="#request" class="smpl">Request</a> = <a href="#request-line" class="smpl">Request-Line</a> ; <a href="#request-line" title="Request-Line">Section 5.1</a>1314 <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.73"></span> <a href="#request" class="smpl">Request</a> = <a href="#request-line" class="smpl">Request-Line</a> ; <a href="#request-line" title="Request-Line">Section 5.1</a> 1290 1315 *(( <a href="#general.header.fields" class="smpl">general-header</a> ; <a href="#general.header.fields" title="General Header Fields">Section 4.5</a> 1291 1316 / <a href="#abnf.dependencies" class="smpl">request-header</a> ; <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a> … … 1297 1322 The elements are separated by SP characters. No CR or LF is allowed except in the final CRLF sequence. 1298 1323 </p> 1299 <div id="rfc.figure.u.3 4"></div><pre class="inline"><span id="rfc.iref.g.73"></span> <a href="#request-line" class="smpl">Request-Line</a> = <a href="#method" class="smpl">Method</a> <a href="#core.rules" class="smpl">SP</a> <a href="#request-target" class="smpl">request-target</a> <a href="#core.rules" class="smpl">SP</a> <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">CRLF</a>1324 <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.74"></span> <a href="#request-line" class="smpl">Request-Line</a> = <a href="#method" class="smpl">Method</a> <a href="#core.rules" class="smpl">SP</a> <a href="#request-target" class="smpl">request-target</a> <a href="#core.rules" class="smpl">SP</a> <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">CRLF</a> 1300 1325 </pre><h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a> <a id="method" href="#method">Method</a></h3> 1301 1326 <p id="rfc.section.5.1.1.p.1">The Method token indicates the method to be performed on the resource identified by the request-target. The method is case-sensitive.</p> 1302 <div id="rfc.figure.u.3 5"></div><pre class="inline"><span id="rfc.iref.g.74"></span><span id="rfc.iref.g.75"></span> <a href="#method" class="smpl">Method</a> = <a href="#rule.token.separators" class="smpl">token</a>1327 <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span> <a href="#method" class="smpl">Method</a> = <a href="#rule.token.separators" class="smpl">token</a> 1303 1328 </pre><h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a> <a id="request-target" href="#request-target">request-target</a></h3> 1304 <p id="rfc.section.5.1.2.p.1">The request-target is a Uniform Resource Identifier (<a href="#uri" title="Uniform Resource Identifiers">Section 2.1</a>) and identifies the resource upon which to apply the request. 1305 </p> 1306 <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.76"></span> <a href="#request-target" class="smpl">request-target</a> = "*" 1329 <p id="rfc.section.5.1.2.p.1">The request-target identifies the resource upon which to apply the request.</p> 1330 <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.77"></span> <a href="#request-target" class="smpl">request-target</a> = "*" 1307 1331 / <a href="#uri" class="smpl">absolute-URI</a> 1308 1332 / ( <a href="#uri" class="smpl">path-absolute</a> [ "?" <a href="#uri" class="smpl">query</a> ] ) … … 1312 1336 apply to a resource. One example would be 1313 1337 </p> 1314 <div id="rfc.figure.u.3 7"></div><pre class="text"> OPTIONS * HTTP/1.11338 <div id="rfc.figure.u.38"></div><pre class="text"> OPTIONS * HTTP/1.1 1315 1339 </pre><p id="rfc.section.5.1.2.p.5">The absolute-URI form is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to forward the request or service it from a valid cache, 1316 1340 and return the response. Note that the proxy <em class="bcp14">MAY</em> forward the request on to another proxy or directly to the server specified by the absolute-URI. In order to avoid request … … 1318 1342 Request-Line would be: 1319 1343 </p> 1320 <div id="rfc.figure.u.3 8"></div><pre class="text"> GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.11344 <div id="rfc.figure.u.39"></div><pre class="text"> GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1 1321 1345 </pre><p id="rfc.section.5.1.2.p.7">To allow for transition to absolute-URIs in all requests in future versions of HTTP, all HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absolute-URI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies. 1322 1346 </p> … … 1327 1351 server would create a TCP connection to port 80 of the host "www.example.org" and send the lines: 1328 1352 </p> 1329 <div id="rfc.figure.u. 39"></div><pre class="text"> GET /pub/WWW/TheProject.html HTTP/1.11353 <div id="rfc.figure.u.40"></div><pre class="text"> GET /pub/WWW/TheProject.html HTTP/1.1 1330 1354 Host: www.example.org 1331 1355 </pre><p id="rfc.section.5.1.2.p.11">followed by the remainder of the Request. Note that the absolute path cannot be empty; if none is present in the original … … 1335 1359 asterisk form of request-target, then the last proxy on the request chain <em class="bcp14">MUST</em> forward the request with "*" as the final request-target. 1336 1360 </p> 1337 <div id="rfc.figure.u.4 0"></div>1361 <div id="rfc.figure.u.41"></div> 1338 1362 <p>For example, the request</p><pre class="text"> OPTIONS http://www.example.org:8001 HTTP/1.1 1339 </pre><div id="rfc.figure.u.4 1"></div>1363 </pre><div id="rfc.figure.u.42"></div> 1340 1364 <p>would be forwarded by the proxy as</p><pre class="text"> OPTIONS * HTTP/1.1 1341 1365 Host: www.example.org:8001 1342 1366 </pre> <p>after connecting to port 8001 of host "www.example.org".</p> 1343 <p id="rfc.section.5.1.2.p.15">The request-target is transmitted in the format specified in <a href="#http.uri" title="http URI scheme">Section 2.1.1</a>. If the request-target is encoded using the "% <a href="#core.rules" class="smpl">HEXDIG</a> <a href="#core.rules" class="smpl">HEXDIG</a>" encoding (<a href="#RFC3986" id="rfc.xref.RFC3986.17"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.4">Section 2.4</a>), the origin server <em class="bcp14">MUST</em> decode the request-target in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid request-targets with an appropriate status code.1367 <p id="rfc.section.5.1.2.p.15">The request-target is transmitted in the format specified in <a href="#http.uri" title="http URI scheme">Section 2.1.1</a>. If the request-target is percent-encoded (<a href="#RFC3986" id="rfc.xref.RFC3986.17"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>), the origin server <em class="bcp14">MUST</em> decode the request-target in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid request-targets with an appropriate status code. 1344 1368 </p> 1345 1369 <p id="rfc.section.5.1.2.p.16">A transparent proxy <em class="bcp14">MUST NOT</em> rewrite the "path-absolute" part of the received request-target when forwarding it to the next inbound server, except as noted … … 1353 1377 </dd> 1354 1378 </dl> 1355 <p id="rfc.section.5.1.2.p.18">HTTP does not place a pre-defined limit on the length of a request-target. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the 414 ( Request-target too Long) status if the received1356 request-targetwould be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 Request-target Too Long">Section 8.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).1379 <p id="rfc.section.5.1.2.p.18">HTTP does not place a pre-defined limit on the length of a request-target. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the 414 (URI Too Long) status if the received request-target 1380 would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 Request-target Too Long">Section 8.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). 1357 1381 </p> 1358 1382 <p id="rfc.section.5.1.2.p.19">Various ad-hoc limitations on request-target length are found in practice. It is <em class="bcp14">RECOMMENDED</em> that all HTTP senders and recipients support request-target lengths of 8000 or more OCTETs. … … 1381 1405 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="response" href="#response">Response</a></h1> 1382 1406 <p id="rfc.section.6.p.1">After receiving and interpreting a request message, a server responds with an HTTP response message.</p> 1383 <div id="rfc.figure.u.4 2"></div><pre class="inline"><span id="rfc.iref.g.77"></span> <a href="#response" class="smpl">Response</a> = <a href="#status-line" class="smpl">Status-Line</a> ; <a href="#status-line" title="Status-Line">Section 6.1</a>1407 <div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.78"></span> <a href="#response" class="smpl">Response</a> = <a href="#status-line" class="smpl">Status-Line</a> ; <a href="#status-line" title="Status-Line">Section 6.1</a> 1384 1408 *(( <a href="#general.header.fields" class="smpl">general-header</a> ; <a href="#general.header.fields" title="General Header Fields">Section 4.5</a> 1385 1409 / <a href="#abnf.dependencies" class="smpl">response-header</a> ; <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a> … … 1392 1416 CRLF sequence. 1393 1417 </p> 1394 <div id="rfc.figure.u.4 3"></div><pre class="inline"><span id="rfc.iref.g.78"></span> <a href="#status-line" class="smpl">Status-Line</a> = <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> <a href="#core.rules" class="smpl">CRLF</a>1418 <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.79"></span> <a href="#status-line" class="smpl">Status-Line</a> = <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> <a href="#core.rules" class="smpl">CRLF</a> 1395 1419 </pre><h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a> <a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h3> 1396 1420 <p id="rfc.section.6.1.1.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. These codes … … 1409 1433 <li>5xx: Server Error - The server failed to fulfill an apparently valid request</li> 1410 1434 </ul> 1411 <div id="rfc.figure.u.4 4"></div><pre class="inline"><span id="rfc.iref.g.79"></span><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> = 3<a href="#core.rules" class="smpl">DIGIT</a>1435 <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> = 3<a href="#core.rules" class="smpl">DIGIT</a> 1412 1436 <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> = *( <a href="#core.rules" class="smpl">WSP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> ) 1413 1437 </pre><h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="connections" href="#connections">Connections</a></h1> … … 1601 1625 </p> 1602 1626 <p id="rfc.section.8.1.p.2">The Connection header's value has the following grammar:</p> 1603 <div id="rfc.figure.u.4 5"></div><pre class="inline"><span id="rfc.iref.g.82"></span><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span> <a href="#header.connection" class="smpl">Connection</a> = "Connection" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.connection" class="smpl">Connection-v</a>1627 <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span><span id="rfc.iref.g.85"></span> <a href="#header.connection" class="smpl">Connection</a> = "Connection" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.connection" class="smpl">Connection-v</a> 1604 1628 <a href="#header.connection" class="smpl">Connection-v</a> = 1#<a href="#header.connection" class="smpl">connection-token</a> 1605 1629 <a href="#header.connection" class="smpl">connection-token</a> = <a href="#rule.token.separators" class="smpl">token</a> … … 1614 1638 of the response. For example, 1615 1639 </p> 1616 <div id="rfc.figure.u.4 6"></div><pre class="text"> Connection: close1640 <div id="rfc.figure.u.47"></div><pre class="text"> Connection: close 1617 1641 </pre><p id="rfc.section.8.1.p.8">in either the request or the response header fields indicates that the connection <em class="bcp14">SHOULD NOT</em> be considered `persistent' (<a href="#persistent.connections" title="Persistent Connections">Section 7.1</a>) after the current request/response is complete. 1618 1642 </p> … … 1630 1654 or, in the case of the HEAD method, the size of the entity-body that would have been sent had the request been a GET. 1631 1655 </p> 1632 <div id="rfc.figure.u.4 7"></div><pre class="inline"><span id="rfc.iref.g.85"></span><span id="rfc.iref.g.86"></span> <a href="#header.content-length" class="smpl">Content-Length</a> = "Content-Length" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1*<a href="#header.content-length" class="smpl">Content-Length-v</a>1656 <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.86"></span><span id="rfc.iref.g.87"></span> <a href="#header.content-length" class="smpl">Content-Length</a> = "Content-Length" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1*<a href="#header.content-length" class="smpl">Content-Length-v</a> 1633 1657 <a href="#header.content-length" class="smpl">Content-Length-v</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a> 1634 1658 </pre><p id="rfc.section.8.2.p.3">An example is</p> 1635 <div id="rfc.figure.u.4 8"></div><pre class="text"> Content-Length: 34951659 <div id="rfc.figure.u.49"></div><pre class="text"> Content-Length: 3495 1636 1660 </pre><p id="rfc.section.8.2.p.5">Applications <em class="bcp14">SHOULD</em> use this field to indicate the transfer-length of the message-body, unless this is prohibited by the rules in <a href="#message.length" title="Message Length">Section 4.4</a>. 1637 1661 </p> … … 1648 1672 as orig-date in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as described in <a href="#full.date" title="Full Date">Section 3.2.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format. 1649 1673 </p> 1650 <div id="rfc.figure.u. 49"></div><pre class="inline"><span id="rfc.iref.g.87"></span><span id="rfc.iref.g.88"></span> <a href="#header.date" class="smpl">Date</a> = "Date" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.date" class="smpl">Date-v</a>1674 <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span> <a href="#header.date" class="smpl">Date</a> = "Date" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.date" class="smpl">Date-v</a> 1651 1675 <a href="#header.date" class="smpl">Date-v</a> = <a href="#full.date" class="smpl">HTTP-date</a> 1652 1676 </pre><p id="rfc.section.8.3.p.3">An example is</p> 1653 <div id="rfc.figure.u.5 0"></div><pre class="text"> Date: Tue, 15 Nov 1994 08:12:31 GMT1677 <div id="rfc.figure.u.51"></div><pre class="text"> Date: Tue, 15 Nov 1994 08:12:31 GMT 1654 1678 </pre><p id="rfc.section.8.3.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases: 1655 1679 </p> … … 1687 1711 a single IP address. 1688 1712 </p> 1689 <div id="rfc.figure.u.5 1"></div><pre class="inline"><span id="rfc.iref.g.89"></span><span id="rfc.iref.g.90"></span> <a href="#header.host" class="smpl">Host</a> = "Host" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.host" class="smpl">Host-v</a>1713 <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span> <a href="#header.host" class="smpl">Host</a> = "Host" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.host" class="smpl">Host-v</a> 1690 1714 <a href="#header.host" class="smpl">Host-v</a> = <a href="#uri" class="smpl">uri-host</a> [ ":" <a href="#uri" class="smpl">port</a> ] ; <a href="#http.uri" title="http URI scheme">Section 2.1.1</a> 1691 1715 </pre><p id="rfc.section.8.4.p.3">A "host" without any trailing port information implies the default port for the service requested (e.g., "80" for an HTTP 1692 1716 URL). For example, a request on the origin server for <http://www.example.org/pub/WWW/> would properly include: 1693 1717 </p> 1694 <div id="rfc.figure.u.5 2"></div><pre class="text"> GET /pub/WWW/ HTTP/1.11718 <div id="rfc.figure.u.53"></div><pre class="text"> GET /pub/WWW/ HTTP/1.1 1695 1719 Host: www.example.org 1696 1720 </pre><p id="rfc.section.8.4.p.5">A client <em class="bcp14">MUST</em> include a Host header field in all HTTP/1.1 request messages. If the requested URI does not include an Internet host name … … 1707 1731 and/or a comma-separated list of extension transfer-coding names with optional accept parameters (as described in <a href="#transfer.codings" title="Transfer Codings">Section 3.3</a>). 1708 1732 </p> 1709 <div id="rfc.figure.u.5 3"></div><pre class="inline"><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span> <a href="#header.te" class="smpl">TE</a> = "TE" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.te" class="smpl">TE-v</a>1733 <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span><span id="rfc.iref.g.94"></span><span id="rfc.iref.g.95"></span><span id="rfc.iref.g.96"></span> <a href="#header.te" class="smpl">TE</a> = "TE" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.te" class="smpl">TE-v</a> 1710 1734 <a href="#header.te" class="smpl">TE-v</a> = #<a href="#header.te" class="smpl">t-codings</a> 1711 <a href="#header.te" class="smpl">t-codings</a> = "trailers" / ( <a href="#transfer.codings" class="smpl">transfer-extension</a> [ <a href="#abnf.dependencies" class="smpl">accept-params</a> ] ) 1735 <a href="#header.te" class="smpl">t-codings</a> = "trailers" / ( <a href="#transfer.codings" class="smpl">transfer-extension</a> [ <a href="#header.te" class="smpl">te-params</a> ] ) 1736 <a href="#header.te" class="smpl">te-params</a> = <a href="#rule.whitespace" class="smpl">OWS</a> ";" <a href="#rule.whitespace" class="smpl">OWS</a> "q=" <a href="#quality.values" class="smpl">qvalue</a> *( <a href="#header.te" class="smpl">te-ext</a> ) 1737 <a href="#header.te" class="smpl">te-ext</a> = <a href="#rule.whitespace" class="smpl">OWS</a> ";" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#rule.token.separators" class="smpl">token</a> [ "=" ( <a href="#rule.token.separators" class="smpl">token</a> / <a href="#rule.quoted-string" class="smpl">quoted-string</a> ) ] 1712 1738 </pre><p id="rfc.section.8.5.p.3">The presence of the keyword "trailers" indicates that the client is willing to accept trailer fields in a chunked transfer-coding, 1713 1739 as defined in <a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section 3.3.1</a>. This keyword is reserved for use with transfer-coding values even though it does not itself represent a transfer-coding. 1714 1740 </p> 1715 1741 <p id="rfc.section.8.5.p.4">Examples of its use are:</p> 1716 <div id="rfc.figure.u.5 4"></div><pre class="text"> TE: deflate1742 <div id="rfc.figure.u.55"></div><pre class="text"> TE: deflate 1717 1743 TE: 1718 1744 TE: trailers, deflate;q=0.5 … … 1733 1759 <li> 1734 1760 <p>If the transfer-coding being tested is one of the transfer-codings listed in the TE field, then it is acceptable unless it 1735 is accompanied by a qvalue of 0. (As defined in <a href=" p3-payload.html#quality.values" title="Quality Values">Section 2.4</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, a qvalue of 0 means "not acceptable.")1761 is accompanied by a qvalue of 0. (As defined in <a href="#quality.values" title="Quality Values">Section 3.5</a>, a qvalue of 0 means "not acceptable.") 1736 1762 </p> 1737 1763 </li> … … 1751 1777 chunked transfer-coding. 1752 1778 </p> 1753 <div id="rfc.figure.u.5 5"></div><pre class="inline"><span id="rfc.iref.g.94"></span><span id="rfc.iref.g.95"></span> <a href="#header.trailer" class="smpl">Trailer</a> = "Trailer" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.trailer" class="smpl">Trailer-v</a>1779 <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.97"></span><span id="rfc.iref.g.98"></span> <a href="#header.trailer" class="smpl">Trailer</a> = "Trailer" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.trailer" class="smpl">Trailer-v</a> 1754 1780 <a href="#header.trailer" class="smpl">Trailer-v</a> = 1#<a href="#message.headers" class="smpl">field-name</a> 1755 1781 </pre><p id="rfc.section.8.6.p.3">An HTTP/1.1 message <em class="bcp14">SHOULD</em> include a Trailer header field in a message using chunked transfer-coding with a non-empty trailer. Doing so allows the recipient … … 1772 1798 transfer-coding is a property of the message, not of the entity. 1773 1799 </p> 1774 <div id="rfc.figure.u.5 6"></div><pre class="inline"><span id="rfc.iref.g.96"></span><span id="rfc.iref.g.97"></span> <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> = "Transfer-Encoding" ":" <a href="#rule.whitespace" class="smpl">OWS</a>1800 <div id="rfc.figure.u.57"></div><pre class="inline"><span id="rfc.iref.g.99"></span><span id="rfc.iref.g.100"></span> <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> = "Transfer-Encoding" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1775 1801 <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a> 1776 1802 <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a> = 1#<a href="#transfer.codings" class="smpl">transfer-coding</a> 1777 1803 </pre><p id="rfc.section.8.7.p.3">Transfer-codings are defined in <a href="#transfer.codings" title="Transfer Codings">Section 3.3</a>. An example is: 1778 1804 </p> 1779 <div id="rfc.figure.u.5 7"></div><pre class="text"> Transfer-Encoding: chunked1805 <div id="rfc.figure.u.58"></div><pre class="text"> Transfer-Encoding: chunked 1780 1806 </pre><p id="rfc.section.8.7.p.5">If multiple encodings have been applied to an entity, the transfer-codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other entity-header fields not defined by this specification. 1781 1807 </p> … … 1787 1813 to use if the server finds it appropriate to switch protocols. The server <em class="bcp14">MUST</em> use the Upgrade header field within a 101 (Switching Protocols) response to indicate which protocol(s) are being switched. 1788 1814 </p> 1789 <div id="rfc.figure.u.5 8"></div><pre class="inline"><span id="rfc.iref.g.98"></span><span id="rfc.iref.g.99"></span> <a href="#header.upgrade" class="smpl">Upgrade</a> = "Upgrade" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.upgrade" class="smpl">Upgrade-v</a>1815 <div id="rfc.figure.u.59"></div><pre class="inline"><span id="rfc.iref.g.101"></span><span id="rfc.iref.g.102"></span> <a href="#header.upgrade" class="smpl">Upgrade</a> = "Upgrade" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.upgrade" class="smpl">Upgrade-v</a> 1790 1816 <a href="#header.upgrade" class="smpl">Upgrade-v</a> = 1#<a href="#product.tokens" class="smpl">product</a> 1791 1817 </pre><p id="rfc.section.8.8.p.3">For example,</p> 1792 <div id="rfc.figure.u. 59"></div><pre class="text"> Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x111818 <div id="rfc.figure.u.60"></div><pre class="text"> Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11 1793 1819 </pre><p id="rfc.section.8.8.p.5">The Upgrade header field is intended to provide a simple mechanism for transition from HTTP/1.1 to some other, incompatible 1794 1820 protocol. It does so by allowing the client to advertise its desire to use another protocol, such as a later version of HTTP … … 1819 1845 of all senders along the request/response chain. 1820 1846 </p> 1821 <div id="rfc.figure.u.6 0"></div><pre class="inline"><span id="rfc.iref.g.100"></span><span id="rfc.iref.g.101"></span><span id="rfc.iref.g.102"></span><span id="rfc.iref.g.103"></span><span id="rfc.iref.g.104"></span><span id="rfc.iref.g.105"></span><span id="rfc.iref.g.106"></span> <a href="#header.via" class="smpl">Via</a> = "Via" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.via" class="smpl">Via-v</a>1847 <div id="rfc.figure.u.61"></div><pre class="inline"><span id="rfc.iref.g.103"></span><span id="rfc.iref.g.104"></span><span id="rfc.iref.g.105"></span><span id="rfc.iref.g.106"></span><span id="rfc.iref.g.107"></span><span id="rfc.iref.g.108"></span><span id="rfc.iref.g.109"></span> <a href="#header.via" class="smpl">Via</a> = "Via" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.via" class="smpl">Via-v</a> 1822 1848 <a href="#header.via" class="smpl">Via-v</a> = 1#( <a href="#header.via" class="smpl">received-protocol</a> <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#header.via" class="smpl">received-by</a> 1823 1849 [ <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#rule.comment" class="smpl">comment</a> ] ) … … 1844 1870 server at www.example.com. The request received by www.example.com would then have the following Via header field: 1845 1871 </p> 1846 <div id="rfc.figure.u.6 1"></div><pre class="text"> Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)1872 <div id="rfc.figure.u.62"></div><pre class="text"> Via: 1.0 fred, 1.1 p.example.net (Apache/1.1) 1847 1873 </pre><p id="rfc.section.8.9.p.9">Proxies and gateways used as a portal through a network firewall <em class="bcp14">SHOULD NOT</em>, by default, forward the names and ports of hosts within the firewall region. This information <em class="bcp14">SHOULD</em> only be propagated if explicitly enabled. If not enabled, the received-by host of any host behind the firewall <em class="bcp14">SHOULD</em> be replaced by an appropriate pseudonym for that host. 1848 1874 </p> … … 1850 1876 For example, 1851 1877 </p> 1852 <div id="rfc.figure.u.6 2"></div><pre class="text"> Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy1878 <div id="rfc.figure.u.63"></div><pre class="text"> Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy 1853 1879 </pre><p id="rfc.section.8.9.p.12">could be collapsed to</p> 1854 <div id="rfc.figure.u.6 3"></div><pre class="text"> Via: 1.0 ricky, 1.1 mertz, 1.0 lucy1880 <div id="rfc.figure.u.64"></div><pre class="text"> Via: 1.0 ricky, 1.1 mertz, 1.0 lucy 1855 1881 </pre><p id="rfc.section.8.9.p.14">Applications <em class="bcp14">SHOULD NOT</em> combine multiple entries unless they are all under the same organizational control and the hosts have already been replaced 1856 1882 by pseudonyms. Applications <em class="bcp14">MUST NOT</em> combine entries which have different received-protocol values. … … 1904 1930 <td>http</td> 1905 1931 <td>standard</td> 1906 <td> <a href="#header.te" id="rfc.xref.header.te. 3" title="TE">Section 8.5</a>1932 <td> <a href="#header.te" id="rfc.xref.header.te.4" title="TE">Section 8.5</a> 1907 1933 </td> 1908 1934 </tr> … … 2156 2182 <h2 id="rfc.references.1"><a href="#rfc.section.12.1" id="rfc.section.12.1">12.1</a> Normative References 2157 2183 </h2> 2158 <table summary="Normative References"> 2184 <table summary="Normative References"> 2159 2185 <tr> 2160 2186 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> … … 2163 2189 <tr> 2164 2190 <td class="reference"><b id="Part2">[Part2]</b></td> 2165 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), February 2009.2191 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), March 2009. 2166 2192 </td> 2167 2193 </tr> 2168 2194 <tr> 2169 2195 <td class="reference"><b id="Part3">[Part3]</b></td> 2170 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), February 2009.2196 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), March 2009. 2171 2197 </td> 2172 2198 </tr> 2173 2199 <tr> 2174 2200 <td class="reference"><b id="Part5">[Part5]</b></td> 2175 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), February 2009.2201 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), March 2009. 2176 2202 </td> 2177 2203 </tr> 2178 2204 <tr> 2179 2205 <td class="reference"><b id="Part6">[Part6]</b></td> 2180 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), February 2009. 2181 </td> 2182 </tr> 2183 <tr> 2184 <td class="reference"><b id="RFC2045">[RFC2045]</b></td> 2185 <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N.S. 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. 2206 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), March 2009. 2186 2207 </td> 2187 2208 </tr> … … 2208 2229 <h2 id="rfc.references.2"><a href="#rfc.section.12.2" id="rfc.section.12.2">12.2</a> Informative References 2209 2230 </h2> 2210 <table summary="Informative References"> 2231 <table summary="Informative References"> 2211 2232 <tr> 2212 2233 <td class="reference"><b id="Kri2001">[Kri2001]</b></td> … … 2248 2269 <td class="reference"><b id="RFC1945">[RFC1945]</b></td> 2249 2270 <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC 1945, May 1996. 2271 </td> 2272 </tr> 2273 <tr> 2274 <td class="reference"><b id="RFC2045">[RFC2045]</b></td> 2275 <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N.S. 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. 2250 2276 </td> 2251 2277 </tr> … … 2357 2383 </p> 2358 2384 <p id="rfc.section.A.p.4">The character set of an entity-body <em class="bcp14">SHOULD</em> be labeled as the lowest common denominator of the character codes used within that body, with the exception that not labeling 2359 the entity is preferred over labeling the entity with the labels US-ASCII or ISO-8859-1. See <a href="#Part3" id="rfc.xref.Part3.1 1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.2385 the entity is preferred over labeling the entity with the labels US-ASCII or ISO-8859-1. See <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 2360 2386 </p> 2361 2387 <p id="rfc.section.A.p.5">Additional rules for requirements on parsing and encoding of dates and other potential problems with date encodings include:</p> … … 2449 2475 <p id="rfc.section.B.3.p.2">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow 2450 2476 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 2451 computed. (Sections <a href="#transfer.codings" title="Transfer Codings">3.3</a>, <a href="#message.length" title="Message Length">4.4</a>, <a href="#header.content-length" id="rfc.xref.header.content-length.3" title="Content-Length">8.2</a>, see also <a href="#Part3" id="rfc.xref.Part3.1 2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)2477 computed. (Sections <a href="#transfer.codings" title="Transfer Codings">3.3</a>, <a href="#message.length" title="Message Length">4.4</a>, <a href="#header.content-length" id="rfc.xref.header.content-length.3" title="Content-Length">8.2</a>, see also <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) 2452 2478 </p> 2453 2479 <p id="rfc.section.B.3.p.3">The use and interpretation of HTTP version numbers has been clarified by <a href="#RFC2145" id="rfc.xref.RFC2145.3"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a>. Require proxies to upgrade requests to highest protocol version they support to deal with problems discovered in HTTP/1.0 2454 2480 implementations (<a href="#http.version" title="HTTP Version">Section 3.1</a>) 2455 2481 </p> 2456 <p id="rfc.section.B.3.p.4">Transfer-coding had significant problems, particularly with interactions with chunked encoding. The solution is that transfer-codings 2482 <p id="rfc.section.B.3.p.4">Quality Values of zero should indicate that "I don't want something" to allow clients to refuse a representation. (<a href="#quality.values" title="Quality Values">Section 3.5</a>) 2483 </p> 2484 <p id="rfc.section.B.3.p.5">Transfer-coding had significant problems, particularly with interactions with chunked encoding. The solution is that transfer-codings 2457 2485 become as full fledged as content-codings. This involves adding an IANA registry for transfer-codings (separate from content 2458 2486 codings), a new header field (TE) and enabling trailer headers in the future. Transfer encoding is a major performance benefit, 2459 2487 so it was worth fixing <a href="#Nie1997" id="rfc.xref.Nie1997.2"><cite title="Network Performance Effects of HTTP/1.1, CSS1, and PNG">[Nie1997]</cite></a>. TE also solves another, obscure, downward interoperability problem that could have occurred due to interactions between 2460 authentication trailers, chunked encoding and HTTP/1.0 clients.(Section <a href="#transfer.codings" title="Transfer Codings">3.3</a>, <a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">3.3.1</a>, and <a href="#header.te" id="rfc.xref.header.te. 4" title="TE">8.5</a>)2488 authentication trailers, chunked encoding and HTTP/1.0 clients.(Section <a href="#transfer.codings" title="Transfer Codings">3.3</a>, <a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">3.3.1</a>, and <a href="#header.te" id="rfc.xref.header.te.5" title="TE">8.5</a>) 2461 2489 </p> 2462 2490 <h2 id="rfc.section.B.4"><a href="#rfc.section.B.4">B.4</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> … … 2511 2539 </p> 2512 2540 <dl class="empty"> 2513 <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.1 3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses).2541 <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses). 2514 2542 </dd> 2515 2543 </dl> … … 2518 2546 <dl class="empty"> 2519 2547 <dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of 2520 entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 3</a> of <a href="#Part3" id="rfc.xref.Part3.1 4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.2548 entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 3</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 2521 2549 </dd> 2522 2550 </dl> 2523 <p id="rfc.section.C.p.8"> <span id="rfc.iref.g.1 07"></span> <dfn>gateway</dfn>2551 <p id="rfc.section.C.p.8"> <span id="rfc.iref.g.110"></span> <dfn>gateway</dfn> 2524 2552 </p> 2525 2553 <dl class="empty"> … … 2579 2607 </p> 2580 2608 <dl class="empty"> 2581 <dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.1 5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status.2609 <dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status. 2582 2610 </dd> 2583 2611 </dl> … … 2619 2647 </dl> 2620 2648 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 2621 <div id="rfc.figure.u.6 4"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS2649 <div id="rfc.figure.u.65"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS 2622 2650 2623 2651 <a href="#abnf.dependencies" class="smpl">Cache-Control</a> = <Cache-Control, defined in [Part6], Section 15.4> … … 2679 2707 2680 2708 <a href="#uri" class="smpl">absolute-URI</a> = <absolute-URI, defined in [RFC3986], Section 4.3> 2681 <a href="#abnf.dependencies" class="smpl">accept-params</a> = <accept-params, defined in [Part3], Section 5.1>2682 2709 <a href="#full.date" class="smpl">asctime-date</a> = wkday SP date3 SP time SP 4DIGIT 2683 2710 <a href="#rule.parameter" class="smpl">attribute</a> = token … … 2722 2749 <a href="#chunked.transfer.encoding" class="smpl">last-chunk</a> = 1*"0" *WSP [ chunk-ext ] CRLF 2723 2750 2724 <a href="#message.body" class="smpl">message-body</a> = entity-body / <entity-body encoded as per2725 Transfer-Encoding>2751 <a href="#message.body" class="smpl">message-body</a> = entity-body / 2752 <entity-body encoded as per Transfer-Encoding> 2726 2753 <a href="#message.headers" class="smpl">message-header</a> = field-name ":" OWS [ field-value ] OWS 2727 2754 <a href="#full.date" class="smpl">month</a> = s-Jan / s-Feb / s-Mar / s-Apr / s-May / s-Jun / s-Jul / s-Aug … … 2748 2775 <a href="#rule.quoted-string" class="smpl">quoted-string</a> = DQUOTE *( qdtext / quoted-pair ) DQUOTE 2749 2776 <a href="#rule.quoted-pair" class="smpl">quoted-text</a> = %x01-09 / %x0B-0C / %x0E-FF 2777 <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] ) 2750 2778 2751 2779 <a href="#header.via" class="smpl">received-by</a> = ( uri-host [ ":" port ] ) / pseudonym … … 2780 2808 <a href="#message.types" class="smpl">start-line</a> = Request-Line / Status-Line 2781 2809 2782 <a href="#header.te" class="smpl">t-codings</a> = "trailers" / ( transfer-extension [ accept-params ] )2810 <a href="#header.te" class="smpl">t-codings</a> = "trailers" / ( transfer-extension [ te-params ] ) 2783 2811 <a href="#rule.token.separators" class="smpl">tchar</a> = "!" / "#" / "$" / "%" / "&" / "'" / "*" / "+" / "-" / "." / 2784 2812 "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA 2813 <a href="#header.te" class="smpl">te-ext</a> = OWS ";" OWS token [ "=" ( token / quoted-string ) ] 2814 <a href="#header.te" class="smpl">te-params</a> = OWS ";" OWS "q=" qvalue *te-ext 2785 2815 <a href="#full.date" class="smpl">time</a> = 2DIGIT ":" 2DIGIT ":" 2DIGIT 2786 2816 <a href="#rule.token.separators" class="smpl">token</a> = 1*tchar … … 2796 2826 <a href="#full.date" class="smpl">wkday</a> = s-Mon / s-Tue / s-Wed / s-Thu / s-Fri / s-Sat / s-Sun 2797 2827 2798 ; Chunked-Body defined but not used 2828 2829 </pre> <div id="rfc.figure.u.66"></div> 2830 <p>ABNF diagnostics:</p><pre class="inline">; Chunked-Body defined but not used 2799 2831 ; Content-Length defined but not used 2800 2832 ; HTTP-message defined but not used … … 2807 2839 ; http-URI defined but not used 2808 2840 ; partial-URI defined but not used 2809 2810 2811 </pre> <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 2841 </pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 2812 2842 <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a> Since RFC2616 2813 2843 </h2> … … 2981 3011 <ul> 2982 3012 <li>Rewrite introduction; add mostly new Architecture Section.</li> 3013 <li>Move definition of quality values from Part 3 into Part 1; make TE request header grammar independent of accept-params (defined 3014 in Part 3). 3015 </li> 2983 3016 </ul> 2984 3017 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> … … 3011 3044 </li> 3012 3045 <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind"> 3013 <li class="indline1">gateway <a class="iref" href="#rfc.iref.g.1 07">C</a></li>3046 <li class="indline1">gateway <a class="iref" href="#rfc.iref.g.110">C</a></li> 3014 3047 <li class="indline1"><tt>Grammar</tt> 3015 3048 <ul class="ind"> … … 3027 3060 <li class="indline1"><tt>chunk-size</tt> <a class="iref" href="#rfc.iref.g.52"><b>3.3.1</b></a></li> 3028 3061 <li class="indline1"><tt>Chunked-Body</tt> <a class="iref" href="#rfc.iref.g.50"><b>3.3.1</b></a></li> 3029 <li class="indline1"><tt>comment</tt> <a class="iref" href="#rfc.iref.g.6 8"><b>4.2</b></a></li>3030 <li class="indline1"><tt>Connection</tt> <a class="iref" href="#rfc.iref.g.8 2"><b>8.1</b></a></li>3031 <li class="indline1"><tt>connection-token</tt> <a class="iref" href="#rfc.iref.g.8 4"><b>8.1</b></a></li>3032 <li class="indline1"><tt>Connection-v</tt> <a class="iref" href="#rfc.iref.g.8 3"><b>8.1</b></a></li>3033 <li class="indline1"><tt>Content-Length</tt> <a class="iref" href="#rfc.iref.g.8 5"><b>8.2</b></a></li>3034 <li class="indline1"><tt>Content-Length-v</tt> <a class="iref" href="#rfc.iref.g.8 6"><b>8.2</b></a></li>3062 <li class="indline1"><tt>comment</tt> <a class="iref" href="#rfc.iref.g.69"><b>4.2</b></a></li> 3063 <li class="indline1"><tt>Connection</tt> <a class="iref" href="#rfc.iref.g.83"><b>8.1</b></a></li> 3064 <li class="indline1"><tt>connection-token</tt> <a class="iref" href="#rfc.iref.g.85"><b>8.1</b></a></li> 3065 <li class="indline1"><tt>Connection-v</tt> <a class="iref" href="#rfc.iref.g.84"><b>8.1</b></a></li> 3066 <li class="indline1"><tt>Content-Length</tt> <a class="iref" href="#rfc.iref.g.86"><b>8.2</b></a></li> 3067 <li class="indline1"><tt>Content-Length-v</tt> <a class="iref" href="#rfc.iref.g.87"><b>8.2</b></a></li> 3035 3068 <li class="indline1">CR <a class="iref" href="#rfc.iref.g.2"><b>1.2</b></a></li> 3036 3069 <li class="indline1">CRLF <a class="iref" href="#rfc.iref.g.3"><b>1.2</b></a></li> 3037 <li class="indline1"><tt>ctext</tt> <a class="iref" href="#rfc.iref.g. 69"><b>4.2</b></a></li>3070 <li class="indline1"><tt>ctext</tt> <a class="iref" href="#rfc.iref.g.70"><b>4.2</b></a></li> 3038 3071 <li class="indline1">CTL <a class="iref" href="#rfc.iref.g.4"><b>1.2</b></a></li> 3039 <li class="indline1"><tt>Date</tt> <a class="iref" href="#rfc.iref.g.8 7"><b>8.3</b></a></li>3040 <li class="indline1"><tt>Date-v</tt> <a class="iref" href="#rfc.iref.g.8 8"><b>8.3</b></a></li>3072 <li class="indline1"><tt>Date</tt> <a class="iref" href="#rfc.iref.g.88"><b>8.3</b></a></li> 3073 <li class="indline1"><tt>Date-v</tt> <a class="iref" href="#rfc.iref.g.89"><b>8.3</b></a></li> 3041 3074 <li class="indline1"><tt>date1</tt> <a class="iref" href="#rfc.iref.g.38"><b>3.2.1</b></a></li> 3042 3075 <li class="indline1"><tt>date2</tt> <a class="iref" href="#rfc.iref.g.39"><b>3.2.1</b></a></li> … … 3044 3077 <li class="indline1">DIGIT <a class="iref" href="#rfc.iref.g.5"><b>1.2</b></a></li> 3045 3078 <li class="indline1">DQUOTE <a class="iref" href="#rfc.iref.g.6"><b>1.2</b></a></li> 3046 <li class="indline1"><tt>extension-code</tt> <a class="iref" href="#rfc.iref.g.8 0"><b>6.1.1</b></a></li>3047 <li class="indline1"><tt>extension-method</tt> <a class="iref" href="#rfc.iref.g.7 5"><b>5.1.1</b></a></li>3048 <li class="indline1"><tt>field-content</tt> <a class="iref" href="#rfc.iref.g.6 7"><b>4.2</b></a></li>3049 <li class="indline1"><tt>field-name</tt> <a class="iref" href="#rfc.iref.g.6 5"><b>4.2</b></a></li>3050 <li class="indline1"><tt>field-value</tt> <a class="iref" href="#rfc.iref.g.6 6"><b>4.2</b></a></li>3051 <li class="indline1"><tt>general-header</tt> <a class="iref" href="#rfc.iref.g.7 1"><b>4.5</b></a></li>3052 <li class="indline1"><tt>generic-message</tt> <a class="iref" href="#rfc.iref.g.6 2"><b>4.1</b></a></li>3079 <li class="indline1"><tt>extension-code</tt> <a class="iref" href="#rfc.iref.g.81"><b>6.1.1</b></a></li> 3080 <li class="indline1"><tt>extension-method</tt> <a class="iref" href="#rfc.iref.g.76"><b>5.1.1</b></a></li> 3081 <li class="indline1"><tt>field-content</tt> <a class="iref" href="#rfc.iref.g.68"><b>4.2</b></a></li> 3082 <li class="indline1"><tt>field-name</tt> <a class="iref" href="#rfc.iref.g.66"><b>4.2</b></a></li> 3083 <li class="indline1"><tt>field-value</tt> <a class="iref" href="#rfc.iref.g.67"><b>4.2</b></a></li> 3084 <li class="indline1"><tt>general-header</tt> <a class="iref" href="#rfc.iref.g.72"><b>4.5</b></a></li> 3085 <li class="indline1"><tt>generic-message</tt> <a class="iref" href="#rfc.iref.g.63"><b>4.1</b></a></li> 3053 3086 <li class="indline1">HEXDIG <a class="iref" href="#rfc.iref.g.7"><b>1.2</b></a></li> 3054 <li class="indline1"><tt>Host</tt> <a class="iref" href="#rfc.iref.g. 89"><b>8.4</b></a></li>3055 <li class="indline1"><tt>Host-v</tt> <a class="iref" href="#rfc.iref.g.9 0"><b>8.4</b></a></li>3087 <li class="indline1"><tt>Host</tt> <a class="iref" href="#rfc.iref.g.90"><b>8.4</b></a></li> 3088 <li class="indline1"><tt>Host-v</tt> <a class="iref" href="#rfc.iref.g.91"><b>8.4</b></a></li> 3056 3089 <li class="indline1"><tt>HTTP-date</tt> <a class="iref" href="#rfc.iref.g.33"><b>3.2.1</b></a></li> 3057 <li class="indline1"><tt>HTTP-message</tt> <a class="iref" href="#rfc.iref.g.6 1"><b>4.1</b></a></li>3090 <li class="indline1"><tt>HTTP-message</tt> <a class="iref" href="#rfc.iref.g.62"><b>4.1</b></a></li> 3058 3091 <li class="indline1"><tt>HTTP-Prot-Name</tt> <a class="iref" href="#rfc.iref.g.32"><b>3.1</b></a></li> 3059 3092 <li class="indline1"><tt>http-URI</tt> <a class="iref" href="#rfc.iref.g.30"><b>2.1.1</b></a></li> … … 3061 3094 <li class="indline1"><tt>last-chunk</tt> <a class="iref" href="#rfc.iref.g.53"><b>3.3.1</b></a></li> 3062 3095 <li class="indline1">LF <a class="iref" href="#rfc.iref.g.8"><b>1.2</b></a></li> 3063 <li class="indline1"><tt>message-body</tt> <a class="iref" href="#rfc.iref.g.7 0"><b>4.3</b></a></li>3064 <li class="indline1"><tt>message-header</tt> <a class="iref" href="#rfc.iref.g.6 4"><b>4.2</b></a></li>3065 <li class="indline1"><tt>Method</tt> <a class="iref" href="#rfc.iref.g.7 4"><b>5.1.1</b></a></li>3096 <li class="indline1"><tt>message-body</tt> <a class="iref" href="#rfc.iref.g.71"><b>4.3</b></a></li> 3097 <li class="indline1"><tt>message-header</tt> <a class="iref" href="#rfc.iref.g.65"><b>4.2</b></a></li> 3098 <li class="indline1"><tt>Method</tt> <a class="iref" href="#rfc.iref.g.75"><b>5.1.1</b></a></li> 3066 3099 <li class="indline1"><tt>month</tt> <a class="iref" href="#rfc.iref.g.44"><b>3.2.1</b></a></li> 3067 3100 <li class="indline1"><tt>obs-text</tt> <a class="iref" href="#rfc.iref.g.20"><b>1.2.2</b></a></li> … … 3074 3107 <li class="indline1"><tt>product</tt> <a class="iref" href="#rfc.iref.g.59"><b>3.4</b></a></li> 3075 3108 <li class="indline1"><tt>product-version</tt> <a class="iref" href="#rfc.iref.g.60"><b>3.4</b></a></li> 3076 <li class="indline1"><tt>protocol-name</tt> <a class="iref" href="#rfc.iref.g.10 3"><b>8.9</b></a></li>3077 <li class="indline1"><tt>protocol-version</tt> <a class="iref" href="#rfc.iref.g.10 4"><b>8.9</b></a></li>3078 <li class="indline1"><tt>pseudonym</tt> <a class="iref" href="#rfc.iref.g.10 6"><b>8.9</b></a></li>3109 <li class="indline1"><tt>protocol-name</tt> <a class="iref" href="#rfc.iref.g.106"><b>8.9</b></a></li> 3110 <li class="indline1"><tt>protocol-version</tt> <a class="iref" href="#rfc.iref.g.107"><b>8.9</b></a></li> 3111 <li class="indline1"><tt>pseudonym</tt> <a class="iref" href="#rfc.iref.g.109"><b>8.9</b></a></li> 3079 3112 <li class="indline1"><tt>qdtext</tt> <a class="iref" href="#rfc.iref.g.19"><b>1.2.2</b></a></li> 3080 3113 <li class="indline1"><tt>query</tt> <a class="iref" href="#rfc.iref.g.28"><b>2.1</b></a></li> … … 3082 3115 <li class="indline1"><tt>quoted-string</tt> <a class="iref" href="#rfc.iref.g.18"><b>1.2.2</b></a></li> 3083 3116 <li class="indline1"><tt>quoted-text</tt> <a class="iref" href="#rfc.iref.g.21"><b>1.2.2</b></a></li> 3084 <li class="indline1"><tt>Reason-Phrase</tt> <a class="iref" href="#rfc.iref.g.81"><b>6.1.1</b></a></li> 3085 <li class="indline1"><tt>received-by</tt> <a class="iref" href="#rfc.iref.g.105"><b>8.9</b></a></li> 3086 <li class="indline1"><tt>received-protocol</tt> <a class="iref" href="#rfc.iref.g.102"><b>8.9</b></a></li> 3087 <li class="indline1"><tt>Request</tt> <a class="iref" href="#rfc.iref.g.72"><b>5</b></a></li> 3088 <li class="indline1"><tt>Request-Line</tt> <a class="iref" href="#rfc.iref.g.73"><b>5.1</b></a></li> 3089 <li class="indline1"><tt>request-target</tt> <a class="iref" href="#rfc.iref.g.76"><b>5.1.2</b></a></li> 3090 <li class="indline1"><tt>Response</tt> <a class="iref" href="#rfc.iref.g.77"><b>6</b></a></li> 3117 <li class="indline1"><tt>qvalue</tt> <a class="iref" href="#rfc.iref.g.61"><b>3.5</b></a></li> 3118 <li class="indline1"><tt>Reason-Phrase</tt> <a class="iref" href="#rfc.iref.g.82"><b>6.1.1</b></a></li> 3119 <li class="indline1"><tt>received-by</tt> <a class="iref" href="#rfc.iref.g.108"><b>8.9</b></a></li> 3120 <li class="indline1"><tt>received-protocol</tt> <a class="iref" href="#rfc.iref.g.105"><b>8.9</b></a></li> 3121 <li class="indline1"><tt>Request</tt> <a class="iref" href="#rfc.iref.g.73"><b>5</b></a></li> 3122 <li class="indline1"><tt>Request-Line</tt> <a class="iref" href="#rfc.iref.g.74"><b>5.1</b></a></li> 3123 <li class="indline1"><tt>request-target</tt> <a class="iref" href="#rfc.iref.g.77"><b>5.1.2</b></a></li> 3124 <li class="indline1"><tt>Response</tt> <a class="iref" href="#rfc.iref.g.78"><b>6</b></a></li> 3091 3125 <li class="indline1"><tt>rfc1123-date</tt> <a class="iref" href="#rfc.iref.g.34"><b>3.2.1</b></a></li> 3092 3126 <li class="indline1"><tt>rfc850-date</tt> <a class="iref" href="#rfc.iref.g.36"><b>3.2.1</b></a></li> 3093 3127 <li class="indline1"><tt>RWS</tt> <a class="iref" href="#rfc.iref.g.14"><b>1.2.2</b></a></li> 3094 3128 <li class="indline1">SP <a class="iref" href="#rfc.iref.g.10"><b>1.2</b></a></li> 3095 <li class="indline1"><tt>start-line</tt> <a class="iref" href="#rfc.iref.g.6 3"><b>4.1</b></a></li>3096 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g. 79"><b>6.1.1</b></a></li>3097 <li class="indline1"><tt>Status-Line</tt> <a class="iref" href="#rfc.iref.g.7 8"><b>6.1</b></a></li>3098 <li class="indline1"><tt>t-codings</tt> <a class="iref" href="#rfc.iref.g.9 3"><b>8.5</b></a></li>3129 <li class="indline1"><tt>start-line</tt> <a class="iref" href="#rfc.iref.g.64"><b>4.1</b></a></li> 3130 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g.80"><b>6.1.1</b></a></li> 3131 <li class="indline1"><tt>Status-Line</tt> <a class="iref" href="#rfc.iref.g.79"><b>6.1</b></a></li> 3132 <li class="indline1"><tt>t-codings</tt> <a class="iref" href="#rfc.iref.g.94"><b>8.5</b></a></li> 3099 3133 <li class="indline1"><tt>tchar</tt> <a class="iref" href="#rfc.iref.g.17"><b>1.2.2</b></a></li> 3100 <li class="indline1"><tt>TE</tt> <a class="iref" href="#rfc.iref.g.91"><b>8.5</b></a></li> 3101 <li class="indline1"><tt>TE-v</tt> <a class="iref" href="#rfc.iref.g.92"><b>8.5</b></a></li> 3134 <li class="indline1"><tt>TE</tt> <a class="iref" href="#rfc.iref.g.92"><b>8.5</b></a></li> 3135 <li class="indline1"><tt>te-ext</tt> <a class="iref" href="#rfc.iref.g.96"><b>8.5</b></a></li> 3136 <li class="indline1"><tt>te-params</tt> <a class="iref" href="#rfc.iref.g.95"><b>8.5</b></a></li> 3137 <li class="indline1"><tt>TE-v</tt> <a class="iref" href="#rfc.iref.g.93"><b>8.5</b></a></li> 3102 3138 <li class="indline1"><tt>time</tt> <a class="iref" href="#rfc.iref.g.41"><b>3.2.1</b></a></li> 3103 3139 <li class="indline1"><tt>token</tt> <a class="iref" href="#rfc.iref.g.16"><b>1.2.2</b></a></li> 3104 <li class="indline1"><tt>Trailer</tt> <a class="iref" href="#rfc.iref.g.9 4"><b>8.6</b></a></li>3140 <li class="indline1"><tt>Trailer</tt> <a class="iref" href="#rfc.iref.g.97"><b>8.6</b></a></li> 3105 3141 <li class="indline1"><tt>trailer-part</tt> <a class="iref" href="#rfc.iref.g.58"><b>3.3.1</b></a></li> 3106 <li class="indline1"><tt>Trailer-v</tt> <a class="iref" href="#rfc.iref.g.9 5"><b>8.6</b></a></li>3142 <li class="indline1"><tt>Trailer-v</tt> <a class="iref" href="#rfc.iref.g.98"><b>8.6</b></a></li> 3107 3143 <li class="indline1"><tt>transfer-coding</tt> <a class="iref" href="#rfc.iref.g.45"><b>3.3</b></a></li> 3108 <li class="indline1"><tt>Transfer-Encoding</tt> <a class="iref" href="#rfc.iref.g.9 6"><b>8.7</b></a></li>3109 <li class="indline1"><tt>Transfer-Encoding-v</tt> <a class="iref" href="#rfc.iref.g. 97"><b>8.7</b></a></li>3144 <li class="indline1"><tt>Transfer-Encoding</tt> <a class="iref" href="#rfc.iref.g.99"><b>8.7</b></a></li> 3145 <li class="indline1"><tt>Transfer-Encoding-v</tt> <a class="iref" href="#rfc.iref.g.100"><b>8.7</b></a></li> 3110 3146 <li class="indline1"><tt>transfer-extension</tt> <a class="iref" href="#rfc.iref.g.46"><b>3.3</b></a></li> 3111 <li class="indline1"><tt>Upgrade</tt> <a class="iref" href="#rfc.iref.g. 98"><b>8.8</b></a></li>3112 <li class="indline1"><tt>Upgrade-v</tt> <a class="iref" href="#rfc.iref.g. 99"><b>8.8</b></a></li>3147 <li class="indline1"><tt>Upgrade</tt> <a class="iref" href="#rfc.iref.g.101"><b>8.8</b></a></li> 3148 <li class="indline1"><tt>Upgrade-v</tt> <a class="iref" href="#rfc.iref.g.102"><b>8.8</b></a></li> 3113 3149 <li class="indline1"><tt>uri-host</tt> <a class="iref" href="#rfc.iref.g.29"><b>2.1</b></a></li> 3114 3150 <li class="indline1"><tt>URI-reference</tt> <a class="iref" href="#rfc.iref.g.23"><b>2.1</b></a></li> 3115 3151 <li class="indline1"><tt>value</tt> <a class="iref" href="#rfc.iref.g.49"><b>3.3</b></a></li> 3116 3152 <li class="indline1">VCHAR <a class="iref" href="#rfc.iref.g.11"><b>1.2</b></a></li> 3117 <li class="indline1"><tt>Via</tt> <a class="iref" href="#rfc.iref.g.10 0"><b>8.9</b></a></li>3118 <li class="indline1"><tt>Via-v</tt> <a class="iref" href="#rfc.iref.g.10 1"><b>8.9</b></a></li>3153 <li class="indline1"><tt>Via</tt> <a class="iref" href="#rfc.iref.g.103"><b>8.9</b></a></li> 3154 <li class="indline1"><tt>Via-v</tt> <a class="iref" href="#rfc.iref.g.104"><b>8.9</b></a></li> 3119 3155 <li class="indline1"><tt>weekday</tt> <a class="iref" href="#rfc.iref.g.43"><b>3.2.1</b></a></li> 3120 3156 <li class="indline1"><tt>wkday</tt> <a class="iref" href="#rfc.iref.g.42"><b>3.2.1</b></a></li> … … 3131 3167 <li class="indline1">Date <a class="iref" href="#rfc.xref.header.date.1">4.5</a>, <a class="iref" href="#rfc.iref.h.5"><b>8.3</b></a>, <a class="iref" href="#rfc.xref.header.date.2">9.1</a></li> 3132 3168 <li class="indline1">Host <a class="iref" href="#rfc.iref.h.7"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.header.host.1">9.1</a>, <a class="iref" href="#rfc.xref.header.host.2">B.1.1</a></li> 3133 <li class="indline1">TE <a class="iref" href="#rfc.xref.header.te.1">3.3</a>, <a class="iref" href="#rfc.xref.header.te.2">3.3.1</a>, <a class="iref" href="#rfc. iref.h.8"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.3">9.1</a>, <a class="iref" href="#rfc.xref.header.te.4">B.3</a></li>3169 <li class="indline1">TE <a class="iref" href="#rfc.xref.header.te.1">3.3</a>, <a class="iref" href="#rfc.xref.header.te.2">3.3.1</a>, <a class="iref" href="#rfc.xref.header.te.3">3.5</a>, <a class="iref" href="#rfc.iref.h.8"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.4">9.1</a>, <a class="iref" href="#rfc.xref.header.te.5">B.3</a></li> 3134 3170 <li class="indline1">Trailer <a class="iref" href="#rfc.xref.header.trailer.1">3.3.1</a>, <a class="iref" href="#rfc.xref.header.trailer.2">4.5</a>, <a class="iref" href="#rfc.iref.h.9"><b>8.6</b></a>, <a class="iref" href="#rfc.xref.header.trailer.3">9.1</a></li> 3135 3171 <li class="indline1">Transfer-Encoding <a class="iref" href="#rfc.xref.header.transfer-encoding.1">3.3</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.2">4.3</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.3">4.4</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.4">4.5</a>, <a class="iref" href="#rfc.iref.h.10"><b>8.7</b></a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.5">9.1</a></li> … … 3140 3176 <li class="indline1">Host header <a class="iref" href="#rfc.iref.h.6"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.header.host.1">9.1</a>, <a class="iref" href="#rfc.xref.header.host.2">B.1.1</a></li> 3141 3177 <li class="indline1">http URI scheme <a class="iref" href="#rfc.iref.h.1"><b>2.1.1</b></a></li> 3142 <li class="indline1">https URI scheme <a class="iref" href="#rfc.iref.h.2">2.1. 1</a></li>3178 <li class="indline1">https URI scheme <a class="iref" href="#rfc.iref.h.2">2.1.2</a></li> 3143 3179 </ul> 3144 3180 </li> … … 3187 3223 </ul> 3188 3224 </li> 3189 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5"> 1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.6">3.3</a>, <a class="iref" href="#rfc.xref.Part3.7">3.3</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a>, <a class="iref" href="#rfc.xref.Part3.10">8.5</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.11">A</a>, <a class="iref" href="#rfc.xref.Part3.12">B.3</a>, <a class="iref" href="#rfc.xref.Part3.13">C</a>, <a class="iref" href="#rfc.xref.Part3.14">C</a>, <a class="iref" href="#rfc.xref.Part3.15">C</a><ul class="ind">3190 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part3. 6">3.3</a>, <a class="iref" href="#rfc.xref.Part3.7">3.3</a></li>3225 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">3.3</a>, <a class="iref" href="#rfc.xref.Part3.6">3.3</a>, <a class="iref" href="#rfc.xref.Part3.7">3.5</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.10">A</a>, <a class="iref" href="#rfc.xref.Part3.11">B.3</a>, <a class="iref" href="#rfc.xref.Part3.12">C</a>, <a class="iref" href="#rfc.xref.Part3.13">C</a>, <a class="iref" href="#rfc.xref.Part3.14">C</a><ul class="ind"> 3226 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part3.5">3.3</a>, <a class="iref" href="#rfc.xref.Part3.6">3.3</a></li> 3191 3227 <li class="indline1"><em>Section 2.3</em> <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a></li> 3192 <li class="indline1"><em>Section 2.4</em> <a class="iref" href="#rfc.xref.Part3.10">8.5</a></li> 3193 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part3.5">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a></li> 3194 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part3.14">C</a></li> 3195 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a></li> 3196 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.13">C</a>, <a class="iref" href="#rfc.xref.Part3.15">C</a></li> 3197 <li class="indline1"><em>Section 5.1</em> <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li> 3228 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a></li> 3229 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part3.13">C</a></li> 3230 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li> 3231 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.7">3.5</a>, <a class="iref" href="#rfc.xref.Part3.12">C</a>, <a class="iref" href="#rfc.xref.Part3.14">C</a></li> 3198 3232 <li class="indline1"><em>Appendix A</em> <a class="iref" href="#rfc.xref.Part3.1">1</a></li> 3199 3233 </ul> … … 3220 3254 <li class="indline1"><em>RFC1900</em> <a class="iref" href="#rfc.xref.RFC1900.1">2.1.1</a>, <a class="iref" href="#rfc.xref.RFC1900.2">10.4</a>, <a class="iref" href="#RFC1900"><b>12.2</b></a></li> 3221 3255 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li> 3222 <li class="indline1"><em>RFC2045</em> <a class="iref" href="#rfc.xref.RFC2045.1">1</a>, <a class="iref" href="#rfc.xref.RFC2045.2">3.3</a>, <a class="iref" href="#rfc.xref.RFC2045.3">11</a>, <a class="iref" href="#RFC2045"><b>12. 1</b></a></li>3256 <li class="indline1"><em>RFC2045</em> <a class="iref" href="#rfc.xref.RFC2045.1">1</a>, <a class="iref" href="#rfc.xref.RFC2045.2">3.3</a>, <a class="iref" href="#rfc.xref.RFC2045.3">11</a>, <a class="iref" href="#RFC2045"><b>12.2</b></a></li> 3223 3257 <li class="indline1"><em>RFC2047</em> <a class="iref" href="#rfc.xref.RFC2047.1">4.2</a>, <a class="iref" href="#RFC2047"><b>12.2</b></a></li> 3224 3258 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2068.2">7.1.1</a>, <a class="iref" href="#rfc.xref.RFC2068.3">7.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.4">7.2.3</a>, <a class="iref" href="#rfc.xref.RFC2068.5">11</a>, <a class="iref" href="#RFC2068"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.6">B</a>, <a class="iref" href="#rfc.xref.RFC2068.7">B.2</a><ul class="ind"> … … 3230 3264 <li class="indline1"><em>RFC2145</em> <a class="iref" href="#rfc.xref.RFC2145.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2145.2">3.1</a>, <a class="iref" href="#RFC2145"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2145.3">B.3</a></li> 3231 3265 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">11</a>, <a class="iref" href="#RFC2616"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3">E.1</a></li> 3232 <li class="indline1"><em>RFC2818</em> <a class="iref" href="#rfc.xref.RFC2818.1">2.1. 1</a>, <a class="iref" href="#RFC2818"><b>12.2</b></a></li>3266 <li class="indline1"><em>RFC2818</em> <a class="iref" href="#rfc.xref.RFC2818.1">2.1.2</a>, <a class="iref" href="#RFC2818"><b>12.2</b></a></li> 3233 3267 <li class="indline1"><em>RFC2965</em> <a class="iref" href="#rfc.xref.RFC2965.1">4.2</a>, <a class="iref" href="#RFC2965"><b>12.2</b></a></li> 3234 3268 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">9.1</a>, <a class="iref" href="#RFC3864"><b>12.2</b></a></li> 3235 3269 <li class="indline1"><em>RFC3977</em> <a class="iref" href="#rfc.xref.RFC3977.1">1</a>, <a class="iref" href="#RFC3977"><b>12.2</b></a></li> 3236 <li class="indline1"><em>RFC3986</em> <a class="iref" href="#rfc.xref.RFC3986.1">1</a>, <a class="iref" href="#rfc.xref.RFC3986.2">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.3">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.4">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.5">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.6">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.7">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.8">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.9">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.10">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.11">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.12">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.13">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.14">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.15">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.16">2.1.2</a>, <a class="iref" href="#rfc.xref.RFC3986.17">5.1.2</a>, <a class="iref" href="#RFC3986"><b>12.1</b></a><ul class="ind"> 3237 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.RFC3986.16">2.1.2</a></li> 3238 <li class="indline1"><em>Section 2.4</em> <a class="iref" href="#rfc.xref.RFC3986.17">5.1.2</a></li> 3270 <li class="indline1"><em>RFC3986</em> <a class="iref" href="#rfc.xref.RFC3986.1">1</a>, <a class="iref" href="#rfc.xref.RFC3986.2">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.3">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.4">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.5">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.6">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.7">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.8">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.9">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.10">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.11">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.12">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.13">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.14">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.15">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.16">2.1.3</a>, <a class="iref" href="#rfc.xref.RFC3986.17">5.1.2</a>, <a class="iref" href="#RFC3986"><b>12.1</b></a><ul class="ind"> 3271 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.RFC3986.16">2.1.3</a>, <a class="iref" href="#rfc.xref.RFC3986.17">5.1.2</a></li> 3239 3272 <li class="indline1"><em>Section 3.2.3</em> <a class="iref" href="#rfc.xref.RFC3986.13">2.1</a></li> 3240 3273 <li class="indline1"><em>Section 3.2.2</em> <a class="iref" href="#rfc.xref.RFC3986.15">2.1</a></li> … … 3270 3303 </li> 3271 3304 <li class="indline0"><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul class="ind"> 3272 <li class="indline1">TE header <a class="iref" href="#rfc.xref.header.te.1">3.3</a>, <a class="iref" href="#rfc.xref.header.te.2">3.3.1</a>, <a class="iref" href="#rfc. iref.t.1"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.3">9.1</a>, <a class="iref" href="#rfc.xref.header.te.4">B.3</a></li>3305 <li class="indline1">TE header <a class="iref" href="#rfc.xref.header.te.1">3.3</a>, <a class="iref" href="#rfc.xref.header.te.2">3.3.1</a>, <a class="iref" href="#rfc.xref.header.te.3">3.5</a>, <a class="iref" href="#rfc.iref.t.1"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.4">9.1</a>, <a class="iref" href="#rfc.xref.header.te.5">B.3</a></li> 3273 3306 <li class="indline1"><em>Tou1998</em> <a class="iref" href="#rfc.xref.Tou1998.1">7.1.1</a>, <a class="iref" href="#Tou1998"><b>12.2</b></a></li> 3274 3307 <li class="indline1">Trailer header <a class="iref" href="#rfc.xref.header.trailer.1">3.3.1</a>, <a class="iref" href="#rfc.xref.header.trailer.2">4.5</a>, <a class="iref" href="#rfc.iref.t.2"><b>8.6</b></a>, <a class="iref" href="#rfc.xref.header.trailer.3">9.1</a></li> … … 3283 3316 <ul class="ind"> 3284 3317 <li class="indline1">http <a class="iref" href="#rfc.iref.u.1"><b>2.1.1</b></a></li> 3285 <li class="indline1">https <a class="iref" href="#rfc.iref.u.2">2.1. 1</a></li>3318 <li class="indline1">https <a class="iref" href="#rfc.iref.u.2">2.1.2</a></li> 3286 3319 </ul> 3287 3320 </li> -
draft-ietf-httpbis/latest-roy/p1-messaging.xml
r446 r461 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " February">15 <!ENTITY ID-MONTH "March"> 16 16 <!ENTITY ID-YEAR "2009"> 17 17 <!ENTITY caching "<xref target='Part6' x:rel='#caching' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 25 25 <!ENTITY entity-body "<xref target='Part3' x:rel='#entity.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 26 26 <!ENTITY entity-header-fields "<xref target='Part3' x:rel='#entity.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 27 <!ENTITY header-accept "<xref target='Part3' x:rel='#header.accept' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">28 27 <!ENTITY header-cache-control "<xref target='Part6' x:rel='#header.cache-control' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 29 28 <!ENTITY header-expect "<xref target='Part2' x:rel='#header.expect' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 31 30 <!ENTITY header-warning "<xref target='Part6' x:rel='#header.warning' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 32 31 <!ENTITY idempotent-methods "<xref target='Part2' x:rel='#idempotent.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 33 <!ENTITY qvalue "<xref target='Part3' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">34 32 <!ENTITY request-header-fields "<xref target='Part2' x:rel='#request.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 35 33 <!ENTITY response-header-fields "<xref target='Part2' x:rel='#response.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 201 199 <t> 202 200 The Hypertext Transfer Protocol (HTTP) is an application-level 203 protocol for distributed, collaborative, hyper mediainformation201 protocol for distributed, collaborative, hypertext information 204 202 systems. HTTP has been in use by the World Wide Web global information 205 203 initiative since 1990. This document is Part 1 of the seven-part specification … … 258 256 Gopher <xref target="RFC1436"/>, and WAIS <xref target="WAIS"/>. 259 257 HTTP proxies and gateways provide access to alternative information 260 services by translating their diverse protocols into a hyper media258 services by translating their diverse protocols into a hypertext 261 259 format that can be viewed and manipulated by clients in the same way 262 260 as HTTP services. 263 261 </t> 264 262 <t> 265 One consequence of HTTP flexibility is that we cannot define the protocol266 in terms of how to implement itbehind the interface. Instead, we are267 limited to restricting the syntax of communication, definingthe intent263 One consequence of HTTP flexibility is that the protocol cannot be defined 264 in terms of what occurs behind the interface. Instead, we are 265 limited to defining the syntax of communication, the intent 268 266 of received communication, and the expected behavior of recipients. If 269 267 the communication is considered in isolation, then successful actions … … 371 369 </t> 372 370 <figure><artwork type="example"> 373 #element => [ ( "," / element ) *( OWS "," [ OWS element ] ) ]374 375 1#element => *( "," OWS ) element *( OWS "," [ OWS element ] )371 #element => [ ( "," / element ) *( OWS "," [ OWS element ] ) ] 372 373 1#element => *( "," OWS ) element *( OWS "," [ OWS element ] ) 376 374 </artwork></figure> 377 375 <t> … … 474 472 <x:anchor-alias value="request-header"/> 475 473 <x:anchor-alias value="response-header"/> 476 <x:anchor-alias value="accept-params"/>477 474 <x:anchor-alias value="entity-body"/> 478 475 <x:anchor-alias value="entity-header"/> … … 488 485 </artwork></figure> 489 486 <figure><!-- Part3--><artwork type="abnf2616"> 490 <x:ref>accept-params</x:ref> = <accept-params, defined in &header-accept;>491 487 <x:ref>entity-body</x:ref> = <entity-body, defined in &entity-body;> 492 488 <x:ref>entity-header</x:ref> = <entity-header, defined in &entity-header-fields;> … … 568 564 <t> 569 565 The "http" scheme is used to locate network resources via the HTTP 570 protocol. This section defines the syntax and semantics for identifiers 571 using the http or https URI schemes. 566 protocol. 572 567 </t> 573 568 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="http-URI"/> … … 587 582 name. 588 583 </t> 584 </section> 585 586 <section title="https URI scheme" anchor="https.uri"> 587 <iref item="https URI scheme"/> 588 <iref item="URI scheme" subitem="https"/> 589 <t> 590 <cref>TBD: Define and explain purpose of https scheme.</cref> 591 </t> 589 592 <t><list><t> 590 <iref item="https URI scheme"/>591 <iref item="URI scheme" subitem="https"/>592 593 <x:h>Note:</x:h> the "https" scheme is defined in <xref target="RFC2818"/>. 593 594 </t></list></t> … … 604 605 <t>Comparisons of host names &MUST; be case-insensitive;</t> 605 606 <t>Comparisons of scheme names &MUST; be case-insensitive;</t> 606 <t>An empty path-absolute is equivalent to an path-absolute of "/".</t> 607 </list> 608 </t> 609 <t> 610 Characters other than those in the "reserved" set (see 611 <xref target="RFC3986" x:fmt="," x:sec="2.2"/>) are equivalent to their 612 ""%" <x:ref>HEXDIG</x:ref> <x:ref>HEXDIG</x:ref>" encoding. 607 <t>An empty path-absolute is equivalent to a path-absolute of "/".</t> 608 <t>Characters other than those in the "reserved" set are equivalent to their 609 percent-encoded octets (see <xref target="RFC3986" x:fmt="," x:sec="2.1"/>). 610 </t> 611 </list> 613 612 </t> 614 613 <t> … … 854 853 </t> 855 854 <figure><artwork type="example"> 856 857 858 855 Sun, 06 Nov 1994 08:49:37 GMT ; RFC 1123 856 Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format 857 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format 859 858 </artwork></figure> 860 859 <t> … … 1131 1130 </t> 1132 1131 <figure><artwork type="example"> 1133 1134 1132 User-Agent: CERN-LineMode/2.15 libwww/2.17b3 1133 Server: Apache/0.8.4 1135 1134 </artwork></figure> 1136 1135 <t> … … 1142 1141 the product value). 1143 1142 </t> 1143 </section> 1144 1145 <section title="Quality Values" anchor="quality.values"> 1146 <x:anchor-alias value="qvalue"/> 1147 <t> 1148 Both transfer codings (TE request header, <xref target="header.te"/>) 1149 and content negotiation (&content.negotiation;) use short "floating point" 1150 numbers to indicate the relative importance ("weight") of various 1151 negotiable parameters. A weight is normalized to a real number in 1152 the range 0 through 1, where 0 is the minimum and 1 the maximum 1153 value. If a parameter has a quality value of 0, then content with 1154 this parameter is `not acceptable' for the client. HTTP/1.1 1155 applications &MUST-NOT; generate more than three digits after the 1156 decimal point. User configuration of these values &SHOULD; also be 1157 limited in this fashion. 1158 </t> 1159 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="qvalue"/> 1160 <x:ref>qvalue</x:ref> = ( "0" [ "." 0*3<x:ref>DIGIT</x:ref> ] ) 1161 / ( "1" [ "." 0*3("0") ] ) 1162 </artwork></figure> 1163 <x:note> 1164 <t> 1165 <x:h>Note:</x:h> "Quality values" is a misnomer, since these values merely represent 1166 relative degradation in desired quality. 1167 </t> 1168 </x:note> 1144 1169 </section> 1145 1170 … … 1500 1525 <x:anchor-alias value="request-target"/> 1501 1526 <t> 1502 The request-target is a Uniform Resource Identifier (<xref target="uri"/>) and1527 The request-target 1503 1528 identifies the resource upon which to apply the request. 1504 1529 </t> … … 1583 1608 <t> 1584 1609 The request-target is transmitted in the format specified in 1585 <xref target="http.uri"/>. If the request-target is encoded using the 1586 "% <x:ref>HEXDIG</x:ref> <x:ref>HEXDIG</x:ref>" encoding 1587 (<xref target="RFC3986" x:fmt="," x:sec="2.4"/>), the origin server 1610 <xref target="http.uri"/>. If the request-target is percent-encoded 1611 (<xref target="RFC3986" x:fmt="," x:sec="2.1"/>), the origin server 1588 1612 &MUST; decode the request-target in order to 1589 1613 properly interpret the request. Servers &SHOULD; respond to invalid … … 1607 1631 HTTP does not place a pre-defined limit on the length of a request-target. 1608 1632 A server &MUST; be prepared to receive URIs of unbounded length and 1609 respond with the 414 ( Request-target too Long) status if the received1633 respond with the 414 (URI Too Long) status if the received 1610 1634 request-target would be longer than the server wishes to handle 1611 1635 (see &status-414;). … … 2379 2403 <x:anchor-alias value="TE-v"/> 2380 2404 <x:anchor-alias value="t-codings"/> 2405 <x:anchor-alias value="te-params"/> 2406 <x:anchor-alias value="te-ext"/> 2381 2407 <t> 2382 2408 The request-header field "TE" indicates what extension transfer-codings … … 2387 2413 parameters (as described in <xref target="transfer.codings"/>). 2388 2414 </t> 2389 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="TE"/><iref primary="true" item="Grammar" subitem="TE-v"/><iref primary="true" item="Grammar" subitem="t-codings"/> 2415 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="TE"/><iref primary="true" item="Grammar" subitem="TE-v"/><iref primary="true" item="Grammar" subitem="t-codings"/><iref primary="true" item="Grammar" subitem="te-params"/><iref primary="true" item="Grammar" subitem="te-ext"/> 2390 2416 <x:ref>TE</x:ref> = "TE" ":" <x:ref>OWS</x:ref> <x:ref>TE-v</x:ref> 2391 2417 <x:ref>TE-v</x:ref> = #<x:ref>t-codings</x:ref> 2392 <x:ref>t-codings</x:ref> = "trailers" / ( <x:ref>transfer-extension</x:ref> [ <x:ref>accept-params</x:ref> ] ) 2418 <x:ref>t-codings</x:ref> = "trailers" / ( <x:ref>transfer-extension</x:ref> [ <x:ref>te-params</x:ref> ] ) 2419 <x:ref>te-params</x:ref> = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> *( <x:ref>te-ext</x:ref> ) 2420 <x:ref>te-ext</x:ref> = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>token</x:ref> [ "=" ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> ) ] 2393 2421 </artwork></figure> 2394 2422 <t> … … 2433 2461 <t>If the transfer-coding being tested is one of the transfer-codings 2434 2462 listed in the TE field, then it is acceptable unless it 2435 is accompanied by a qvalue of 0. (As defined in &qvalue;, a2463 is accompanied by a qvalue of 0. (As defined in <xref target="quality.values"/>, a 2436 2464 qvalue of 0 means "not acceptable.")</t> 2437 2465 </x:lt> … … 2446 2474 <t> 2447 2475 If the TE field-value is empty or if no TE field is present, the only 2448 transfer-coding 2476 transfer-coding is "chunked". A message with no transfer-coding is 2449 2477 always acceptable. 2450 2478 </t> … … 3355 3383 </reference> 3356 3384 3357 <reference anchor="RFC2045">3358 <front>3359 <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>3360 <author initials="N." surname="Freed" fullname="Ned Freed">3361 <organization>Innosoft International, Inc.</organization>3362 <address><email>ned@innosoft.com</email></address>3363 </author>3364 <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">3365 <organization>First Virtual Holdings</organization>3366 <address><email>nsb@nsb.fv.com</email></address>3367 </author>3368 <date month="November" year="1996"/>3369 </front>3370 <seriesInfo name="RFC" value="2045"/>3371 </reference>3372 3373 3385 <reference anchor="RFC2119"> 3374 3386 <front> … … 3574 3586 </reference> 3575 3587 3588 <reference anchor="RFC2045"> 3589 <front> 3590 <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title> 3591 <author initials="N." surname="Freed" fullname="Ned Freed"> 3592 <organization>Innosoft International, Inc.</organization> 3593 <address><email>ned@innosoft.com</email></address> 3594 </author> 3595 <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein"> 3596 <organization>First Virtual Holdings</organization> 3597 <address><email>nsb@nsb.fv.com</email></address> 3598 </author> 3599 <date month="November" year="1996"/> 3600 </front> 3601 <seriesInfo name="RFC" value="2045"/> 3602 </reference> 3603 3576 3604 <reference anchor="RFC2047"> 3577 3605 <front> … … 4092 4120 </t> 4093 4121 <t> 4122 Quality Values of zero should indicate that "I don't want something" 4123 to allow clients to refuse a representation. (<xref target="quality.values"/>) 4124 </t> 4125 <t> 4094 4126 Transfer-coding had significant problems, particularly with 4095 4127 interactions with chunked encoding. The solution is that transfer-codings … … 4462 4494 4463 4495 <x:ref>absolute-URI</x:ref> = <absolute-URI, defined in [RFC3986], Section 4.3> 4464 <x:ref>accept-params</x:ref> = <accept-params, defined in [Part3], Section 5.1>4465 4496 <x:ref>asctime-date</x:ref> = wkday SP date3 SP time SP 4DIGIT 4466 4497 <x:ref>attribute</x:ref> = token … … 4505 4536 <x:ref>last-chunk</x:ref> = 1*"0" *WSP [ chunk-ext ] CRLF 4506 4537 4507 <x:ref>message-body</x:ref> = entity-body / <entity-body encoded as per4508 Transfer-Encoding>4538 <x:ref>message-body</x:ref> = entity-body / 4539 <entity-body encoded as per Transfer-Encoding> 4509 4540 <x:ref>message-header</x:ref> = field-name ":" OWS [ field-value ] OWS 4510 4541 <x:ref>month</x:ref> = s-Jan / s-Feb / s-Mar / s-Apr / s-May / s-Jun / s-Jul / s-Aug … … 4531 4562 <x:ref>quoted-string</x:ref> = DQUOTE *( qdtext / quoted-pair ) DQUOTE 4532 4563 <x:ref>quoted-text</x:ref> = %x01-09 / %x0B-0C / %x0E-FF 4564 <x:ref>qvalue</x:ref> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] ) 4533 4565 4534 4566 <x:ref>received-by</x:ref> = ( uri-host [ ":" port ] ) / pseudonym … … 4563 4595 <x:ref>start-line</x:ref> = Request-Line / Status-Line 4564 4596 4565 <x:ref>t-codings</x:ref> = "trailers" / ( transfer-extension [ accept-params ] )4597 <x:ref>t-codings</x:ref> = "trailers" / ( transfer-extension [ te-params ] ) 4566 4598 <x:ref>tchar</x:ref> = "!" / "#" / "$" / "%" / "&" / "'" / "*" / "+" / "-" / "." / 4567 4599 "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA 4600 <x:ref>te-ext</x:ref> = OWS ";" OWS token [ "=" ( token / quoted-string ) ] 4601 <x:ref>te-params</x:ref> = OWS ";" OWS "q=" qvalue *te-ext 4568 4602 <x:ref>time</x:ref> = 2DIGIT ":" 2DIGIT ":" 2DIGIT 4569 4603 <x:ref>token</x:ref> = 1*tchar … … 4579 4613 <x:ref>wkday</x:ref> = s-Mon / s-Tue / s-Wed / s-Thu / s-Fri / s-Sat / s-Sun 4580 4614 4581 ; Chunked-Body defined but not used 4615 4616 </artwork> 4617 </figure> 4618 <figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">; Chunked-Body defined but not used 4582 4619 ; Content-Length defined but not used 4583 4620 ; HTTP-message defined but not used … … 4590 4627 ; http-URI defined but not used 4591 4628 ; partial-URI defined but not used 4592 4593 4594 </artwork> 4595 </figure> 4596 </section> 4629 </artwork></figure></section> 4597 4630 4598 4631 <section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log"> … … 4947 4980 Rewrite introduction; add mostly new Architecture Section. 4948 4981 </t> 4982 <t> 4983 Move definition of quality values from Part 3 into Part 1; 4984 make TE request header grammar independent of accept-params (defined in Part 3). 4985 </t> 4949 4986 </list> 4950 4987 </t> -
draft-ietf-httpbis/latest-roy/p2-semantics.html
r446 r461 146 146 border-width: 1px; 147 147 } 148 caption { 149 caption-side: bottom; 150 font-weight: bold; 151 font-size: 9pt; 152 margin-top: .5em; 153 } 154 148 155 table.header { 149 156 width: 95%; … … 317 324 } 318 325 @top-right { 319 content: " February2009";326 content: "March 2009"; 320 327 } 321 328 @top-center { … … 364 371 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 365 372 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 366 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 1, 2009-02-20 13:12:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">373 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.424, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 367 374 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 368 375 <meta name="DC.Creator" content="Fielding, R."> … … 376 383 <meta name="DC.Creator" content="Reschke, J. F."> 377 384 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 378 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-0 2">385 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-03"> 379 386 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 380 387 <meta name="DC.Description.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."> … … 412 419 </tr> 413 420 <tr> 414 <td class="header left">Expires: August2009</td>421 <td class="header left">Expires: September 2009</td> 415 422 <td class="header right">H. Frystyk</td> 416 423 </tr> … … 461 468 <tr> 462 469 <td class="header left"></td> 463 <td class="header right"> February 20, 2009</td>470 <td class="header right">March 2, 2009</td> 464 471 </tr> 465 472 </table> … … 485 492 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 486 493 </p> 487 <p>This Internet-Draft will expire in August2009.</p>494 <p>This Internet-Draft will expire in September 2009.</p> 488 495 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 489 496 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2095 2102 <tr> 2096 2103 <td class="reference"><b id="Part1">[Part1]</b></td> 2097 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), February 2009.2104 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), March 2009. 2098 2105 </td> 2099 2106 </tr> 2100 2107 <tr> 2101 2108 <td class="reference"><b id="Part3">[Part3]</b></td> 2102 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), February 2009.2109 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), March 2009. 2103 2110 </td> 2104 2111 </tr> 2105 2112 <tr> 2106 2113 <td class="reference"><b id="Part4">[Part4]</b></td> 2107 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), February 2009.2114 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), March 2009. 2108 2115 </td> 2109 2116 </tr> 2110 2117 <tr> 2111 2118 <td class="reference"><b id="Part5">[Part5]</b></td> 2112 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), February 2009.2119 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), March 2009. 2113 2120 </td> 2114 2121 </tr> 2115 2122 <tr> 2116 2123 <td class="reference"><b id="Part6">[Part6]</b></td> 2117 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), February 2009.2124 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), March 2009. 2118 2125 </td> 2119 2126 </tr> 2120 2127 <tr> 2121 2128 <td class="reference"><b id="Part7">[Part7]</b></td> 2122 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), February 2009.2129 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), March 2009. 2123 2130 </td> 2124 2131 </tr> … … 2260 2267 2261 2268 <a href="#abnf.dependencies" class="smpl">If-Match</a> = <If-Match, defined in [Part4], Section 6.2> 2262 <a href="#abnf.dependencies" class="smpl">If-Modified-Since</a> = <If-Modified-Since, defined in [Part4], Section 2263 6.3>2269 If-Modified-Since = 2270 <If-Modified-Since, defined in [Part4], Section 6.3> 2264 2271 <a href="#abnf.dependencies" class="smpl">If-None-Match</a> = <If-None-Match, defined in [Part4], Section 6.4> 2265 2272 <a href="#abnf.dependencies" class="smpl">If-Range</a> = <If-Range, defined in [Part5], Section 5.3> 2266 <a href="#abnf.dependencies" class="smpl">If-Unmodified-Since</a> = <If-Unmodified-Since, defined in [Part4], 2267 Section 6.5>2273 If-Unmodified-Since = 2274 <If-Unmodified-Since, defined in [Part4], Section 6.5> 2268 2275 2269 2276 <a href="#header.location" class="smpl">Location</a> = "Location:" OWS Location-v … … 2273 2280 <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*DIGIT 2274 2281 <a href="#method" class="smpl">Method</a> = %x4F.50.54.49.4F.4E.53 / %x47.45.54 / %x48.45.41.44 / 2275 %x50.4F.5 3.54 / %x50.55.54 / %x44.45.4C.45.54.45 / %x54.52.41.43.452276 / %x43.4F.4E.4E.45.43.54 / extension-method2282 %x50.4F.54 / %x50.55.54 / %x44.45.4C.45.54.45 / %x54.52.41.43.45 / 2283 %x43.4E.4E.45.43.54 / extension-method 2277 2284 2278 2285 <a href="#core.rules" class="smpl">OWS</a> = <OWS, defined in [Part1], Section 1.2.2> 2279 2286 2280 <a href="#abnf.dependencies" class="smpl">Proxy-Authenticate</a> = <Proxy-Authenticate, defined in [Part7], Section 2281 3.2>2282 <a href="#abnf.dependencies" class="smpl">Proxy-Authorization</a> = <Proxy-Authorization, defined in [Part7], 2283 Section 3.3>2287 Proxy-Authenticate = 2288 <Proxy-Authenticate, defined in [Part7], Section 3.2> 2289 Proxy-Authorization = 2290 <Proxy-Authorization, defined in [Part7], Section 3.3> 2284 2291 2285 2292 <a href="#core.rules" class="smpl">RWS</a> = <RWS, defined in [Part1], Section 1.2.2> … … 2307 2314 <a href="#abnf.dependencies" class="smpl">Vary</a> = <Vary, defined in [Part6], Section 15.5> 2308 2315 2309 <a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a> = <WWW-Authenticate, defined in [Part7], Section 2310 3.4>2316 WWW-Authenticate = 2317 <WWW-Authenticate, defined in [Part7], Section 3.4> 2311 2318 2312 2319 <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in [Part1], Section 2.1> … … 2344 2351 <a href="#core.rules" class="smpl">token</a> = <token, defined in [Part1], Section 1.2.2> 2345 2352 2346 ; Reason-Phrase defined but not used 2353 2354 </pre> <div id="rfc.figure.u.30"></div> 2355 <p>ABNF diagnostics:</p><pre class="inline">; Reason-Phrase defined but not used 2347 2356 ; Status-Code defined but not used 2348 2357 ; request-header defined but not used 2349 2358 ; response-header defined but not used 2350 2351 2352 </pre> <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 2359 </pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 2353 2360 <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> Since RFC2616 2354 2361 </h2> -
draft-ietf-httpbis/latest-roy/p2-semantics.xml
r446 r461 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " February">15 <!ENTITY ID-MONTH "March"> 16 16 <!ENTITY ID-YEAR "2009"> 17 17 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 3229 3229 3230 3230 <x:ref>If-Match</x:ref> = <If-Match, defined in [Part4], Section 6.2> 3231 <x:ref>If-Modified-Since</x:ref> = <If-Modified-Since, defined in [Part4], Section 3232 6.3>3231 If-Modified-Since = 3232 <If-Modified-Since, defined in [Part4], Section 6.3> 3233 3233 <x:ref>If-None-Match</x:ref> = <If-None-Match, defined in [Part4], Section 6.4> 3234 3234 <x:ref>If-Range</x:ref> = <If-Range, defined in [Part5], Section 5.3> 3235 <x:ref>If-Unmodified-Since</x:ref> = <If-Unmodified-Since, defined in [Part4], 3236 Section 6.5>3235 If-Unmodified-Since = 3236 <If-Unmodified-Since, defined in [Part4], Section 6.5> 3237 3237 3238 3238 <x:ref>Location</x:ref> = "Location:" OWS Location-v … … 3242 3242 <x:ref>Max-Forwards-v</x:ref> = 1*DIGIT 3243 3243 <x:ref>Method</x:ref> = %x4F.50.54.49.4F.4E.53 / %x47.45.54 / %x48.45.41.44 / 3244 %x50.4F.5 3.54 / %x50.55.54 / %x44.45.4C.45.54.45 / %x54.52.41.43.453245 / %x43.4F.4E.4E.45.43.54 / extension-method3244 %x50.4F.54 / %x50.55.54 / %x44.45.4C.45.54.45 / %x54.52.41.43.45 / 3245 %x43.4E.4E.45.43.54 / extension-method 3246 3246 3247 3247 <x:ref>OWS</x:ref> = <OWS, defined in [Part1], Section 1.2.2> 3248 3248 3249 <x:ref>Proxy-Authenticate</x:ref> = <Proxy-Authenticate, defined in [Part7], Section 3250 3.2>3251 <x:ref>Proxy-Authorization</x:ref> = <Proxy-Authorization, defined in [Part7], 3252 Section 3.3>3249 Proxy-Authenticate = 3250 <Proxy-Authenticate, defined in [Part7], Section 3.2> 3251 Proxy-Authorization = 3252 <Proxy-Authorization, defined in [Part7], Section 3.3> 3253 3253 3254 3254 <x:ref>RWS</x:ref> = <RWS, defined in [Part1], Section 1.2.2> … … 3276 3276 <x:ref>Vary</x:ref> = <Vary, defined in [Part6], Section 15.5> 3277 3277 3278 <x:ref>WWW-Authenticate</x:ref> = <WWW-Authenticate, defined in [Part7], Section 3279 3.4>3278 WWW-Authenticate = 3279 <WWW-Authenticate, defined in [Part7], Section 3.4> 3280 3280 3281 3281 <x:ref>absolute-URI</x:ref> = <absolute-URI, defined in [Part1], Section 2.1> … … 3313 3313 <x:ref>token</x:ref> = <token, defined in [Part1], Section 1.2.2> 3314 3314 3315 ; Reason-Phrase defined but not used 3315 3316 </artwork> 3317 </figure> 3318 <figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">; Reason-Phrase defined but not used 3316 3319 ; Status-Code defined but not used 3317 3320 ; request-header defined but not used 3318 3321 ; response-header defined but not used 3319 3320 3321 </artwork> 3322 </figure> 3323 </section> 3322 </artwork></figure></section> 3324 3323 3325 3324 <section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log"> -
draft-ietf-httpbis/latest-roy/p3-payload.html
r446 r461 153 153 border-width: 1px; 154 154 } 155 caption { 156 caption-side: bottom; 157 font-weight: bold; 158 font-size: 9pt; 159 margin-top: .5em; 160 } 161 155 162 table.header { 156 163 width: 95%; … … 327 334 } 328 335 @top-right { 329 content: " February2009";336 content: "March 2009"; 330 337 } 331 338 @top-center { … … 372 379 <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 373 380 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 374 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 1, 2009-02-20 13:12:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">381 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.424, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 375 382 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 376 383 <meta name="DC.Creator" content="Fielding, R."> … … 384 391 <meta name="DC.Creator" content="Reschke, J. F."> 385 392 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 386 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-0 2">393 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-03"> 387 394 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 388 395 <meta name="DC.Description.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."> … … 415 422 </tr> 416 423 <tr> 417 <td class="header left">Expires: August2009</td>424 <td class="header left">Expires: September 2009</td> 418 425 <td class="header right">HP</td> 419 426 </tr> … … 468 475 <tr> 469 476 <td class="header left"></td> 470 <td class="header right"> February 20, 2009</td>477 <td class="header right">March 2, 2009</td> 471 478 </tr> 472 479 </table> … … 492 499 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 493 500 </p> 494 <p>This Internet-Draft will expire in August2009.</p>501 <p>This Internet-Draft will expire in September 2009.</p> 495 502 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 496 503 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 533 540 </ul> 534 541 </li> 535 <li class="tocline1">2.4 <a href="#quality.values">Quality Values</a></li> 536 <li class="tocline1">2.5 <a href="#language.tags">Language Tags</a></li> 542 <li class="tocline1">2.4 <a href="#language.tags">Language Tags</a></li> 537 543 </ul> 538 544 </li> … … 646 652 <a href="#abnf.dependencies" class="smpl">message-header</a> = <message-header, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a>> 647 653 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.1</a>> 654 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 3.5</a>> 648 655 </pre><div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Last-Modified</a> = <Last-Modified, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a>> 649 656 </pre><div id="rfc.figure.u.4"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Content-Range</a> = <Content-Range, defined in <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a>> … … 795 802 </dd> 796 803 </dl> 797 <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a> <a id="quality.values" href="#quality.values">Quality Values</a></h2> 798 <p id="rfc.section.2.4.p.1">HTTP content negotiation (<a href="#content.negotiation" title="Content Negotiation">Section 4</a>) uses short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight 799 is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has 800 a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion. 801 </p> 802 <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.10"></span> <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." 0*3<a href="#notation" class="smpl">DIGIT</a> ] ) 803 / ( "1" [ "." 0*3("0") ] ) 804 </pre><p id="rfc.section.2.4.p.3">"Quality values" is a misnomer, since these values merely represent relative degradation in desired quality.</p> 805 <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a> <a id="language.tags" href="#language.tags">Language Tags</a></h2> 806 <p id="rfc.section.2.5.p.1">A language tag identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information 804 <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a> <a id="language.tags" href="#language.tags">Language Tags</a></h2> 805 <p id="rfc.section.2.4.p.1">A language tag identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information 807 806 to other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the Accept-Language and 808 807 Content-Language fields. 809 808 </p> 810 <p id="rfc.section.2. 5.p.2">The syntax and registry of HTTP language tags is the same as that defined by <a href="#RFC1766" id="rfc.xref.RFC1766.1"><cite title="Tags for the Identification of Languages">[RFC1766]</cite></a>. In summary, a language tag is composed of 1 or more parts: A primary language tag and a possibly empty series of subtags:811 </p> 812 <div id="rfc.figure.u.1 1"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span> <a href="#language.tags" class="smpl">language-tag</a> = <a href="#language.tags" class="smpl">primary-tag</a> *( "-" <a href="#language.tags" class="smpl">subtag</a> )809 <p id="rfc.section.2.4.p.2">The syntax and registry of HTTP language tags is the same as that defined by <a href="#RFC1766" id="rfc.xref.RFC1766.1"><cite title="Tags for the Identification of Languages">[RFC1766]</cite></a>. In summary, a language tag is composed of 1 or more parts: A primary language tag and a possibly empty series of subtags: 810 </p> 811 <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span> <a href="#language.tags" class="smpl">language-tag</a> = <a href="#language.tags" class="smpl">primary-tag</a> *( "-" <a href="#language.tags" class="smpl">subtag</a> ) 813 812 <a href="#language.tags" class="smpl">primary-tag</a> = 1*8<a href="#notation" class="smpl">ALPHA</a> 814 813 <a href="#language.tags" class="smpl">subtag</a> = 1*8<a href="#notation" class="smpl">ALPHA</a> 815 </pre><p id="rfc.section.2. 5.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language tags is administered814 </pre><p id="rfc.section.2.4.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language tags is administered 816 815 by the IANA. Example tags include: 817 816 </p> 818 <div id="rfc.figure.u.1 2"></div><pre class="text">en, en-US, en-cockney, i-cherokee, x-pig-latin819 </pre><p id="rfc.section.2. 5.p.6">where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country817 <div id="rfc.figure.u.11"></div><pre class="text"> en, en-US, en-cockney, i-cherokee, x-pig-latin 818 </pre><p id="rfc.section.2.4.p.6">where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country 820 819 code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered 821 820 in future.) … … 832 831 by the request. 833 832 </p> 834 <div id="rfc.figure.u.1 3"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span> <a href="#entity.header.fields" class="smpl">entity-header</a> = <a href="#header.content-encoding" class="smpl">Content-Encoding</a> ; <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section 5.5</a>833 <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span> <a href="#entity.header.fields" class="smpl">entity-header</a> = <a href="#header.content-encoding" class="smpl">Content-Encoding</a> ; <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section 5.5</a> 835 834 / <a href="#header.content-language" class="smpl">Content-Language</a> ; <a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section 5.6</a> 836 / <a href="#abnf.dependencies" class="smpl">Content-Length</a> ; <a href="#Part1" id="rfc.xref.Part1.1 0"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 8.2</a>835 / <a href="#abnf.dependencies" class="smpl">Content-Length</a> ; <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 8.2</a> 837 836 / <a href="#header.content-location" class="smpl">Content-Location</a> ; <a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section 5.7</a> 838 837 / <a href="#header.content-md5" class="smpl">Content-MD5</a> ; <a href="#header.content-md5" id="rfc.xref.header.content-md5.1" title="Content-MD5">Section 5.8</a> … … 849 848 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="entity.body" href="#entity.body">Entity Body</a></h2> 850 849 <p id="rfc.section.3.2.p.1">The entity-body (if any) sent with an HTTP request or response is in a format and encoding defined by the entity-header fields.</p> 851 <div id="rfc.figure.u.1 4"></div><pre class="inline"><span id="rfc.iref.g.16"></span> <a href="#entity.body" class="smpl">entity-body</a> = *<a href="#notation" class="smpl">OCTET</a>852 </pre><p id="rfc.section.3.2.p.3">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.1 1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure850 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.15"></span> <a href="#entity.body" class="smpl">entity-body</a> = *<a href="#notation" class="smpl">OCTET</a> 851 </pre><p id="rfc.section.3.2.p.3">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure 853 852 safe and proper transfer of the message. 854 853 </p> … … 857 856 and Content-Encoding. These define a two-layer, ordered encoding model: 858 857 </p> 859 <div id="rfc.figure.u.1 5"></div><pre class="text">entity-body := Content-Encoding( Content-Type( data ) )858 <div id="rfc.figure.u.14"></div><pre class="text"> entity-body := Content-Encoding( Content-Type( data ) ) 860 859 </pre><p id="rfc.section.3.2.1.p.3">Content-Type specifies the media type of the underlying data. Content-Encoding may be used to indicate any additional content 861 860 codings applied to the data, usually for the purpose of data compression, that are a property of the requested resource. There … … 867 866 </p> 868 867 <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a> <a id="entity.length" href="#entity.length">Entity Length</a></h3> 869 <p id="rfc.section.3.2.2.p.1">The entity-length of a message is the length of the message-body before any transfer-codings have been applied. <a href="p1-messaging.html#message.length" title="Message Length">Section 4.4</a> of <a href="#Part1" id="rfc.xref.Part1.1 2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> defines how the transfer-length of a message-body is determined.868 <p id="rfc.section.3.2.2.p.1">The entity-length of a message is the length of the message-body before any transfer-codings have been applied. <a href="p1-messaging.html#message.length" title="Message Length">Section 4.4</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> defines how the transfer-length of a message-body is determined. 870 869 </p> 871 870 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1> … … 961 960 a request for an in-line image. 962 961 </p> 963 <div id="rfc.figure.u.1 6"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span> <a href="#header.accept" class="smpl">Accept</a> = "Accept" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept" class="smpl">Accept-v</a>962 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span> <a href="#header.accept" class="smpl">Accept</a> = "Accept" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept" class="smpl">Accept-v</a> 964 963 <a href="#header.accept" class="smpl">Accept-v</a> = #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] ) 965 964 … … 968 967 / ( <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> ) 969 968 ) *( <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> ) 970 <a href="#header.accept" class="smpl">accept-params</a> = <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="# quality.values" class="smpl">qvalue</a> *( <a href="#header.accept" class="smpl">accept-ext</a> )969 <a href="#header.accept" class="smpl">accept-params</a> = <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> *( <a href="#header.accept" class="smpl">accept-ext</a> ) 971 970 <a href="#header.accept" class="smpl">accept-ext</a> = <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#core.rules" class="smpl">token</a> 972 971 [ "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> ) ] … … 976 975 <p id="rfc.section.5.1.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor. The first 977 976 "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user 978 agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href=" #quality.values" title="Quality Values">Section 2.4</a>). The default value is q=1.977 agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1. 979 978 </p> 980 979 <dl class="empty"> … … 986 985 </dl> 987 986 <p id="rfc.section.5.1.p.5">The example</p> 988 <div id="rfc.figure.u.1 7"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic987 <div id="rfc.figure.u.16"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic 989 988 </pre><p id="rfc.section.5.1.p.7"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in 990 989 quality." … … 995 994 </p> 996 995 <p id="rfc.section.5.1.p.9">A more elaborate example is</p> 997 <div id="rfc.figure.u.1 8"></div><pre class="text"> Accept: text/plain; q=0.5, text/html,996 <div id="rfc.figure.u.17"></div><pre class="text"> Accept: text/plain; q=0.5, text/html, 998 997 text/x-dvi; q=0.8, text/x-c 999 998 </pre><p id="rfc.section.5.1.p.11">Verbally, this would be interpreted as "text/html and text/x-c are the preferred media types, but if they do not exist, then … … 1003 1002 to a given type, the most specific reference has precedence. For example, 1004 1003 </p> 1005 <div id="rfc.figure.u.19"></div><pre class="text"> Accept: text/*, text/html, text/html;level=1, */* 1006 </pre><p id="rfc.section.5.1.p.14">have the following precedence:</p> 1007 <div id="rfc.figure.u.20"></div><pre class="text"> 1) text/html;level=1 1008 2) text/html 1009 3) text/* 1010 4) */* 1011 </pre><p id="rfc.section.5.1.p.16">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence 1004 <div id="rfc.figure.u.18"></div><pre class="text"> Accept: text/*, text/html, text/html;level=1, */* 1005 </pre><p id="rfc.section.5.1.p.14">have the following precedence: </p> 1006 <ol> 1007 <li>text/html;level=1</li> 1008 <li>text/html</li> 1009 <li>text/*</li> 1010 <li>*/*</li> 1011 </ol> 1012 <p id="rfc.section.5.1.p.15">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence 1012 1013 which matches that type. For example, 1013 1014 </p> 1014 <div id="rfc.figure.u. 21"></div><pre class="text"> Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,1015 <div id="rfc.figure.u.19"></div><pre class="text"> Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1, 1015 1016 text/html;level=2;q=0.4, */*;q=0.5 1016 </pre><p id="rfc.section.5.1.p.18">would cause the following values to be associated:</p> 1017 <div id="rfc.figure.u.22"></div><pre class="text"> text/html;level=1 = 1 1018 text/html = 0.7 1019 text/plain = 0.3 1020 image/jpeg = 0.5 1021 text/html;level=2 = 0.4 1022 text/html;level=3 = 0.7 1023 </pre><p id="rfc.section.5.1.p.20"> <b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent 1017 </pre><p id="rfc.section.5.1.p.17">would cause the following values to be associated:</p> 1018 <div id="rfc.table.u.1"> 1019 <table summary="" class="tt full" cellpadding="3" cellspacing="0"> 1020 <thead> 1021 <tr> 1022 <th>Media Type</th> 1023 <th>Quality Value</th> 1024 </tr> 1025 </thead> 1026 <tbody> 1027 <tr> 1028 <td>text/html;level=1</td> 1029 <td>1</td> 1030 </tr> 1031 <tr> 1032 <td>text/html</td> 1033 <td>0.7</td> 1034 </tr> 1035 <tr> 1036 <td>text/plain</td> 1037 <td>0.3</td> 1038 </tr> 1039 <tr> 1040 <td>image/jpeg</td> 1041 <td>0.5</td> 1042 </tr> 1043 <tr> 1044 <td>text/html;level=2</td> 1045 <td>0.4</td> 1046 </tr> 1047 <tr> 1048 <td>text/html;level=3</td> 1049 <td>0.7</td> 1050 </tr> 1051 </tbody> 1052 </table> 1053 </div> 1054 <p id="rfc.section.5.1.p.18"> <b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent 1024 1055 is a closed system which cannot interact with other rendering agents, this default set ought to be configurable by the user. 1025 1056 </p> … … 1031 1062 to a server which is capable of representing documents in those character sets. 1032 1063 </p> 1033 <div id="rfc.figure.u.2 3"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset" ":" <a href="#core.rules" class="smpl">OWS</a>1064 <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span> <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset" ":" <a href="#core.rules" class="smpl">OWS</a> 1034 1065 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> 1035 1066 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" ) 1036 [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="# quality.values" class="smpl">qvalue</a> ] )1067 [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] ) 1037 1068 </pre><p id="rfc.section.5.2.p.3">Character set values are described in <a href="#character.sets" title="Character Sets">Section 2.1</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset. The default value is q=1. An 1038 1069 example is 1039 1070 </p> 1040 <div id="rfc.figure.u.2 4"></div><pre class="text"> Accept-Charset: iso-8859-5, unicode-1-1;q=0.81071 <div id="rfc.figure.u.21"></div><pre class="text"> Accept-Charset: iso-8859-5, unicode-1-1;q=0.8 1041 1072 </pre><p id="rfc.section.5.2.p.5">The special value "*", if present in the Accept-Charset field, matches every character set (including ISO-8859-1) which is 1042 1073 not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets … … 1052 1083 <p id="rfc.section.5.3.p.1">The request-header field "Accept-Encoding" is similar to Accept, but restricts the content-codings (<a href="#content.codings" title="Content Codings">Section 2.2</a>) that are acceptable in the response. 1053 1084 </p> 1054 <div id="rfc.figure.u.2 5"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span><span id="rfc.iref.g.26"></span> <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> = "Accept-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a>1085 <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span> <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> = "Accept-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> 1055 1086 <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a> 1056 1087 <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a> = 1057 #( <a href="#header.accept-encoding" class="smpl">codings</a> [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="# quality.values" class="smpl">qvalue</a> ] )1088 #( <a href="#header.accept-encoding" class="smpl">codings</a> [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] ) 1058 1089 <a href="#header.accept-encoding" class="smpl">codings</a> = ( <a href="#content.codings" class="smpl">content-coding</a> / "*" ) 1059 1090 </pre><p id="rfc.section.5.3.p.3">Each codings value <em class="bcp14">MAY</em> be given an associated quality value which represents the preference for that encoding. The default value is q=1. 1060 1091 </p> 1061 1092 <p id="rfc.section.5.3.p.4">Examples of its use are:</p> 1062 <div id="rfc.figure.u.2 6"></div><pre class="text"> Accept-Encoding: compress, gzip1093 <div id="rfc.figure.u.23"></div><pre class="text"> Accept-Encoding: compress, gzip 1063 1094 Accept-Encoding: 1064 1095 Accept-Encoding: * … … 1068 1099 <ol> 1069 1100 <li>If the content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable, unless it 1070 is accompanied by a qvalue of 0. (As defined in <a href=" #quality.values" title="Quality Values">Section 2.4</a>, a qvalue of 0 means "not acceptable.")1101 is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable.") 1071 1102 </li> 1072 1103 <li>The special "*" symbol in an Accept-Encoding field matches any available content-coding not explicitly listed in the header … … 1100 1131 <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a> <a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h2> 1101 1132 <p id="rfc.section.5.4.p.1">The request-header field "Accept-Language" is similar to Accept, but restricts the set of natural languages that are preferred 1102 as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2. 5</a>.1103 </p> 1104 <div id="rfc.figure.u.2 7"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span> <a href="#header.accept-language" class="smpl">Accept-Language</a> = "Accept-Language" ":" <a href="#core.rules" class="smpl">OWS</a>1133 as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2.4</a>. 1134 </p> 1135 <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span> <a href="#header.accept-language" class="smpl">Accept-Language</a> = "Accept-Language" ":" <a href="#core.rules" class="smpl">OWS</a> 1105 1136 <a href="#header.accept-language" class="smpl">Accept-Language-v</a> 1106 1137 <a href="#header.accept-language" class="smpl">Accept-Language-v</a> = 1107 1#( <a href="#header.accept-language" class="smpl">language-range</a> [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="# quality.values" class="smpl">qvalue</a> ] )1138 1#( <a href="#header.accept-language" class="smpl">language-range</a> [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] ) 1108 1139 <a href="#header.accept-language" class="smpl">language-range</a> = 1109 1140 <language-range, defined in <a href="#RFC4647" id="rfc.xref.RFC4647.1"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-2.1">Section 2.1</a>> … … 1111 1142 languages specified by that range. The quality value defaults to "q=1". For example, 1112 1143 </p> 1113 <div id="rfc.figure.u.2 8"></div><pre class="text"> Accept-Language: da, en-gb;q=0.8, en;q=0.71144 <div id="rfc.figure.u.25"></div><pre class="text"> Accept-Language: da, en-gb;q=0.8, en;q=0.7 1114 1145 </pre><p id="rfc.section.5.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English."</p> 1115 1146 <p id="rfc.section.5.4.p.6">For matching, the "Basic Filtering" matching scheme, defined in <a href="http://tools.ietf.org/html/rfc4647#section-3.3.1">Section 3.3.1</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, is used: … … 1155 1186 to be compressed without losing the identity of its underlying media type. 1156 1187 </p> 1157 <div id="rfc.figure.u.2 9"></div><pre class="inline"><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span> <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = "Content-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a>1188 <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span> <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = "Content-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> 1158 1189 <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> = 1#<a href="#content.codings" class="smpl">content-coding</a> 1159 1190 </pre><p id="rfc.section.5.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section 2.2</a>. An example of its use is 1160 1191 </p> 1161 <div id="rfc.figure.u. 30"></div><pre class="text"> Content-Encoding: gzip1192 <div id="rfc.figure.u.27"></div><pre class="text"> Content-Encoding: gzip 1162 1193 </pre><p id="rfc.section.5.5.p.5">The content-coding is a characteristic of the entity identified by the request-target. Typically, the entity-body is stored 1163 1194 with this encoding and is only decoded before rendering or analogous usage. However, a non-transparent proxy <em class="bcp14">MAY</em> modify the content-coding if the new coding is known to be acceptable to the recipient, unless the "no-transform" cache-control … … 1176 1207 Note that this might not be equivalent to all the languages used within the entity-body. 1177 1208 </p> 1178 <div id="rfc.figure.u. 31"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span> <a href="#header.content-language" class="smpl">Content-Language</a> = "Content-Language" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a>1209 <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span> <a href="#header.content-language" class="smpl">Content-Language</a> = "Content-Language" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a> 1179 1210 <a href="#header.content-language" class="smpl">Content-Language-v</a> = 1#<a href="#language.tags" class="smpl">language-tag</a> 1180 </pre><p id="rfc.section.5.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2. 5</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate entities according to the user's1211 </pre><p id="rfc.section.5.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2.4</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate entities according to the user's 1181 1212 own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate field is 1182 1213 </p> 1183 <div id="rfc.figure.u. 32"></div><pre class="text"> Content-Language: da1214 <div id="rfc.figure.u.29"></div><pre class="text"> Content-Language: da 1184 1215 </pre><p id="rfc.section.5.6.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean 1185 1216 that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language … … 1189 1220 simultaneously in the original Maori and English versions, would call for 1190 1221 </p> 1191 <div id="rfc.figure.u.3 3"></div><pre class="text"> Content-Language: mi, en1222 <div id="rfc.figure.u.30"></div><pre class="text"> Content-Language: mi, en 1192 1223 </pre><p id="rfc.section.5.6.p.8">However, just because multiple languages are present within an entity does not mean that it is intended for multiple linguistic 1193 1224 audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin," which is clearly intended … … 1204 1235 accessed, the server <em class="bcp14">SHOULD</em> provide a Content-Location for the particular variant which is returned. 1205 1236 </p> 1206 <div id="rfc.figure.u.3 4"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span> <a href="#header.content-location" class="smpl">Content-Location</a> = "Content-Location" ":" <a href="#core.rules" class="smpl">OWS</a>1237 <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span> <a href="#header.content-location" class="smpl">Content-Location</a> = "Content-Location" ":" <a href="#core.rules" class="smpl">OWS</a> 1207 1238 <a href="#header.content-location" class="smpl">Content-Location-v</a> 1208 1239 <a href="#header.content-location" class="smpl">Content-Location-v</a> = … … 1225 1256 attacks.) 1226 1257 </p> 1227 <div id="rfc.figure.u.3 5"></div><pre class="inline"><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span> <a href="#header.content-md5" class="smpl">Content-MD5</a> = "Content-MD5" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a>1258 <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span> <a href="#header.content-md5" class="smpl">Content-MD5</a> = "Content-MD5" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a> 1228 1259 <a href="#header.content-md5" class="smpl">Content-MD5-v</a> = <base64 of 128 bit MD5 digest as per <a href="#RFC1864" id="rfc.xref.RFC1864.2"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>> 1229 1260 </pre><p id="rfc.section.5.8.p.3">The Content-MD5 header field <em class="bcp14">MAY</em> be generated by an origin server or client to function as an integrity check of the entity-body. Only origin servers or clients <em class="bcp14">MAY</em> generate the Content-MD5 header field; proxies and gateways <em class="bcp14">MUST NOT</em> generate it, as this would defeat its value as an end-to-end integrity check. Any recipient of the entity-body, including … … 1262 1293 the HEAD method, the media type that would have been sent had the request been a GET. 1263 1294 </p> 1264 <div id="rfc.figure.u.3 6"></div><pre class="inline"><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span> <a href="#header.content-type" class="smpl">Content-Type</a> = "Content-Type" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a>1295 <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span> <a href="#header.content-type" class="smpl">Content-Type</a> = "Content-Type" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a> 1265 1296 <a href="#header.content-type" class="smpl">Content-Type-v</a> = <a href="#media.types" class="smpl">media-type</a> 1266 1297 </pre><p id="rfc.section.5.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section 2.3</a>. An example of the field is 1267 1298 </p> 1268 <div id="rfc.figure.u.3 7"></div><pre class="text"> Content-Type: text/html; charset=ISO-8859-41299 <div id="rfc.figure.u.34"></div><pre class="text"> Content-Type: text/html; charset=ISO-8859-4 1269 1300 </pre><p id="rfc.section.5.9.p.5">Further discussion of methods for identifying the media type of an entity is provided in <a href="#type" title="Type">Section 3.2.1</a>. 1270 1301 </p> … … 1406 1437 <tr> 1407 1438 <td class="reference"><b id="Part1">[Part1]</b></td> 1408 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), February 2009.1439 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), March 2009. 1409 1440 </td> 1410 1441 </tr> 1411 1442 <tr> 1412 1443 <td class="reference"><b id="Part2">[Part2]</b></td> 1413 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), February 2009.1444 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), March 2009. 1414 1445 </td> 1415 1446 </tr> 1416 1447 <tr> 1417 1448 <td class="reference"><b id="Part4">[Part4]</b></td> 1418 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), February 2009.1449 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), March 2009. 1419 1450 </td> 1420 1451 </tr> 1421 1452 <tr> 1422 1453 <td class="reference"><b id="Part5">[Part5]</b></td> 1423 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), February 2009.1454 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), March 2009. 1424 1455 </td> 1425 1456 </tr> 1426 1457 <tr> 1427 1458 <td class="reference"><b id="Part6">[Part6]</b></td> 1428 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), February 2009.1459 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), March 2009. 1429 1460 </td> 1430 1461 </tr> … … 1590 1621 environments. 1591 1622 </p> 1592 <div id="rfc.figure.u.3 8"></div><pre class="inline"><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span> <a href="#mime-version" class="smpl">MIME-Version</a> = "MIME-Version" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a>1623 <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span> <a href="#mime-version" class="smpl">MIME-Version</a> = "MIME-Version" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a> 1593 1624 <a href="#mime-version" class="smpl">MIME-Version-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a> 1594 1625 </pre><p id="rfc.section.A.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this … … 1609 1640 </p> 1610 1641 <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> 1611 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#full.date" title="Full Date">Section 3.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.1 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.1642 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#full.date" title="Full Date">Section 3.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.16"><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. 1612 1643 </p> 1613 1644 <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> … … 1626 1657 </p> 1627 1658 <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> 1628 <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 8.7</a> of <a href="#Part1" id="rfc.xref.Part1.1 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.1659 <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 8.7</a> of <a href="#Part1" id="rfc.xref.Part1.17"><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. 1629 1660 </p> 1630 1661 <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> … … 1648 1679 in <a href="#RFC2183" id="rfc.xref.RFC2183.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>. 1649 1680 </p> 1650 <div id="rfc.figure.u.3 9"></div><pre class="inline"><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span> <a href="#content-disposition" class="smpl">content-disposition</a> = "Content-Disposition" ":" <a href="#core.rules" class="smpl">OWS</a>1681 <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span> <a href="#content-disposition" class="smpl">content-disposition</a> = "Content-Disposition" ":" <a href="#core.rules" class="smpl">OWS</a> 1651 1682 <a href="#content-disposition" class="smpl">content-disposition-v</a> 1652 1683 <a href="#content-disposition" class="smpl">content-disposition-v</a> = <a href="#content-disposition" class="smpl">disposition-type</a> … … 1658 1689 <a href="#content-disposition" class="smpl">disp-extension-parm</a> = <a href="#core.rules" class="smpl">token</a> "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> ) 1659 1690 </pre><p id="rfc.section.B.1.p.3">An example is</p> 1660 <div id="rfc.figure.u. 40"></div><pre class="text">Content-Disposition: attachment; filename="fname.ext"1691 <div id="rfc.figure.u.37"></div><pre class="text"> Content-Disposition: attachment; filename="fname.ext" 1661 1692 </pre><p id="rfc.section.B.1.p.5">The receiving user agent <em class="bcp14">SHOULD NOT</em> respect any directory path information present in the filename-parm parameter, which is the only parameter believed to apply 1662 1693 to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only. … … 1671 1702 <p id="rfc.section.C.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow 1672 1703 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 1673 computed. (<a href="#entity.length" title="Entity Length">Section 3.2.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.1 5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).1704 computed. (<a href="#entity.length" title="Entity Length">Section 3.2.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1674 1705 </p> 1675 1706 <p id="rfc.section.C.1.p.2">Charset wildcarding is introduced to avoid explosion of character set names in accept headers. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section 5.2</a>) … … 1680 1711 <p id="rfc.section.C.1.p.4">A content-coding of "identity" was introduced, to solve problems discovered in caching. (<a href="#content.codings" title="Content Codings">Section 2.2</a>) 1681 1712 </p> 1682 <p id="rfc.section.C.1.p.5">Quality Values of zero should indicate that "I don't want something" to allow clients to refuse a representation. (<a href="#quality.values" title="Quality Values">Section 2.4</a>) 1683 </p> 1684 <p id="rfc.section.C.1.p.6">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.12"></span>, Content-Version<span id="rfc.iref.c.8"></span><span id="rfc.iref.h.13"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.14"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.15"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.16"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.17"></span> and Content-Base<span id="rfc.iref.c.9"></span><span id="rfc.iref.h.18"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.2">Section 19.6.2</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 1713 <p id="rfc.section.C.1.p.5">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.12"></span>, Content-Version<span id="rfc.iref.c.8"></span><span id="rfc.iref.h.13"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.14"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.15"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.16"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.17"></span> and Content-Base<span id="rfc.iref.c.9"></span><span id="rfc.iref.h.18"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.2">Section 19.6.2</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 1685 1714 </p> 1686 1715 <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> … … 1690 1719 </p> 1691 1720 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 1692 <div id="rfc.figure.u. 41"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = "Accept:" OWS Accept-v1721 <div id="rfc.figure.u.38"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = "Accept:" OWS Accept-v 1693 1722 <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset:" OWS Accept-Charset-v 1694 1723 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q=" … … 1768 1797 1769 1798 <a href="#core.rules" class="smpl">quoted-string</a> = <quoted-string, defined in [Part1], Section 1.2.2> 1770 <a href="# quality.values" class="smpl">qvalue</a> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )1799 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in [Part1], Section 3.5> 1771 1800 1772 1801 <a href="#language.tags" class="smpl">subtag</a> = 1*8ALPHA … … 1778 1807 <a href="#rule.parameter" class="smpl">value</a> = token / quoted-string 1779 1808 1780 ; Accept defined but not used 1809 1810 </pre> <div id="rfc.figure.u.39"></div> 1811 <p>ABNF diagnostics:</p><pre class="inline">; Accept defined but not used 1781 1812 ; Accept-Charset defined but not used 1782 1813 ; Accept-Encoding defined but not used … … 1786 1817 ; entity-body defined but not used 1787 1818 ; entity-header defined but not used 1788 1789 1790 </pre> <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 1819 </pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 1791 1820 <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a> Since RFC2616 1792 1821 </h2> … … 1880 1909 <ul> 1881 1910 <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> 1911 </ul> 1912 <p id="rfc.section.E.7.p.3">Other changes: </p> 1913 <ul> 1914 <li>Move definition of quality values into Part 1.</li> 1882 1915 </ul> 1883 1916 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> … … 1918 1951 <li class="indline1"><tt>Grammar</tt> 1919 1952 <ul class="ind"> 1920 <li class="indline1"><tt>Accept</tt> <a class="iref" href="#rfc.iref.g.1 7"><b>5.1</b></a></li>1921 <li class="indline1"><tt>Accept-Charset</tt> <a class="iref" href="#rfc.iref.g.2 2"><b>5.2</b></a></li>1922 <li class="indline1"><tt>Accept-Charset-v</tt> <a class="iref" href="#rfc.iref.g.2 3"><b>5.2</b></a></li>1923 <li class="indline1"><tt>Accept-Encoding</tt> <a class="iref" href="#rfc.iref.g.2 4"><b>5.3</b></a></li>1924 <li class="indline1"><tt>Accept-Encoding-v</tt> <a class="iref" href="#rfc.iref.g.2 5"><b>5.3</b></a></li>1925 <li class="indline1"><tt>accept-ext</tt> <a class="iref" href="#rfc.iref.g.2 1"><b>5.1</b></a></li>1926 <li class="indline1"><tt>Accept-Language</tt> <a class="iref" href="#rfc.iref.g.2 7"><b>5.4</b></a></li>1927 <li class="indline1"><tt>Accept-Language-v</tt> <a class="iref" href="#rfc.iref.g.2 8"><b>5.4</b></a></li>1928 <li class="indline1"><tt>accept-params</tt> <a class="iref" href="#rfc.iref.g. 20"><b>5.1</b></a></li>1929 <li class="indline1"><tt>Accept-v</tt> <a class="iref" href="#rfc.iref.g.1 8"><b>5.1</b></a></li>1953 <li class="indline1"><tt>Accept</tt> <a class="iref" href="#rfc.iref.g.16"><b>5.1</b></a></li> 1954 <li class="indline1"><tt>Accept-Charset</tt> <a class="iref" href="#rfc.iref.g.21"><b>5.2</b></a></li> 1955 <li class="indline1"><tt>Accept-Charset-v</tt> <a class="iref" href="#rfc.iref.g.22"><b>5.2</b></a></li> 1956 <li class="indline1"><tt>Accept-Encoding</tt> <a class="iref" href="#rfc.iref.g.23"><b>5.3</b></a></li> 1957 <li class="indline1"><tt>Accept-Encoding-v</tt> <a class="iref" href="#rfc.iref.g.24"><b>5.3</b></a></li> 1958 <li class="indline1"><tt>accept-ext</tt> <a class="iref" href="#rfc.iref.g.20"><b>5.1</b></a></li> 1959 <li class="indline1"><tt>Accept-Language</tt> <a class="iref" href="#rfc.iref.g.26"><b>5.4</b></a></li> 1960 <li class="indline1"><tt>Accept-Language-v</tt> <a class="iref" href="#rfc.iref.g.27"><b>5.4</b></a></li> 1961 <li class="indline1"><tt>accept-params</tt> <a class="iref" href="#rfc.iref.g.19"><b>5.1</b></a></li> 1962 <li class="indline1"><tt>Accept-v</tt> <a class="iref" href="#rfc.iref.g.17"><b>5.1</b></a></li> 1930 1963 <li class="indline1"><tt>attribute</tt> <a class="iref" href="#rfc.iref.g.8"><b>2.3</b></a></li> 1931 1964 <li class="indline1"><tt>charset</tt> <a class="iref" href="#rfc.iref.g.1"><b>2.1</b></a></li> 1932 <li class="indline1"><tt>codings</tt> <a class="iref" href="#rfc.iref.g.2 6"><b>5.3</b></a></li>1965 <li class="indline1"><tt>codings</tt> <a class="iref" href="#rfc.iref.g.25"><b>5.3</b></a></li> 1933 1966 <li class="indline1"><tt>content-coding</tt> <a class="iref" href="#rfc.iref.g.2"><b>2.2</b></a></li> 1934 <li class="indline1"><tt>content-disposition</tt> <a class="iref" href="#rfc.iref.g.4 2"><b>B.1</b></a></li>1935 <li class="indline1"><tt>content-disposition-v</tt> <a class="iref" href="#rfc.iref.g.4 3"><b>B.1</b></a></li>1936 <li class="indline1"><tt>Content-Encoding</tt> <a class="iref" href="#rfc.iref.g. 30"><b>5.5</b></a></li>1937 <li class="indline1"><tt>Content-Encoding-v</tt> <a class="iref" href="#rfc.iref.g.3 1"><b>5.5</b></a></li>1938 <li class="indline1"><tt>Content-Language</tt> <a class="iref" href="#rfc.iref.g.3 2"><b>5.6</b></a></li>1939 <li class="indline1"><tt>Content-Language-v</tt> <a class="iref" href="#rfc.iref.g.3 3"><b>5.6</b></a></li>1940 <li class="indline1"><tt>Content-Location</tt> <a class="iref" href="#rfc.iref.g.3 4"><b>5.7</b></a></li>1941 <li class="indline1"><tt>Content-Location-v</tt> <a class="iref" href="#rfc.iref.g.3 5"><b>5.7</b></a></li>1942 <li class="indline1"><tt>Content-MD5</tt> <a class="iref" href="#rfc.iref.g.3 6"><b>5.8</b></a></li>1943 <li class="indline1"><tt>Content-MD5-v</tt> <a class="iref" href="#rfc.iref.g.3 7"><b>5.8</b></a></li>1944 <li class="indline1"><tt>Content-Type</tt> <a class="iref" href="#rfc.iref.g.3 8"><b>5.9</b></a></li>1945 <li class="indline1"><tt>Content-Type-v</tt> <a class="iref" href="#rfc.iref.g.3 9"><b>5.9</b></a></li>1946 <li class="indline1"><tt>disp-extension-parm</tt> <a class="iref" href="#rfc.iref.g.4 8"><b>B.1</b></a></li>1947 <li class="indline1"><tt>disp-extension-token</tt> <a class="iref" href="#rfc.iref.g.4 7"><b>B.1</b></a></li>1948 <li class="indline1"><tt>disposition-parm</tt> <a class="iref" href="#rfc.iref.g.4 5"><b>B.1</b></a></li>1949 <li class="indline1"><tt>disposition-type</tt> <a class="iref" href="#rfc.iref.g.4 4"><b>B.1</b></a></li>1950 <li class="indline1"><tt>entity-body</tt> <a class="iref" href="#rfc.iref.g.1 6"><b>3.2</b></a></li>1951 <li class="indline1"><tt>entity-header</tt> <a class="iref" href="#rfc.iref.g.1 4"><b>3.1</b></a></li>1952 <li class="indline1"><tt>extension-header</tt> <a class="iref" href="#rfc.iref.g.1 5"><b>3.1</b></a></li>1953 <li class="indline1"><tt>filename-parm</tt> <a class="iref" href="#rfc.iref.g.4 6"><b>B.1</b></a></li>1954 <li class="indline1"><tt>language-range</tt> <a class="iref" href="#rfc.iref.g.2 9"><b>5.4</b></a></li>1955 <li class="indline1"><tt>language-tag</tt> <a class="iref" href="#rfc.iref.g.1 1"><b>2.5</b></a></li>1956 <li class="indline1"><tt>media-range</tt> <a class="iref" href="#rfc.iref.g.1 9"><b>5.1</b></a></li>1967 <li class="indline1"><tt>content-disposition</tt> <a class="iref" href="#rfc.iref.g.41"><b>B.1</b></a></li> 1968 <li class="indline1"><tt>content-disposition-v</tt> <a class="iref" href="#rfc.iref.g.42"><b>B.1</b></a></li> 1969 <li class="indline1"><tt>Content-Encoding</tt> <a class="iref" href="#rfc.iref.g.29"><b>5.5</b></a></li> 1970 <li class="indline1"><tt>Content-Encoding-v</tt> <a class="iref" href="#rfc.iref.g.30"><b>5.5</b></a></li> 1971 <li class="indline1"><tt>Content-Language</tt> <a class="iref" href="#rfc.iref.g.31"><b>5.6</b></a></li> 1972 <li class="indline1"><tt>Content-Language-v</tt> <a class="iref" href="#rfc.iref.g.32"><b>5.6</b></a></li> 1973 <li class="indline1"><tt>Content-Location</tt> <a class="iref" href="#rfc.iref.g.33"><b>5.7</b></a></li> 1974 <li class="indline1"><tt>Content-Location-v</tt> <a class="iref" href="#rfc.iref.g.34"><b>5.7</b></a></li> 1975 <li class="indline1"><tt>Content-MD5</tt> <a class="iref" href="#rfc.iref.g.35"><b>5.8</b></a></li> 1976 <li class="indline1"><tt>Content-MD5-v</tt> <a class="iref" href="#rfc.iref.g.36"><b>5.8</b></a></li> 1977 <li class="indline1"><tt>Content-Type</tt> <a class="iref" href="#rfc.iref.g.37"><b>5.9</b></a></li> 1978 <li class="indline1"><tt>Content-Type-v</tt> <a class="iref" href="#rfc.iref.g.38"><b>5.9</b></a></li> 1979 <li class="indline1"><tt>disp-extension-parm</tt> <a class="iref" href="#rfc.iref.g.47"><b>B.1</b></a></li> 1980 <li class="indline1"><tt>disp-extension-token</tt> <a class="iref" href="#rfc.iref.g.46"><b>B.1</b></a></li> 1981 <li class="indline1"><tt>disposition-parm</tt> <a class="iref" href="#rfc.iref.g.44"><b>B.1</b></a></li> 1982 <li class="indline1"><tt>disposition-type</tt> <a class="iref" href="#rfc.iref.g.43"><b>B.1</b></a></li> 1983 <li class="indline1"><tt>entity-body</tt> <a class="iref" href="#rfc.iref.g.15"><b>3.2</b></a></li> 1984 <li class="indline1"><tt>entity-header</tt> <a class="iref" href="#rfc.iref.g.13"><b>3.1</b></a></li> 1985 <li class="indline1"><tt>extension-header</tt> <a class="iref" href="#rfc.iref.g.14"><b>3.1</b></a></li> 1986 <li class="indline1"><tt>filename-parm</tt> <a class="iref" href="#rfc.iref.g.45"><b>B.1</b></a></li> 1987 <li class="indline1"><tt>language-range</tt> <a class="iref" href="#rfc.iref.g.28"><b>5.4</b></a></li> 1988 <li class="indline1"><tt>language-tag</tt> <a class="iref" href="#rfc.iref.g.10"><b>2.4</b></a></li> 1989 <li class="indline1"><tt>media-range</tt> <a class="iref" href="#rfc.iref.g.18"><b>5.1</b></a></li> 1957 1990 <li class="indline1"><tt>media-type</tt> <a class="iref" href="#rfc.iref.g.4"><b>2.3</b></a></li> 1958 <li class="indline1"><tt>MIME-Version</tt> <a class="iref" href="#rfc.iref.g. 40"><b>A.1</b></a></li>1959 <li class="indline1"><tt>MIME-Version-v</tt> <a class="iref" href="#rfc.iref.g.4 1"><b>A.1</b></a></li>1991 <li class="indline1"><tt>MIME-Version</tt> <a class="iref" href="#rfc.iref.g.39"><b>A.1</b></a></li> 1992 <li class="indline1"><tt>MIME-Version-v</tt> <a class="iref" href="#rfc.iref.g.40"><b>A.1</b></a></li> 1960 1993 <li class="indline1"><tt>parameter</tt> <a class="iref" href="#rfc.iref.g.7"><b>2.3</b></a></li> 1961 <li class="indline1"><tt>primary-tag</tt> <a class="iref" href="#rfc.iref.g.12"><b>2.5</b></a></li> 1962 <li class="indline1"><tt>qvalue</tt> <a class="iref" href="#rfc.iref.g.10"><b>2.4</b></a></li> 1963 <li class="indline1"><tt>subtag</tt> <a class="iref" href="#rfc.iref.g.13"><b>2.5</b></a></li> 1994 <li class="indline1"><tt>primary-tag</tt> <a class="iref" href="#rfc.iref.g.11"><b>2.4</b></a></li> 1995 <li class="indline1"><tt>subtag</tt> <a class="iref" href="#rfc.iref.g.12"><b>2.4</b></a></li> 1964 1996 <li class="indline1"><tt>subtype</tt> <a class="iref" href="#rfc.iref.g.6"><b>2.3</b></a></li> 1965 1997 <li class="indline1"><tt>type</tt> <a class="iref" href="#rfc.iref.g.5"><b>2.3</b></a></li> … … 2009 2041 </li> 2010 2042 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 2011 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.10"> 3.1</a>, <a class="iref" href="#rfc.xref.Part1.11">3.2</a>, <a class="iref" href="#rfc.xref.Part1.12">3.2.2</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.13">A.3</a>, <a class="iref" href="#rfc.xref.Part1.14">A.6</a>, <a class="iref" href="#rfc.xref.Part1.15">C.1</a><ul class="ind">2043 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">3.1</a>, <a class="iref" href="#rfc.xref.Part1.12">3.2</a>, <a class="iref" href="#rfc.xref.Part1.13">3.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">5.1</a>, <a class="iref" href="#rfc.xref.Part1.15">5.3</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.16">A.3</a>, <a class="iref" href="#rfc.xref.Part1.17">A.6</a>, <a class="iref" href="#rfc.xref.Part1.18">C.1</a><ul class="ind"> 2012 2044 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a></li> 2013 2045 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a></li> 2014 2046 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.6">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a></li> 2015 <li class="indline1"><em>Section 3.2.1</em> <a class="iref" href="#rfc.xref.Part1.13">A.3</a></li> 2047 <li class="indline1"><em>Section 3.2.1</em> <a class="iref" href="#rfc.xref.Part1.16">A.3</a></li> 2048 <li class="indline1"><em>Section 3.5</em> <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">5.1</a>, <a class="iref" href="#rfc.xref.Part1.15">5.3</a></li> 2016 2049 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1.8">1.2.2</a></li> 2017 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.1 1">3.2</a></li>2018 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.1 2">3.2.2</a></li>2019 <li class="indline1"><em>Section 8.2</em> <a class="iref" href="#rfc.xref.Part1.7">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.1 0">3.1</a></li>2020 <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.1 4">A.6</a></li>2050 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.12">3.2</a></li> 2051 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.13">3.2.2</a></li> 2052 <li class="indline1"><em>Section 8.2</em> <a class="iref" href="#rfc.xref.Part1.7">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">3.1</a></li> 2053 <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.17">A.6</a></li> 2021 2054 </ul> 2022 2055 </li> … … 2044 2077 </li> 2045 2078 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> 2046 <li class="indline1"><em>RFC1766</em> <a class="iref" href="#rfc.xref.RFC1766.1">2. 5</a>, <a class="iref" href="#RFC1766"><b>9.1</b></a></li>2079 <li class="indline1"><em>RFC1766</em> <a class="iref" href="#rfc.xref.RFC1766.1">2.4</a>, <a class="iref" href="#RFC1766"><b>9.1</b></a></li> 2047 2080 <li class="indline1"><em>RFC1864</em> <a class="iref" href="#rfc.xref.RFC1864.1">5.8</a>, <a class="iref" href="#rfc.xref.RFC1864.2">5.8</a>, <a class="iref" href="#RFC1864"><b>9.1</b></a></li> 2048 2081 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li> -
draft-ietf-httpbis/latest-roy/p3-payload.xml
r446 r461 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " February">15 <!ENTITY ID-MONTH "March"> 16 16 <!ENTITY ID-YEAR "2009"> 17 17 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 31 31 <!ENTITY multipart-byteranges "<xref target='Part5' x:rel='#internet.media.type.multipart.byteranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 32 32 <!ENTITY full-date "<xref target='Part1' x:rel='#full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 33 <!ENTITY qvalue "<xref target='Part1' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 33 34 <!ENTITY uri "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 34 35 ]> … … 296 297 <x:anchor-alias value="message-header"/> 297 298 <x:anchor-alias value="partial-URI"/> 299 <x:anchor-alias value="qvalue"/> 298 300 <t> 299 301 The ABNF rules below are defined in other parts: … … 304 306 <x:ref>message-header</x:ref> = <message-header, defined in &message-headers;> 305 307 <x:ref>partial-URI</x:ref> = <partial-URI, defined in &uri;> 308 <x:ref>qvalue</x:ref> = <qvalue, defined in &qvalue;> 306 309 </artwork></figure> 307 310 <figure><!--Part4--><artwork type="abnf2616"> … … 603 606 </section> 604 607 605 <section title="Quality Values" anchor="quality.values">606 <x:anchor-alias value="qvalue"/>607 <t>608 HTTP content negotiation (<xref target="content.negotiation"/>) uses short "floating point"609 numbers to indicate the relative importance ("weight") of various610 negotiable parameters. A weight is normalized to a real number in611 the range 0 through 1, where 0 is the minimum and 1 the maximum612 value. If a parameter has a quality value of 0, then content with613 this parameter is `not acceptable' for the client. HTTP/1.1614 applications &MUST-NOT; generate more than three digits after the615 decimal point. User configuration of these values &SHOULD; also be616 limited in this fashion.617 </t>618 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="qvalue"/>619 <x:ref>qvalue</x:ref> = ( "0" [ "." 0*3<x:ref>DIGIT</x:ref> ] )620 / ( "1" [ "." 0*3("0") ] )621 </artwork></figure>622 <t>623 "Quality values" is a misnomer, since these values merely represent624 relative degradation in desired quality.625 </t>626 </section>627 628 608 <section title="Language Tags" anchor="language.tags"> 629 609 <x:anchor-alias value="language-tag"/> … … 654 634 </t> 655 635 <figure><artwork type="example"> 656 636 en, en-US, en-cockney, i-cherokee, x-pig-latin 657 637 </artwork></figure> 658 638 <t> … … 730 710 </t> 731 711 <figure><artwork type="example"> 732 712 entity-body := Content-Encoding( Content-Type( data ) ) 733 713 </artwork></figure> 734 714 <t> … … 967 947 parameter(s) from the accept-params. Quality factors allow the user 968 948 or user agent to indicate the relative degree of preference for that 969 media-range, using the qvalue scale from 0 to 1 ( <xref target="quality.values"/>). The949 media-range, using the qvalue scale from 0 to 1 (&qvalue;). The 970 950 default value is q=1. 971 951 <list><t> … … 1020 1000 <t> 1021 1001 have the following precedence: 1022 </t>1023 <figure><artwork type="example">1024 1) text/html;level=11025 2) text/html1026 3) text/*1027 4) */*1028 </ artwork></figure>1002 <list style="numbers"> 1003 <t>text/html;level=1</t> 1004 <t>text/html</t> 1005 <t>text/*</t> 1006 <t>*/*</t> 1007 </list> 1008 </t> 1029 1009 <t> 1030 1010 The media type quality factor associated with a given type is … … 1039 1019 would cause the following values to be associated: 1040 1020 </t> 1041 <figure><artwork type="example"> 1042 text/html;level=1 = 1 1043 text/html = 0.7 1044 text/plain = 0.3 1045 image/jpeg = 0.5 1046 text/html;level=2 = 0.4 1047 text/html;level=3 = 0.7 1048 </artwork></figure> 1021 <texttable align="left"> 1022 <ttcol>Media Type</ttcol><ttcol>Quality Value</ttcol> 1023 <c>text/html;level=1</c> <c>1</c> 1024 <c>text/html</c> <c>0.7</c> 1025 <c>text/plain</c> <c>0.3</c> 1026 <c>image/jpeg</c> <c>0.5</c> 1027 <c>text/html;level=2</c> <c>0.4</c> 1028 <c>text/html;level=3</c> <c>0.7</c> 1029 </texttable> 1049 1030 <t> 1050 1031 <x:h>Note:</x:h> A user agent might be provided with a default set of quality … … 1137 1118 <t>If the content-coding is one of the content-codings listed in 1138 1119 the Accept-Encoding field, then it is acceptable, unless it is 1139 accompanied by a qvalue of 0. (As defined in <xref target="quality.values"/>, a1120 accompanied by a qvalue of 0. (As defined in &qvalue;, a 1140 1121 qvalue of 0 means "not acceptable.")</t> 1141 1122 … … 2589 2570 </t> 2590 2571 <figure><artwork type="example"> 2591 2572 Content-Disposition: attachment; filename="fname.ext" 2592 2573 </artwork></figure> 2593 2574 <t> … … 2632 2613 A content-coding of "identity" was introduced, to solve problems 2633 2614 discovered in caching. (<xref target="content.codings"/>) 2634 </t>2635 <t>2636 Quality Values of zero should indicate that "I don't want something"2637 to allow clients to refuse a representation. (<xref target="quality.values"/>)2638 2615 </t> 2639 2616 <t> … … 2738 2715 2739 2716 <x:ref>quoted-string</x:ref> = <quoted-string, defined in [Part1], Section 1.2.2> 2740 <x:ref>qvalue</x:ref> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )2717 <x:ref>qvalue</x:ref> = <qvalue, defined in [Part1], Section 3.5> 2741 2718 2742 2719 <x:ref>subtag</x:ref> = 1*8ALPHA … … 2748 2725 <x:ref>value</x:ref> = token / quoted-string 2749 2726 2750 ; Accept defined but not used 2727 2728 </artwork> 2729 </figure> 2730 <figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">; Accept defined but not used 2751 2731 ; Accept-Charset defined but not used 2752 2732 ; Accept-Encoding defined but not used … … 2756 2736 ; entity-body defined but not used 2757 2737 ; entity-header defined but not used 2758 2759 2760 </artwork> 2761 </figure> 2762 </section> 2738 </artwork></figure></section> 2763 2739 2764 2740 <section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log"> … … 2941 2917 </list> 2942 2918 </t> 2919 <t> 2920 Other changes: 2921 <list style="symbols"> 2922 <t> 2923 Move definition of quality values into Part 1. 2924 </t> 2925 </list> 2926 </t> 2943 2927 </section> 2944 2928 -
draft-ietf-httpbis/latest-roy/p4-conditional.html
r446 r461 146 146 border-width: 1px; 147 147 } 148 caption { 149 caption-side: bottom; 150 font-weight: bold; 151 font-size: 9pt; 152 margin-top: .5em; 153 } 154 148 155 table.header { 149 156 width: 95%; … … 317 324 } 318 325 @top-right { 319 content: " February2009";326 content: "March 2009"; 320 327 } 321 328 @top-center { … … 361 368 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 362 369 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 363 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 1, 2009-02-20 13:12:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">370 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.424, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 364 371 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 365 372 <meta name="DC.Creator" content="Fielding, R."> … … 373 380 <meta name="DC.Creator" content="Reschke, J. F."> 374 381 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 375 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-0 2">382 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-03"> 376 383 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 377 384 <meta name="DC.Description.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."> … … 404 411 </tr> 405 412 <tr> 406 <td class="header left">Expires: August2009</td>413 <td class="header left">Expires: September 2009</td> 407 414 <td class="header right">HP</td> 408 415 </tr> … … 457 464 <tr> 458 465 <td class="header left"></td> 459 <td class="header right"> February 20, 2009</td>466 <td class="header right">March 2, 2009</td> 460 467 </tr> 461 468 </table> … … 481 488 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 482 489 </p> 483 <p>This Internet-Draft will expire in August2009.</p>490 <p>This Internet-Draft will expire in September 2009.</p> 484 491 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 485 492 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1086 1093 <tr> 1087 1094 <td class="reference"><b id="Part1">[Part1]</b></td> 1088 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), February 2009.1095 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), March 2009. 1089 1096 </td> 1090 1097 </tr> 1091 1098 <tr> 1092 1099 <td class="reference"><b id="Part5">[Part5]</b></td> 1093 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), February 2009.1100 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), March 2009. 1094 1101 </td> 1095 1102 </tr> 1096 1103 <tr> 1097 1104 <td class="reference"><b id="Part6">[Part6]</b></td> 1098 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), February 2009.1105 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), March 2009. 1099 1106 </td> 1100 1107 </tr> … … 1175 1182 <a href="#entity.tags" class="smpl">weak</a> = "W/" 1176 1183 1177 ; ETag defined but not used 1184 1185 </pre> <div id="rfc.figure.u.17"></div> 1186 <p>ABNF diagnostics:</p><pre class="inline">; ETag defined but not used 1178 1187 ; If-Match defined but not used 1179 1188 ; If-Modified-Since defined but not used … … 1181 1190 ; If-Unmodified-Since defined but not used 1182 1191 ; Last-Modified defined but not used 1183 1184 1185 </pre> <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 1192 </pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 1186 1193 <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> Since RFC2616 1187 1194 </h2> -
draft-ietf-httpbis/latest-roy/p4-conditional.xml
r446 r461 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " February">15 <!ENTITY ID-MONTH "March"> 16 16 <!ENTITY ID-YEAR "2009"> 17 17 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 1414 1414 <x:ref>weak</x:ref> = "W/" 1415 1415 1416 ; ETag defined but not used 1416 1417 </artwork> 1418 </figure> 1419 <figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">; ETag defined but not used 1417 1420 ; If-Match defined but not used 1418 1421 ; If-Modified-Since defined but not used … … 1420 1423 ; If-Unmodified-Since defined but not used 1421 1424 ; Last-Modified defined but not used 1422 1423 1424 </artwork> 1425 </figure> 1426 </section> 1425 </artwork></figure></section> 1427 1426 1428 1427 <section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log"> -
draft-ietf-httpbis/latest-roy/p5-range.html
r446 r461 146 146 border-width: 1px; 147 147 } 148 caption { 149 caption-side: bottom; 150 font-weight: bold; 151 font-size: 9pt; 152 margin-top: .5em; 153 } 154 148 155 table.header { 149 156 width: 95%; … … 317 324 } 318 325 @top-right { 319 content: " February2009";326 content: "March 2009"; 320 327 } 321 328 @top-center { … … 361 368 <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C"> 362 369 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 363 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 1, 2009-02-20 13:12:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">370 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.424, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 364 371 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 365 372 <meta name="DC.Creator" content="Fielding, R."> … … 373 380 <meta name="DC.Creator" content="Reschke, J. F."> 374 381 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 375 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-0 2">382 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-03"> 376 383 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 377 384 <meta name="DC.Description.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."> … … 404 411 </tr> 405 412 <tr> 406 <td class="header left">Expires: August2009</td>413 <td class="header left">Expires: September 2009</td> 407 414 <td class="header right">HP</td> 408 415 </tr> … … 457 464 <tr> 458 465 <td class="header left"></td> 459 <td class="header right"> February 20, 2009</td>466 <td class="header right">March 2, 2009</td> 460 467 </tr> 461 468 </table> … … 481 488 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 482 489 </p> 483 <p>This Internet-Draft will expire in August2009.</p>490 <p>This Internet-Draft will expire in September 2009.</p> 484 491 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 485 492 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 915 922 <tr> 916 923 <td class="reference"><b id="Part1">[Part1]</b></td> 917 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), February 2009.924 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), March 2009. 918 925 </td> 919 926 </tr> 920 927 <tr> 921 928 <td class="reference"><b id="Part3">[Part3]</b></td> 922 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), February 2009.929 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), March 2009. 923 930 </td> 924 931 </tr> 925 932 <tr> 926 933 <td class="reference"><b id="Part4">[Part4]</b></td> 927 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), February 2009.934 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), March 2009. 928 935 </td> 929 936 </tr> 930 937 <tr> 931 938 <td class="reference"><b id="Part6">[Part6]</b></td> 932 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), February 2009.939 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), March 2009. 933 940 </td> 934 941 </tr> … … 1133 1140 <a href="#core.rules" class="smpl">token</a> = <token, defined in [Part1], Section 1.2.2> 1134 1141 1135 ; Accept-Ranges defined but not used 1142 1143 </pre> <div id="rfc.figure.u.20"></div> 1144 <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used 1136 1145 ; Content-Range defined but not used 1137 1146 ; If-Range defined but not used 1138 1147 ; Range defined but not used 1139 1140 1141 </pre> <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 1148 </pre><h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 1142 1149 <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a> Since RFC2616 1143 1150 </h2> -
draft-ietf-httpbis/latest-roy/p5-range.xml
r446 r461 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " February">15 <!ENTITY ID-MONTH "March"> 16 16 <!ENTITY ID-YEAR "2009"> 17 17 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 1431 1431 <x:ref>token</x:ref> = <token, defined in [Part1], Section 1.2.2> 1432 1432 1433 ; Accept-Ranges defined but not used 1433 1434 </artwork> 1435 </figure> 1436 <figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">; Accept-Ranges defined but not used 1434 1437 ; Content-Range defined but not used 1435 1438 ; If-Range defined but not used 1436 1439 ; Range defined but not used 1437 1438 1439 </artwork> 1440 </figure> 1441 </section> 1442 1440 </artwork></figure></section> 1443 1441 1444 1442 <section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log"> -
draft-ietf-httpbis/latest-roy/p6-cache.html
r446 r461 149 149 border-width: 1px; 150 150 } 151 caption { 152 caption-side: bottom; 153 font-weight: bold; 154 font-size: 9pt; 155 margin-top: .5em; 156 } 157 151 158 table.header { 152 159 width: 95%; … … 320 327 } 321 328 @top-right { 322 content: " February2009";329 content: "March 2009"; 323 330 } 324 331 @top-center { … … 361 368 <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A"> 362 369 <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B"> 363 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 1, 2009-02-20 13:12:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">370 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.424, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 364 371 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 365 372 <meta name="DC.Creator" content="Fielding, R."> … … 373 380 <meta name="DC.Creator" content="Reschke, J. F."> 374 381 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 375 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-0 2">382 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-03"> 376 383 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 377 384 <meta name="DC.Description.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."> … … 404 411 </tr> 405 412 <tr> 406 <td class="header left">Expires: August2009</td>413 <td class="header left">Expires: September 2009</td> 407 414 <td class="header right">HP</td> 408 415 </tr> … … 457 464 <tr> 458 465 <td class="header left"></td> 459 <td class="header right"> February 20, 2009</td>466 <td class="header right">March 2, 2009</td> 460 467 </tr> 461 468 </table> … … 481 488 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 482 489 </p> 483 <p>This Internet-Draft will expire in August2009.</p>490 <p>This Internet-Draft will expire in September 2009.</p> 484 491 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 485 492 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1452 1459 <tr> 1453 1460 <td class="reference"><b id="Part1">[Part1]</b></td> 1454 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), February 2009.1461 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), March 2009. 1455 1462 </td> 1456 1463 </tr> 1457 1464 <tr> 1458 1465 <td class="reference"><b id="Part2">[Part2]</b></td> 1459 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), February 2009.1466 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), March 2009. 1460 1467 </td> 1461 1468 </tr> 1462 1469 <tr> 1463 1470 <td class="reference"><b id="Part3">[Part3]</b></td> 1464 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), February 2009.1471 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), March 2009. 1465 1472 </td> 1466 1473 </tr> 1467 1474 <tr> 1468 1475 <td class="reference"><b id="Part4">[Part4]</b></td> 1469 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), February 2009.1476 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), March 2009. 1470 1477 </td> 1471 1478 </tr> 1472 1479 <tr> 1473 1480 <td class="reference"><b id="Part5">[Part5]</b></td> 1474 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), February 2009.1481 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), March 2009. 1475 1482 </td> 1476 1483 </tr> 1477 1484 <tr> 1478 1485 <td class="reference"><b id="Part7">[Part7]</b></td> 1479 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), February 2009.1486 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), March 2009. 1480 1487 </td> 1481 1488 </tr> -
draft-ietf-httpbis/latest-roy/p6-cache.xml
r446 r461 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " February">15 <!ENTITY ID-MONTH "March"> 16 16 <!ENTITY ID-YEAR "2009"> 17 17 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> -
draft-ietf-httpbis/latest-roy/p7-auth.html
r446 r461 146 146 border-width: 1px; 147 147 } 148 caption { 149 caption-side: bottom; 150 font-weight: bold; 151 font-size: 9pt; 152 margin-top: .5em; 153 } 154 148 155 table.header { 149 156 width: 95%; … … 317 324 } 318 325 @top-right { 319 content: " February2009";326 content: "March 2009"; 320 327 } 321 328 @top-center { … … 358 365 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 359 366 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 360 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 1, 2009-02-20 13:12:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">367 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.424, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 361 368 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 362 369 <meta name="DC.Creator" content="Fielding, R."> … … 370 377 <meta name="DC.Creator" content="Reschke, J. F."> 371 378 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 372 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-0 2">379 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-03"> 373 380 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 374 381 <meta name="DC.Description.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 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication."> … … 406 413 </tr> 407 414 <tr> 408 <td class="header left">Expires: August2009</td>415 <td class="header left">Expires: September 2009</td> 409 416 <td class="header right">H. Frystyk</td> 410 417 </tr> … … 455 462 <tr> 456 463 <td class="header left"></td> 457 <td class="header right"> February 20, 2009</td>464 <td class="header right">March 2, 2009</td> 458 465 </tr> 459 466 </table> … … 479 486 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 480 487 </p> 481 <p>This Internet-Draft will expire in August2009.</p>488 <p>This Internet-Draft will expire in September 2009.</p> 482 489 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 483 490 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 746 753 <tr> 747 754 <td class="reference"><b id="Part1">[Part1]</b></td> 748 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), February 2009.755 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), March 2009. 749 756 </td> 750 757 </tr> 751 758 <tr> 752 759 <td class="reference"><b id="Part6">[Part6]</b></td> 753 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), February 2009.760 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), March 2009. 754 761 </td> 755 762 </tr> … … 822 829 <a href="#abnf.dependencies" class="smpl">credentials</a> = <credentials, defined in [RFC2617], Section 1.2> 823 830 824 ; Authorization defined but not used 831 832 </pre> <div id="rfc.figure.u.8"></div> 833 <p>ABNF diagnostics:</p><pre class="inline">; Authorization defined but not used 825 834 ; Proxy-Authenticate defined but not used 826 835 ; Proxy-Authorization defined but not used 827 836 ; WWW-Authenticate defined but not used 828 829 830 </pre> <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 837 </pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 831 838 <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> Since RFC2616 832 839 </h2> -
draft-ietf-httpbis/latest-roy/p7-auth.xml
r446 r461 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " February">15 <!ENTITY ID-MONTH "March"> 16 16 <!ENTITY ID-YEAR "2009"> 17 17 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 834 834 <x:ref>credentials</x:ref> = <credentials, defined in [RFC2617], Section 1.2> 835 835 836 ; Authorization defined but not used 836 837 </artwork> 838 </figure> 839 <figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">; Authorization defined but not used 837 840 ; Proxy-Authenticate defined but not used 838 841 ; Proxy-Authorization defined but not used 839 842 ; WWW-Authenticate defined but not used 840 841 842 </artwork> 843 </figure> 844 </section> 845 843 </artwork></figure></section> 846 844 847 845 <section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
Note: See TracChangeset
for help on using the changeset viewer.