Changeset 2301 for draft-ietf-httpbis/latest
- Timestamp:
- 01/07/13 08:47:55 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 12 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2300 r2301 440 440 } 441 441 @top-right { 442 content: "Ju ne2013";442 content: "July 2013"; 443 443 } 444 444 @top-center { … … 449 449 } 450 450 @bottom-center { 451 content: "Expires December 25, 2013";451 content: "Expires January 2, 2014"; 452 452 } 453 453 @bottom-right { … … 486 486 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 487 487 <link href="p2-semantics.html" rel="next"> 488 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.59 7, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">488 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 489 489 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 490 490 <meta name="dct.creator" content="Fielding, R."> 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2013-0 6-23">493 <meta name="dct.issued" scheme="ISO8601" content="2013-07-01"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 520 520 <tr> 521 521 <td class="left">Intended status: Standards Track</td> 522 <td class="right">Ju ne 23, 2013</td>522 <td class="right">July 1, 2013</td> 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: December 25, 2013</td>525 <td class="left">Expires: January 2, 2014</td> 526 526 <td class="right"></td> 527 527 </tr> … … 551 551 in progress”. 552 552 </p> 553 <p>This Internet-Draft will expire on December 25, 2013.</p>553 <p>This Internet-Draft will expire on January 2, 2014.</p> 554 554 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 555 555 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 775 775 </p> 776 776 <div id="core.rules"> 777 <p id="rfc.section.1.2.p.2"> 777 <p id="rfc.section.1.2.p.2"> The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG 778 778 (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR 779 779 (any visible <a href="#USASCII" id="rfc.xref.USASCII.1"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[USASCII]</cite></a> character). … … 876 876 often based on dynamic configuration for load balancing. 877 877 </p> 878 <p id="rfc.section.2.3.p.4"> <span id="rfc.iref.u.2"></span><span id="rfc.iref.d.1"></span><span id="rfc.iref.i.2"></span><span id="rfc.iref.o.2"></span> We use the terms "<dfn>upstream</dfn>" and "<dfn>downstream</dfn>" to describe various requirements in relation to the directional flow of a message: all messages flow from upstream to downstream.878 <p id="rfc.section.2.3.p.4"><span id="rfc.iref.u.2"></span><span id="rfc.iref.d.1"></span> <span id="rfc.iref.i.2"></span><span id="rfc.iref.o.2"></span> We use the terms "<dfn>upstream</dfn>" and "<dfn>downstream</dfn>" to describe various requirements in relation to the directional flow of a message: all messages flow from upstream to downstream. 879 879 Likewise, we use the terms inbound and outbound to refer to directions in relation to the request path: "<dfn>inbound</dfn>" means toward the origin server and "<dfn>outbound</dfn>" means toward the user agent. 880 880 </p> … … 885 885 for the sake of security, annotation services, or shared caching. 886 886 </p> 887 <p id="rfc.section.2.3.p.6"> <span id="rfc.iref.t.1"></span><span id="rfc.iref.n.1"></span> An HTTP-to-HTTP proxy is called a "<dfn>transforming proxy</dfn>" if it is designed or configured to modify request or response messages in a semantically meaningful way (i.e., modifications,887 <p id="rfc.section.2.3.p.6"><span id="rfc.iref.t.1"></span> <span id="rfc.iref.n.1"></span> An HTTP-to-HTTP proxy is called a "<dfn>transforming proxy</dfn>" if it is designed or configured to modify request or response messages in a semantically meaningful way (i.e., modifications, 888 888 beyond those required by normal HTTP processing, that change the message in a way that would be significant to the original 889 889 sender or potentially significant to downstream recipients). For example, a transforming proxy might be acting as a shared … … 893 893 a given message, we use the term "<dfn>non-transforming proxy</dfn>" to target requirements that preserve HTTP message semantics. See <a href="p2-semantics.html#status.203" title="203 Non-Authoritative Information">Section 6.3.4</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> and <a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> for status and warning codes related to transformations. 894 894 </p> 895 <p id="rfc.section.2.3.p.7"><span id="rfc.iref.g.13"></span><span id="rfc.iref.r.4"></span> 895 <p id="rfc.section.2.3.p.7"><span id="rfc.iref.g.13"></span><span id="rfc.iref.r.4"></span> <span id="rfc.iref.a.1"></span> A "<dfn>gateway</dfn>" (a.k.a., "<dfn>reverse proxy</dfn>") is an intermediary that acts as an origin server for the outbound connection, but translates received requests and forwards 896 896 them inbound to another server or servers. Gateways are often used to encapsulate legacy or untrusted information services, 897 897 to improve server performance through "<dfn>accelerator</dfn>" caching, and to enable partitioning or load balancing of HTTP services across multiple machines. … … 907 907 when Transport Layer Security (TLS, <a href="#RFC5246" id="rfc.xref.RFC5246.1"><cite title="The Transport Layer Security (TLS) Protocol Version 1.2">[RFC5246]</cite></a>) is used to establish confidential communication through a shared firewall proxy. 908 908 </p> 909 <p id="rfc.section.2.3.p.10"><span id="rfc.iref.i.3"></span> <span id="rfc.iref.t.3"></span><span id="rfc.iref.c.3"></span> The above categories for intermediary only consider those acting as participants in the HTTP communication. There are also909 <p id="rfc.section.2.3.p.10"><span id="rfc.iref.i.3"></span> <span id="rfc.iref.t.3"></span> <span id="rfc.iref.c.3"></span> The above categories for intermediary only consider those acting as participants in the HTTP communication. There are also 910 910 intermediaries that can act on lower layers of the network protocol stack, filtering or redirecting HTTP traffic without the 911 911 knowledge or permission of message senders. Network intermediaries often introduce security flaws or interoperability problems … … 1241 1241 of the combined field value; a proxy <em class="bcp14">MUST NOT</em> change the order of these field values when forwarding a message. 1242 1242 </p> 1243 <div class="note" id="rfc.section.3.2.2.p.4"> 1244 <p> 1243 <div class="note" id="rfc.section.3.2.2.p.4"> 1244 <p><b>Note:</b> In practice, the "Set-Cookie" header field (<a href="#RFC6265" id="rfc.xref.RFC6265.2"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>) often appears multiple times in a response message and does not use the list syntax, violating the above requirements on 1245 1245 multiple header fields with the same name. Since it cannot be combined into a single field-value, recipients ought to handle 1246 1246 "Set-Cookie" as a special case while processing header fields. (See Appendix A.2.3 of <a href="#Kri2001" id="rfc.xref.Kri2001.1"><cite title="HTTP Cookies: Standards, Privacy, and Politics">[Kri2001]</cite></a> for details.) … … 1267 1267 </div> 1268 1268 <div id="rule.whitespace"> 1269 <p id="rfc.section.3.2.3.p.5"> 1269 <p id="rfc.section.3.2.3.p.5"> </p> 1270 1270 </div> 1271 1271 <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span> <a href="#rule.whitespace" class="smpl">OWS</a> = *( <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">HTAB</a> ) … … 1310 1310 <h3 id="rfc.section.3.2.6"><a href="#rfc.section.3.2.6">3.2.6</a> <a id="field.components" href="#field.components">Field value components</a></h3> 1311 1311 <div id="rule.token.separators"> 1312 <p id="rfc.section.3.2.6.p.1"> 1312 <p id="rfc.section.3.2.6.p.1"> Many HTTP header field values consist of words (token or quoted-string) separated by whitespace or special characters. These 1313 1313 special characters <em class="bcp14">MUST</em> be in a quoted string to be used within a parameter value (as defined in <a href="#transfer.codings" title="Transfer Codings">Section 4</a>). 1314 1314 </p> … … 1327 1327 / "]" / "?" / "=" / "{" / "}" 1328 1328 </pre><div id="rule.quoted-string"> 1329 <p id="rfc.section.3.2.6.p.3"> 1329 <p id="rfc.section.3.2.6.p.3"> A string of text is parsed as a single word if it is quoted using double-quote marks.</p> 1330 1330 </div> 1331 1331 <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span> <a href="#rule.quoted-string" class="smpl">quoted-string</a> = <a href="#core.rules" class="smpl">DQUOTE</a> *( <a href="#rule.quoted-string" class="smpl">qdtext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> ) <a href="#core.rules" class="smpl">DQUOTE</a> … … 1333 1333 <a href="#rule.quoted-string" class="smpl">obs-text</a> = %x80-FF 1334 1334 </pre><div id="rule.quoted-pair"> 1335 <p id="rfc.section.3.2.6.p.5"> 1335 <p id="rfc.section.3.2.6.p.5"> The backslash octet ("\") can be used as a single-octet quoting mechanism within quoted-string constructs:</p> 1336 1336 </div> 1337 1337 <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.50"></span> <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> = "\" ( <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> ) … … 1342 1342 </p> 1343 1343 <div id="rule.comment"> 1344 <p id="rfc.section.3.2.6.p.9"> 1344 <p id="rfc.section.3.2.6.p.9"> Comments can be included in some HTTP header fields by surrounding the comment text with parentheses. Comments are only allowed 1345 1345 in fields containing "comment" as part of their field value definition. 1346 1346 </p> … … 1349 1349 <a href="#rule.comment" class="smpl">ctext</a> = <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / %x21-27 / %x2A-5B / %x5D-7E / <a href="#rule.quoted-string" class="smpl">obs-text</a> 1350 1350 </pre><div id="rule.quoted-cpair"> 1351 <p id="rfc.section.3.2.6.p.11"> 1351 <p id="rfc.section.3.2.6.p.11"> The backslash octet ("\") can be used as a single-octet quoting mechanism within comment constructs:</p> 1352 1352 </div> 1353 1353 <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.53"></span> <a href="#rule.quoted-cpair" class="smpl">quoted-cpair</a> = "\" ( <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> ) … … 1441 1441 that decimal value prior to determining the message body length. 1442 1442 </p> 1443 <div class="note" id="rfc.section.3.3.2.p.13"> 1444 <p> 1443 <div class="note" id="rfc.section.3.3.2.p.13"> 1444 <p><b>Note:</b> HTTP's use of Content-Length for message framing differs significantly from the same field's use in MIME, where it is an optional 1445 1445 field used only within the "message/external-body" media-type. 1446 1446 </p> … … 1449 1449 <h3 id="rfc.section.3.3.3"><a href="#rfc.section.3.3.3">3.3.3</a> <a id="message.body.length" href="#message.body.length">Message Body Length</a></h3> 1450 1450 <p id="rfc.section.3.3.3.p.1">The length of a message body is determined by one of the following (in order of precedence):</p> 1451 <p id="rfc.section.3.3.3.p.2"> 1451 <p id="rfc.section.3.3.3.p.2"></p> 1452 1452 <ol> 1453 1453 <li> … … 1557 1557 <a href="#transfer.codings" class="smpl">transfer-extension</a> = <a href="#rule.token.separators" class="smpl">token</a> *( <a href="#rule.whitespace" class="smpl">OWS</a> ";" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">transfer-parameter</a> ) 1558 1558 </pre><div id="rule.parameter"> 1559 <p id="rfc.section.4.p.3"> 1559 <p id="rfc.section.4.p.3"> Parameters are in the form of attribute/value pairs.</p> 1560 1560 </div> 1561 1561 <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span> <a href="#rule.parameter" class="smpl">transfer-parameter</a> = <a href="#rule.parameter" class="smpl">attribute</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> <a href="#rule.parameter" class="smpl">value</a> … … 1653 1653 <p id="rfc.section.4.2.2.p.1">The "deflate" coding is a "zlib" data format <a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> containing a "deflate" compressed data stream <a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a> that uses a combination of the Lempel-Ziv (LZ77) compression algorithm and Huffman coding. 1654 1654 </p> 1655 <div class="note" id="rfc.section.4.2.2.p.2"> 1656 <p> 1655 <div class="note" id="rfc.section.4.2.2.p.2"> 1656 <p><b>Note:</b> Some incorrect implementations send the "deflate" compressed data without the zlib wrapper. 1657 1657 </p> 1658 1658 </div> … … 1741 1741 <a href="#asterisk-form" class="smpl">asterisk-form</a> = "*" 1742 1742 </pre><div id="origin-form"> 1743 <p id="rfc.section.5.3.p.3"><span id="rfc.iref.o.3"></span> 1743 <p id="rfc.section.5.3.p.3"><span id="rfc.iref.o.3"></span> <b>origin-form</b> 1744 1744 </p> 1745 1745 </div> … … 1757 1757 </pre><p id="rfc.section.5.3.p.9">followed by the remainder of the request message.</p> 1758 1758 <div id="absolute-form"> 1759 <p id="rfc.section.5.3.p.10"><span id="rfc.iref.a.2"></span> 1759 <p id="rfc.section.5.3.p.10"><span id="rfc.iref.a.2"></span> <b>absolute-form</b> 1760 1760 </p> 1761 1761 </div> … … 1769 1769 </p> 1770 1770 <div id="authority-form"> 1771 <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.3"></span> 1771 <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.3"></span> <b>authority-form</b> 1772 1772 </p> 1773 1773 </div> … … 1776 1776 <div id="rfc.figure.u.41"></div><pre class="text2">CONNECT www.example.com:80 HTTP/1.1 1777 1777 </pre><div id="asterisk-form"> 1778 <p id="rfc.section.5.3.p.18"><span id="rfc.iref.a.4"></span> 1778 <p id="rfc.section.5.3.p.18"><span id="rfc.iref.a.4"></span> <b>asterisk-form</b> 1779 1779 </p> 1780 1780 </div> … … 1996 1996 </pre><p id="rfc.section.6.1.p.12">in either the request or the response header fields indicates that the connection <em class="bcp14">MUST</em> be closed after the current request/response is complete (<a href="#persistent.tear-down" id="rfc.xref.persistent.tear-down.1" title="Tear-down">Section 6.6</a>). 1997 1997 </p> 1998 <p id="rfc.section.6.1.p.13">A client that does not support <a href="#persistent.connections" class="smpl">persistent connections</a> 1999 </p> 2000 <p id="rfc.section.6.1.p.14">A server that does not support <a href="#persistent.connections" class="smpl">persistent connections</a> 1998 <p id="rfc.section.6.1.p.13">A client that does not support <a href="#persistent.connections" class="smpl">persistent connections</a> <em class="bcp14">MUST</em> send the "close" connection option in every request message. 1999 </p> 2000 <p id="rfc.section.6.1.p.14">A server that does not support <a href="#persistent.connections" class="smpl">persistent connections</a> <em class="bcp14">MUST</em> send the "close" connection option in every response message that does not have a <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a> status code. 2001 2001 </p> 2002 2002 <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a> <a id="persistent.establishment" href="#persistent.establishment">Establishment</a></h2> … … 2195 2195 <td class="left">http</td> 2196 2196 <td class="left">standard</td> 2197 <td class="left"> 2197 <td class="left"><a href="#header.connection" id="rfc.xref.header.connection.7" title="Connection">Section 6.1</a> 2198 2198 </td> 2199 2199 </tr> … … 2202 2202 <td class="left">http</td> 2203 2203 <td class="left">standard</td> 2204 <td class="left"> 2204 <td class="left"><a href="#header.content-length" id="rfc.xref.header.content-length.1" title="Content-Length">Section 3.3.2</a> 2205 2205 </td> 2206 2206 </tr> … … 2209 2209 <td class="left">http</td> 2210 2210 <td class="left">standard</td> 2211 <td class="left"> 2211 <td class="left"><a href="#header.host" id="rfc.xref.header.host.2" title="Host">Section 5.4</a> 2212 2212 </td> 2213 2213 </tr> … … 2216 2216 <td class="left">http</td> 2217 2217 <td class="left">standard</td> 2218 <td class="left"> 2218 <td class="left"><a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section 4.3</a> 2219 2219 </td> 2220 2220 </tr> … … 2223 2223 <td class="left">http</td> 2224 2224 <td class="left">standard</td> 2225 <td class="left"> 2225 <td class="left"><a href="#header.trailer" id="rfc.xref.header.trailer.1" title="Trailer">Section 4.1.1</a> 2226 2226 </td> 2227 2227 </tr> … … 2230 2230 <td class="left">http</td> 2231 2231 <td class="left">standard</td> 2232 <td class="left"> 2232 <td class="left"><a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.3" title="Transfer-Encoding">Section 3.3.1</a> 2233 2233 </td> 2234 2234 </tr> … … 2237 2237 <td class="left">http</td> 2238 2238 <td class="left">standard</td> 2239 <td class="left"> 2239 <td class="left"><a href="#header.upgrade" id="rfc.xref.header.upgrade.2" title="Upgrade">Section 6.7</a> 2240 2240 </td> 2241 2241 </tr> … … 2244 2244 <td class="left">http</td> 2245 2245 <td class="left">standard</td> 2246 <td class="left"> 2246 <td class="left"><a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section 5.7.1</a> 2247 2247 </td> 2248 2248 </tr> … … 2268 2268 <td class="left">http</td> 2269 2269 <td class="left">reserved</td> 2270 <td class="left"> 2270 <td class="left"><a href="#header.field.registration" title="Header Field Registration">Section 7.1</a> 2271 2271 </td> 2272 2272 </tr> … … 2314 2314 for all "message" types regarding line length and encodings. 2315 2315 </p> 2316 <p id="rfc.section.7.3.1.p.2"> 2316 <p id="rfc.section.7.3.1.p.2"></p> 2317 2317 <dl> 2318 2318 <dt>Type name:</dt> … … 2344 2344 <dt>Applications that use this media type:</dt> 2345 2345 <dt>Additional information:</dt> 2346 <dd> 2346 <dd> 2347 2347 <dl> 2348 2348 <dt>Magic number(s):</dt> … … 2369 2369 <h3 id="rfc.section.7.3.2"><a href="#rfc.section.7.3.2">7.3.2</a> <a id="internet.media.type.application.http" href="#internet.media.type.application.http">Internet Media Type application/http</a></h3> 2370 2370 <p id="rfc.section.7.3.2.p.1">The application/http type can be used to enclose a pipeline of one or more HTTP request or response messages (not intermixed).</p> 2371 <p id="rfc.section.7.3.2.p.2"> 2371 <p id="rfc.section.7.3.2.p.2"></p> 2372 2372 <dl> 2373 2373 <dt>Type name:</dt> … … 2401 2401 <dt>Applications that use this media type:</dt> 2402 2402 <dt>Additional information:</dt> 2403 <dd> 2403 <dd> 2404 2404 <dl> 2405 2405 <dt>Magic number(s):</dt> … … 2454 2454 <td class="left">chunked</td> 2455 2455 <td class="left">Transfer in a series of chunks</td> 2456 <td class="left"> 2456 <td class="left"><a href="#chunked.encoding" title="Chunked Transfer Coding">Section 4.1</a> 2457 2457 </td> 2458 2458 </tr> … … 2460 2460 <td class="left">compress</td> 2461 2461 <td class="left">UNIX "compress" data format <a href="#Welch" id="rfc.xref.Welch.2"><cite title="A Technique for High Performance Data Compression">[Welch]</cite></a></td> 2462 <td class="left"> 2462 <td class="left"><a href="#compress.coding" title="Compress Coding">Section 4.2.1</a> 2463 2463 </td> 2464 2464 </tr> … … 2467 2467 <td class="left">"deflate" compressed data (<a href="#RFC1951" id="rfc.xref.RFC1951.2"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.2"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>) 2468 2468 </td> 2469 <td class="left"> 2469 <td class="left"><a href="#deflate.coding" title="Deflate Coding">Section 4.2.2</a> 2470 2470 </td> 2471 2471 </tr> … … 2473 2473 <td class="left">gzip</td> 2474 2474 <td class="left">GZIP file format <a href="#RFC1952" id="rfc.xref.RFC1952.2"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td> 2475 <td class="left"> 2475 <td class="left"><a href="#gzip.coding" title="Gzip Coding">Section 4.2.3</a> 2476 2476 </td> 2477 2477 </tr> … … 2479 2479 <td class="left">x-compress</td> 2480 2480 <td class="left">Deprecated (alias for compress)</td> 2481 <td class="left"> 2481 <td class="left"><a href="#compress.coding" title="Compress Coding">Section 4.2.1</a> 2482 2482 </td> 2483 2483 </tr> … … 2485 2485 <td class="left">x-gzip</td> 2486 2486 <td class="left">Deprecated (alias for gzip)</td> 2487 <td class="left"> 2487 <td class="left"><a href="#gzip.coding" title="Gzip Coding">Section 4.2.3</a> 2488 2488 </td> 2489 2489 </tr> … … 2657 2657 <tr> 2658 2658 <td class="reference"><b id="Part2">[Part2]</b></td> 2659 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), Ju ne 2013.2659 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), July 2013. 2660 2660 </td> 2661 2661 </tr> 2662 2662 <tr> 2663 2663 <td class="reference"><b id="Part4">[Part4]</b></td> 2664 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), Ju ne 2013.2664 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), July 2013. 2665 2665 </td> 2666 2666 </tr> 2667 2667 <tr> 2668 2668 <td class="reference"><b id="Part5">[Part5]</b></td> 2669 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), Ju ne 2013.2669 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), July 2013. 2670 2670 </td> 2671 2671 </tr> 2672 2672 <tr> 2673 2673 <td class="reference"><b id="Part6">[Part6]</b></td> 2674 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), Ju ne 2013.2674 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), July 2013. 2675 2675 </td> 2676 2676 </tr> 2677 2677 <tr> 2678 2678 <td class="reference"><b id="Part7">[Part7]</b></td> 2679 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), Ju ne 2013.2679 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), July 2013. 2680 2680 </td> 2681 2681 </tr> … … 3014 3014 "," 3015 3015 ", ," 3016 </pre><p id="rfc.section.B.p.15"> 3016 </pre><p id="rfc.section.B.p.15"><a href="#collected.abnf" title="Collected ABNF">Appendix C</a> shows the collected ABNF, with the list rules expanded as explained above. 3017 3017 </p> 3018 3018 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 3147 3147 <p id="rfc.section.D.2.p.1">Closed issues: </p> 3148 3148 <ul> 3149 <li> 3150 </li> 3151 <li> 3152 </li> 3153 <li> 3154 </li> 3155 <li> 3156 </li> 3157 <li> 3158 </li> 3159 <li> 3160 </li> 3161 <li> 3162 </li> 3163 <li> 3164 </li> 3165 <li> 3166 </li> 3167 <li> 3168 </li> 3169 <li> 3170 </li> 3171 <li> 3172 </li> 3173 <li> 3174 </li> 3175 <li> 3176 </li> 3177 <li> 3178 </li> 3179 <li> 3180 </li> 3181 <li> 3182 </li> 3183 <li> 3184 </li> 3185 <li> 3186 </li> 3187 <li> 3149 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/128">http://tools.ietf.org/wg/httpbis/trac/ticket/128</a>>: "Cite HTTPS URI scheme definition" (the spec now includes the HTTPs scheme definition and thus updates RFC 2818) 3150 </li> 3151 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/389">http://tools.ietf.org/wg/httpbis/trac/ticket/389</a>>: "mention of 'proxies' in section about caches" 3152 </li> 3153 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/390">http://tools.ietf.org/wg/httpbis/trac/ticket/390</a>>: "use of ABNF terms from RFC 3986" 3154 </li> 3155 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/391">http://tools.ietf.org/wg/httpbis/trac/ticket/391</a>>: "transferring URIs with userinfo in payload" 3156 </li> 3157 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/392">http://tools.ietf.org/wg/httpbis/trac/ticket/392</a>>: "editorial improvements to message length definition" 3158 </li> 3159 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/395">http://tools.ietf.org/wg/httpbis/trac/ticket/395</a>>: "Connection header field MUST vs SHOULD" 3160 </li> 3161 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/396">http://tools.ietf.org/wg/httpbis/trac/ticket/396</a>>: "editorial improvements to persistent connections section" 3162 </li> 3163 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/397">http://tools.ietf.org/wg/httpbis/trac/ticket/397</a>>: "URI normalization vs empty path" 3164 </li> 3165 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/408">http://tools.ietf.org/wg/httpbis/trac/ticket/408</a>>: "p1 feedback" 3166 </li> 3167 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/409">http://tools.ietf.org/wg/httpbis/trac/ticket/409</a>>: "is parsing OBS-FOLD mandatory?" 3168 </li> 3169 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/410">http://tools.ietf.org/wg/httpbis/trac/ticket/410</a>>: "HTTPS and Shared Caching" 3170 </li> 3171 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/411">http://tools.ietf.org/wg/httpbis/trac/ticket/411</a>>: "Requirements for recipients of ws between start-line and first header field" 3172 </li> 3173 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/412">http://tools.ietf.org/wg/httpbis/trac/ticket/412</a>>: "SP and HT when being tolerant" 3174 </li> 3175 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/414">http://tools.ietf.org/wg/httpbis/trac/ticket/414</a>>: "Message Parsing Strictness" 3176 </li> 3177 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/415">http://tools.ietf.org/wg/httpbis/trac/ticket/415</a>>: "'Render'" 3178 </li> 3179 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>>: "No-Transform" 3180 </li> 3181 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/419">http://tools.ietf.org/wg/httpbis/trac/ticket/419</a>>: "p2 editorial feedback" 3182 </li> 3183 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/420">http://tools.ietf.org/wg/httpbis/trac/ticket/420</a>>: "Content-Length SHOULD be sent" 3184 </li> 3185 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/431">http://tools.ietf.org/wg/httpbis/trac/ticket/431</a>>: "origin-form does not allow path starting with "//"" 3186 </li> 3187 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/433">http://tools.ietf.org/wg/httpbis/trac/ticket/433</a>>: "ambiguity in part 1 example" 3188 3188 </li> 3189 3189 </ul> … … 3191 3191 <p id="rfc.section.D.3.p.1">Closed issues: </p> 3192 3192 <ul> 3193 <li> 3194 </li> 3195 <li> 3196 </li> 3197 <li> 3198 </li> 3199 <li> 3200 </li> 3201 <li> 3202 </li> 3203 <li> 3204 </li> 3205 <li> 3206 </li> 3207 <li> 3208 </li> 3209 <li> 3210 </li> 3211 <li> 3212 </li> 3213 <li> 3214 </li> 3215 <li> 3216 </li> 3217 <li> 3218 </li> 3219 <li> 3220 </li> 3221 <li> 3193 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/435">http://tools.ietf.org/wg/httpbis/trac/ticket/435</a>>: "Part1 should have a reference to TCP (RFC 793)" 3194 </li> 3195 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>>: "media type registration template issues" 3196 </li> 3197 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/442">http://tools.ietf.org/wg/httpbis/trac/ticket/442</a>>: "BWS" (vs conformance) 3198 </li> 3199 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/444">http://tools.ietf.org/wg/httpbis/trac/ticket/444</a>>: "obs-fold language" 3200 </li> 3201 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/445">http://tools.ietf.org/wg/httpbis/trac/ticket/445</a>>: "Ordering in Upgrade" 3202 </li> 3203 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/446">http://tools.ietf.org/wg/httpbis/trac/ticket/446</a>>: "p1 editorial feedback" 3204 </li> 3205 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/447">http://tools.ietf.org/wg/httpbis/trac/ticket/447</a>>: "HTTP and TCP name delegation" 3206 </li> 3207 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/449">http://tools.ietf.org/wg/httpbis/trac/ticket/449</a>>: "Receiving a higher minor HTTP version number" 3208 </li> 3209 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/451">http://tools.ietf.org/wg/httpbis/trac/ticket/451</a>>: "HTTP(S) URIs and fragids" 3210 </li> 3211 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/457">http://tools.ietf.org/wg/httpbis/trac/ticket/457</a>>: "Registering x-gzip and x-deflate" 3212 </li> 3213 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/460">http://tools.ietf.org/wg/httpbis/trac/ticket/460</a>>: "Via and gateways" 3214 </li> 3215 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/465">http://tools.ietf.org/wg/httpbis/trac/ticket/465</a>>: "Mention 203 Non-Authoritative Information in p1" 3216 </li> 3217 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/476">http://tools.ietf.org/wg/httpbis/trac/ticket/476</a>>: "SHOULD and conformance" 3218 </li> 3219 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/477">http://tools.ietf.org/wg/httpbis/trac/ticket/477</a>>: "Pipelining language" 3220 </li> 3221 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/482">http://tools.ietf.org/wg/httpbis/trac/ticket/482</a>>: "proxy handling of a really bad Content-Length" 3222 3222 </li> 3223 3223 </ul> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2300 r2301 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 "Ju ne">15 <!ENTITY ID-MONTH "July"> 16 16 <!ENTITY ID-YEAR "2013"> 17 17 <!ENTITY mdash "—"> -
draft-ietf-httpbis/latest/p2-semantics.html
r2294 r2301 440 440 } 441 441 @top-right { 442 content: "Ju ne2013";442 content: "July 2013"; 443 443 } 444 444 @top-center { … … 449 449 } 450 450 @bottom-center { 451 content: "Expires December 18, 2013";451 content: "Expires January 2, 2014"; 452 452 } 453 453 @bottom-right { … … 489 489 <link href="p1-messaging.html" rel="prev"> 490 490 <link href="p4-conditional.html" rel="next"> 491 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.59 7, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">491 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 492 492 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 493 493 <meta name="dct.creator" content="Fielding, R."> 494 494 <meta name="dct.creator" content="Reschke, J. F."> 495 495 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 496 <meta name="dct.issued" scheme="ISO8601" content="2013-0 6-16">496 <meta name="dct.issued" scheme="ISO8601" content="2013-07-01"> 497 497 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 498 498 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation."> … … 522 522 <tr> 523 523 <td class="left">Intended status: Standards Track</td> 524 <td class="right">Ju ne 16, 2013</td>524 <td class="right">July 1, 2013</td> 525 525 </tr> 526 526 <tr> 527 <td class="left">Expires: December 18, 2013</td>527 <td class="left">Expires: January 2, 2014</td> 528 528 <td class="right"></td> 529 529 </tr> … … 553 553 in progress”. 554 554 </p> 555 <p>This Internet-Draft will expire on December 18, 2013.</p>555 <p>This Internet-Draft will expire on January 2, 2014.</p> 556 556 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 557 557 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 896 896 <a href="#media.type" class="smpl">subtype</a> = <a href="#imported.abnf" class="smpl">token</a> 897 897 </pre><div id="rule.parameter"> 898 <p id="rfc.section.3.1.1.1.p.3"> 898 <p id="rfc.section.3.1.1.1.p.3"> The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs. 899 899 </p> 900 900 </div> … … 915 915 </pre><p id="rfc.section.3.1.1.1.p.8">Internet media types ought to be registered with IANA according to the procedures defined in <a href="#BCP13" id="rfc.xref.BCP13.1"><cite title="Media Type Specifications and Registration Procedures">[BCP13]</cite></a>. 916 916 </p> 917 <div class="note" id="rfc.section.3.1.1.1.p.9"> 918 <p> 917 <div class="note" id="rfc.section.3.1.1.1.p.9"> 918 <p><b>Note:</b> Unlike some similar constructs in other header fields, media type parameters do not allow whitespace (even "bad" whitespace) 919 919 around the "=" character. 920 920 </p> … … 1027 1027 other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the <a href="#header.accept-language" class="smpl">Accept-Language</a> and <a href="#header.content-language" class="smpl">Content-Language</a> header fields. 1028 1028 </p> 1029 <p id="rfc.section.3.1.3.1.p.2"> 1029 <p id="rfc.section.3.1.3.1.p.2"><a href="#header.accept-language" class="smpl">Accept-Language</a> uses the looser language-range production defined in <a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section 5.3.5</a>, whereas <a href="#header.content-language" class="smpl">Content-Language</a> uses the stricter language-tag production defined below. 1030 1030 </p> 1031 1031 <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.12"></span> <a href="#language.tags" class="smpl">language-tag</a> = <Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>> … … 1688 1688 <h4 id="rfc.section.5.1.1.1"><a href="#rfc.section.5.1.1.1">5.1.1.1</a> <a id="use.of.the.100.status" href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></h4> 1689 1689 <p id="rfc.section.5.1.1.1.p.1">The only expectation defined by this specification is:</p> 1690 <p id="rfc.section.5.1.1.1.p.2"> <dfn>100-continue</dfn>1690 <p id="rfc.section.5.1.1.1.p.2"><dfn>100-continue</dfn> 1691 1691 </p> 1692 1692 <ul class="empty"> … … 1862 1862 since it acts as a separator between the two parameter sets. 1863 1863 </p> 1864 <div class="note" id="rfc.section.5.3.2.p.5"> 1865 <p> 1864 <div class="note" id="rfc.section.5.3.2.p.5"> 1865 <p><b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice. 1866 1866 Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to 1867 1867 be unlikely given the lack of any "q" parameters in the IANA media type registry and the rare usage of any media type parameters … … 1871 1871 <p id="rfc.section.5.3.2.p.6">The example</p> 1872 1872 <div id="rfc.figure.u.24"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic 1873 </pre><p id="rfc.section.5.3.2.p.8"> 1873 </pre><p id="rfc.section.5.3.2.p.8"><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 1874 1874 quality". 1875 1875 </p> … … 1937 1937 </table> 1938 1938 </div> 1939 <p id="rfc.section.5.3.2.p.19"> 1939 <p id="rfc.section.5.3.2.p.19"><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 1940 1940 is a closed system that cannot interact with other rendering agents, this default set ought to be configurable by the user. 1941 1941 </p> … … 1996 1996 response have a content-coding that is listed as acceptable, the origin server <em class="bcp14">SHOULD</em> send a response without any content-coding. 1997 1997 </p> 1998 <div class="note" id="rfc.section.5.3.4.p.9"> 1999 <p> 1998 <div class="note" id="rfc.section.5.3.4.p.9"> 1999 <p><b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues might 2000 2000 not work and are not permitted with x-gzip or x-compress. 2001 2001 </p> … … 2034 2034 preference. A user agent that does not provide such control to the user <em class="bcp14">MUST NOT</em> send an Accept-Language header field. 2035 2035 </p> 2036 <div class="note" id="rfc.section.5.3.5.p.11"> 2037 <p> 2036 <div class="note" id="rfc.section.5.3.5.p.11"> 2037 <p><b>Note:</b> User agents ought to provide guidance to users when setting a preference, since users are rarely familiar with the details 2038 2038 of language matching as described above. For example, users might assume that on selecting "en-gb", they will be served any 2039 2039 kind of English document if British English is not available. A user agent might suggest, in such a case, to add "en" to the … … 2177 2177 </p> 2178 2178 <ul> 2179 <li> 2180 </li> 2181 <li> 2182 </li> 2183 <li> 2184 </li> 2185 <li> 2186 </li> 2187 <li> 2179 <li><a href="#status.1xx" class="smpl">1xx (Informational)</a>: The request was received, continuing process 2180 </li> 2181 <li><a href="#status.2xx" class="smpl">2xx (Successful)</a>: The request was successfully received, understood, and accepted 2182 </li> 2183 <li><a href="#status.3xx" class="smpl">3xx (Redirection)</a>: Further action needs to be taken in order to complete the request 2184 </li> 2185 <li><a href="#status.4xx" class="smpl">4xx (Client Error)</a>: The request contains bad syntax or cannot be fulfilled 2186 </li> 2187 <li><a href="#status.5xx" class="smpl">5xx (Server Error)</a>: The server failed to fulfill an apparently valid request 2188 2188 </li> 2189 2189 </ul> … … 2564 2564 </li> 2565 2565 </ol> 2566 <div class="note" id="rfc.section.6.4.p.3"> 2567 <p> 2566 <div class="note" id="rfc.section.6.4.p.3"> 2567 <p><b>Note:</b> In HTTP/1.0, the status codes <a href="#status.301" class="smpl">301 (Moved Permanently)</a> and <a href="#status.302" class="smpl">302 (Found)</a> were defined for the first type of redirect (<a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, <a href="http://tools.ietf.org/html/rfc1945#section-9.3">Section 9.3</a>). Early user agents split on whether the method applied to the redirect target would be the same as the original request 2568 2568 or would be rewritten as GET. Although HTTP originally defined the former semantics for <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a> (to match its original implementation at CERN), and defined <a href="#status.303" class="smpl">303 (See Other)</a> to match the latter semantics, prevailing practice gradually converged on the latter semantics for <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a> as well. The first revision of HTTP/1.1 added <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> to indicate the former semantics without being impacted by divergent practice. Over 10 years later, most user agents still 2569 2569 do method rewriting for <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a>; therefore, this specification makes that behavior conformant when the original request is POST. … … 2572 2572 <p id="rfc.section.6.4.p.4">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops). 2573 2573 </p> 2574 <div class="note" id="rfc.section.6.4.p.5"> 2575 <p> 2574 <div class="note" id="rfc.section.6.4.p.5"> 2575 <p><b>Note:</b> An earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3">Section 10.3</a>). Content developers need to be aware that some clients might implement such a fixed limitation. 2576 2576 </p> 2577 2577 </div> … … 2591 2591 <p id="rfc.section.6.4.1.p.4">A 300 response is cacheable unless otherwise indicated by the method definition or explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). 2592 2592 </p> 2593 <div class="note" id="rfc.section.6.4.1.p.5"> 2594 <p> 2593 <div class="note" id="rfc.section.6.4.1.p.5"> 2594 <p><b>Note:</b> The original proposal for 300 defined the URI header field as providing a list of alternative representations, such that it 2595 2595 would be usable for 200, 300, and 406 responses and be transferred in responses to the HEAD method. However, lack of deployment 2596 2596 and disagreement over syntax led to both URI and Alternates (a subsequent proposal) being dropped from this specification. … … 2607 2607 with a hyperlink to the new URI(s). 2608 2608 </p> 2609 <div class="note" id="rfc.section.6.4.2.p.3"> 2610 <p> 2609 <div class="note" id="rfc.section.6.4.2.p.3"> 2610 <p><b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> can be used instead. 2611 2611 </p> 2612 2612 </div> … … 2621 2621 with a hyperlink to the different URI(s). 2622 2622 </p> 2623 <div class="note" id="rfc.section.6.4.3.p.3"> 2624 <p> 2623 <div class="note" id="rfc.section.6.4.3.p.3"> 2624 <p><b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> can be used instead. 2625 2625 </p> 2626 2626 </div> … … 2659 2659 with a hyperlink to the different URI(s). 2660 2660 </p> 2661 <div class="note" id="rfc.section.6.4.7.p.3"> 2662 <p> 2661 <div class="note" id="rfc.section.6.4.7.p.3"> 2662 <p><b>Note:</b> This status code is similar to <a href="#status.302" class="smpl">302 (Found)</a>, except that it does not allow changing the request method from POST to GET. This specification defines no equivalent counterpart 2663 2663 for <a href="#status.301" class="smpl">301 (Moved 2664 2664 Permanently)</a> (<a href="#status-308" id="rfc.xref.status-308.1"><cite title="The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)">[status-308]</cite></a>, however, defines the status code 308 (Permanent Redirect) for this purpose). … … 2687 2687 <p id="rfc.section.6.5.3.p.2">If authentication credentials were provided in the request, the server considers them insufficient to grant access. The client <em class="bcp14">SHOULD NOT</em> repeat the request with the same credentials. The client <em class="bcp14">MAY</em> repeat the request with new or different credentials. However, a request might be forbidden for reasons unrelated to the credentials. 2688 2688 </p> 2689 <p id="rfc.section.6.5.3.p.3">An origin server that wishes to "hide" the current existence of a forbidden <a href="#resources" class="smpl">target resource</a> 2689 <p id="rfc.section.6.5.3.p.3">An origin server that wishes to "hide" the current existence of a forbidden <a href="#resources" class="smpl">target resource</a> <em class="bcp14">MAY</em> instead respond with a status code of <a href="#status.404" class="smpl">404 (Not Found)</a>. 2690 2690 </p> 2691 2691 <div id="rfc.iref.76"></div> … … 2811 2811 which will likely be alleviated after some delay. The server <em class="bcp14">MAY</em> send a <a href="#header.retry-after" class="smpl">Retry-After</a> header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section 7.1.3</a>) to suggest an appropriate amount of time for the client to wait before retrying the request. 2812 2812 </p> 2813 <div class="note" id="rfc.section.6.6.4.p.2"> 2814 <p> 2813 <div class="note" id="rfc.section.6.6.4.p.2"> 2814 <p><b>Note:</b> The existence of the 503 status code does not imply that a server has to use it when becoming overloaded. Some servers might 2815 2815 simply refuse the connection. 2816 2816 </p> … … 2902 2902 </p> 2903 2903 <div id="preferred.date.format"> 2904 <p id="rfc.section.7.1.1.1.p.7"> 2904 <p id="rfc.section.7.1.1.1.p.7"> Preferred format:</p> 2905 2905 </div> 2906 2906 <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.40"></span><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><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span> <a href="#preferred.date.format" class="smpl">IMF-fixdate</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#imported.abnf" class="smpl">SP</a> date1 <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a> … … 2943 2943 <a href="#preferred.date.format" class="smpl">second</a> = 2<a href="#imported.abnf" class="smpl">DIGIT</a> 2944 2944 </pre><div id="obsolete.date.formats"> 2945 <p id="rfc.section.7.1.1.1.p.9"> 2945 <p id="rfc.section.7.1.1.1.p.9"> Obsolete formats:</p> 2946 2946 </div> 2947 2947 <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.52"></span> <a href="#obsolete.date.formats" class="smpl">obs-date</a> = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a> … … 2969 2969 date and time specifications defined by the Internet Message Format. 2970 2970 </p> 2971 <div class="note" id="rfc.section.7.1.1.1.p.16"> 2972 <p> 2971 <div class="note" id="rfc.section.7.1.1.1.p.16"> 2972 <p><b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Implementations are 2973 2973 not required to use these formats for user presentation, request logging, etc. 2974 2974 </p> … … 3023 3023 header field in a <a href="#status.201" class="smpl">201 (Created)</a> response is supposed to provide a URI that is specific to the created resource. 3024 3024 </p> 3025 <div class="note" id="rfc.section.7.1.2.p.9"> 3026 <p> 3025 <div class="note" id="rfc.section.7.1.2.p.9"> 3026 <p><b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate 3027 3027 or define such processing, but does allow it for the sake of robustness. 3028 3028 </p> 3029 3029 </div> 3030 <div class="note" id="rfc.section.7.1.2.p.10"> 3031 <p> 3030 <div class="note" id="rfc.section.7.1.2.p.10"> 3031 <p><b>Note:</b> The <a href="#header.content-location" class="smpl">Content-Location</a> header field (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section 3.1.4.2</a>) differs from Location in that the Content-Location refers to the most specific resource corresponding to the enclosed representation. 3032 3032 It is therefore possible for a response to contain both the Location and Content-Location header fields. 3033 3033 </p> … … 3041 3041 <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.57"></span> <a href="#header.retry-after" class="smpl">Retry-After</a> = <a href="#http.date" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> 3042 3042 </pre><div id="rule.delta-seconds"> 3043 <p id="rfc.section.7.1.3.p.4"> 3043 <p id="rfc.section.7.1.3.p.4"> Time spans are non-negative decimal integers, representing time in seconds.</p> 3044 3044 </div> 3045 3045 <div id="rfc.figure.u.55"></div><pre class="inline"><span id="rfc.iref.g.58"></span> <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> … … 3232 3232 response semantics (<a href="#Part5" id="rfc.xref.Part5.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>), it ought to document this too. 3233 3233 </p> 3234 <div class="note" id="rfc.section.8.1.2.p.4"> 3235 <p> 3234 <div class="note" id="rfc.section.8.1.2.p.4"> 3235 <p><b>Note:</b> Avoid defining a method name that starts with "M-", since that prefix might be misinterpreted as having the semantics assigned 3236 3236 to it by <a href="#RFC2774" id="rfc.xref.RFC2774.1"><cite title="An HTTP Extension Framework">[RFC2774]</cite></a>. 3237 3237 </p> … … 3255 3255 <td class="left">no</td> 3256 3256 <td class="left">no</td> 3257 <td class="left"> 3257 <td class="left"><a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section 4.3.6</a> 3258 3258 </td> 3259 3259 </tr> … … 3262 3262 <td class="left">no</td> 3263 3263 <td class="left">yes</td> 3264 <td class="left"> 3264 <td class="left"><a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section 4.3.5</a> 3265 3265 </td> 3266 3266 </tr> … … 3269 3269 <td class="left">yes</td> 3270 3270 <td class="left">yes</td> 3271 <td class="left"> 3271 <td class="left"><a href="#GET" id="rfc.xref.GET.4" title="GET">Section 4.3.1</a> 3272 3272 </td> 3273 3273 </tr> … … 3276 3276 <td class="left">yes</td> 3277 3277 <td class="left">yes</td> 3278 <td class="left"> 3278 <td class="left"><a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section 4.3.2</a> 3279 3279 </td> 3280 3280 </tr> … … 3283 3283 <td class="left">yes</td> 3284 3284 <td class="left">yes</td> 3285 <td class="left"> 3285 <td class="left"><a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section 4.3.7</a> 3286 3286 </td> 3287 3287 </tr> … … 3290 3290 <td class="left">no</td> 3291 3291 <td class="left">no</td> 3292 <td class="left"> 3292 <td class="left"><a href="#POST" id="rfc.xref.POST.3" title="POST">Section 4.3.3</a> 3293 3293 </td> 3294 3294 </tr> … … 3297 3297 <td class="left">no</td> 3298 3298 <td class="left">yes</td> 3299 <td class="left"> 3299 <td class="left"><a href="#PUT" id="rfc.xref.PUT.3" title="PUT">Section 4.3.4</a> 3300 3300 </td> 3301 3301 </tr> … … 3304 3304 <td class="left">yes</td> 3305 3305 <td class="left">yes</td> 3306 <td class="left"> 3306 <td class="left"><a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section 4.3.8</a> 3307 3307 </td> 3308 3308 </tr> … … 3367 3367 <td class="left">100</td> 3368 3368 <td class="left">Continue</td> 3369 <td class="left"> 3369 <td class="left"><a href="#status.100" id="rfc.xref.status.100.4" title="100 Continue">Section 6.2.1</a> 3370 3370 </td> 3371 3371 </tr> … … 3373 3373 <td class="left">101</td> 3374 3374 <td class="left">Switching Protocols</td> 3375 <td class="left"> 3375 <td class="left"><a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section 6.2.2</a> 3376 3376 </td> 3377 3377 </tr> … … 3379 3379 <td class="left">200</td> 3380 3380 <td class="left">OK</td> 3381 <td class="left"> 3381 <td class="left"><a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section 6.3.1</a> 3382 3382 </td> 3383 3383 </tr> … … 3385 3385 <td class="left">201</td> 3386 3386 <td class="left">Created</td> 3387 <td class="left"> 3387 <td class="left"><a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section 6.3.2</a> 3388 3388 </td> 3389 3389 </tr> … … 3391 3391 <td class="left">202</td> 3392 3392 <td class="left">Accepted</td> 3393 <td class="left"> 3393 <td class="left"><a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section 6.3.3</a> 3394 3394 </td> 3395 3395 </tr> … … 3397 3397 <td class="left">203</td> 3398 3398 <td class="left">Non-Authoritative Information</td> 3399 <td class="left"> 3399 <td class="left"><a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section 6.3.4</a> 3400 3400 </td> 3401 3401 </tr> … … 3403 3403 <td class="left">204</td> 3404 3404 <td class="left">No Content</td> 3405 <td class="left"> 3405 <td class="left"><a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section 6.3.5</a> 3406 3406 </td> 3407 3407 </tr> … … 3409 3409 <td class="left">205</td> 3410 3410 <td class="left">Reset Content</td> 3411 <td class="left"> 3411 <td class="left"><a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section 6.3.6</a> 3412 3412 </td> 3413 3413 </tr> … … 3415 3415 <td class="left">300</td> 3416 3416 <td class="left">Multiple Choices</td> 3417 <td class="left"> 3417 <td class="left"><a href="#status.300" id="rfc.xref.status.300.3" title="300 Multiple Choices">Section 6.4.1</a> 3418 3418 </td> 3419 3419 </tr> … … 3421 3421 <td class="left">301</td> 3422 3422 <td class="left">Moved Permanently</td> 3423 <td class="left"> 3423 <td class="left"><a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section 6.4.2</a> 3424 3424 </td> 3425 3425 </tr> … … 3427 3427 <td class="left">302</td> 3428 3428 <td class="left">Found</td> 3429 <td class="left"> 3429 <td class="left"><a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section 6.4.3</a> 3430 3430 </td> 3431 3431 </tr> … … 3433 3433 <td class="left">303</td> 3434 3434 <td class="left">See Other</td> 3435 <td class="left"> 3435 <td class="left"><a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section 6.4.4</a> 3436 3436 </td> 3437 3437 </tr> … … 3439 3439 <td class="left">305</td> 3440 3440 <td class="left">Use Proxy</td> 3441 <td class="left"> 3441 <td class="left"><a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section 6.4.5</a> 3442 3442 </td> 3443 3443 </tr> … … 3445 3445 <td class="left">306</td> 3446 3446 <td class="left">(Unused)</td> 3447 <td class="left"> 3447 <td class="left"><a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section 6.4.6</a> 3448 3448 </td> 3449 3449 </tr> … … 3451 3451 <td class="left">307</td> 3452 3452 <td class="left">Temporary Redirect</td> 3453 <td class="left"> 3453 <td class="left"><a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section 6.4.7</a> 3454 3454 </td> 3455 3455 </tr> … … 3457 3457 <td class="left">400</td> 3458 3458 <td class="left">Bad Request</td> 3459 <td class="left"> 3459 <td class="left"><a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section 6.5.1</a> 3460 3460 </td> 3461 3461 </tr> … … 3463 3463 <td class="left">402</td> 3464 3464 <td class="left">Payment Required</td> 3465 <td class="left"> 3465 <td class="left"><a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section 6.5.2</a> 3466 3466 </td> 3467 3467 </tr> … … 3469 3469 <td class="left">403</td> 3470 3470 <td class="left">Forbidden</td> 3471 <td class="left"> 3471 <td class="left"><a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section 6.5.3</a> 3472 3472 </td> 3473 3473 </tr> … … 3475 3475 <td class="left">404</td> 3476 3476 <td class="left">Not Found</td> 3477 <td class="left"> 3477 <td class="left"><a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section 6.5.4</a> 3478 3478 </td> 3479 3479 </tr> … … 3481 3481 <td class="left">405</td> 3482 3482 <td class="left">Method Not Allowed</td> 3483 <td class="left"> 3483 <td class="left"><a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section 6.5.5</a> 3484 3484 </td> 3485 3485 </tr> … … 3487 3487 <td class="left">406</td> 3488 3488 <td class="left">Not Acceptable</td> 3489 <td class="left"> 3489 <td class="left"><a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section 6.5.6</a> 3490 3490 </td> 3491 3491 </tr> … … 3493 3493 <td class="left">408</td> 3494 3494 <td class="left">Request Timeout</td> 3495 <td class="left"> 3495 <td class="left"><a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section 6.5.7</a> 3496 3496 </td> 3497 3497 </tr> … … 3499 3499 <td class="left">409</td> 3500 3500 <td class="left">Conflict</td> 3501 <td class="left"> 3501 <td class="left"><a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section 6.5.8</a> 3502 3502 </td> 3503 3503 </tr> … … 3505 3505 <td class="left">410</td> 3506 3506 <td class="left">Gone</td> 3507 <td class="left"> 3507 <td class="left"><a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section 6.5.9</a> 3508 3508 </td> 3509 3509 </tr> … … 3511 3511 <td class="left">411</td> 3512 3512 <td class="left">Length Required</td> 3513 <td class="left"> 3513 <td class="left"><a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section 6.5.10</a> 3514 3514 </td> 3515 3515 </tr> … … 3517 3517 <td class="left">413</td> 3518 3518 <td class="left">Payload Too Large</td> 3519 <td class="left"> 3519 <td class="left"><a href="#status.413" id="rfc.xref.status.413.2" title="413 Payload Too Large">Section 6.5.11</a> 3520 3520 </td> 3521 3521 </tr> … … 3523 3523 <td class="left">414</td> 3524 3524 <td class="left">URI Too Long</td> 3525 <td class="left"> 3525 <td class="left"><a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section 6.5.12</a> 3526 3526 </td> 3527 3527 </tr> … … 3529 3529 <td class="left">415</td> 3530 3530 <td class="left">Unsupported Media Type</td> 3531 <td class="left"> 3531 <td class="left"><a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section 6.5.13</a> 3532 3532 </td> 3533 3533 </tr> … … 3535 3535 <td class="left">417</td> 3536 3536 <td class="left">Expectation Failed</td> 3537 <td class="left"> 3537 <td class="left"><a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section 6.5.14</a> 3538 3538 </td> 3539 3539 </tr> … … 3541 3541 <td class="left">426</td> 3542 3542 <td class="left">Upgrade Required</td> 3543 <td class="left"> 3543 <td class="left"><a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section 6.5.15</a> 3544 3544 </td> 3545 3545 </tr> … … 3547 3547 <td class="left">500</td> 3548 3548 <td class="left">Internal Server Error</td> 3549 <td class="left"> 3549 <td class="left"><a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section 6.6.1</a> 3550 3550 </td> 3551 3551 </tr> … … 3553 3553 <td class="left">501</td> 3554 3554 <td class="left">Not Implemented</td> 3555 <td class="left"> 3555 <td class="left"><a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section 6.6.2</a> 3556 3556 </td> 3557 3557 </tr> … … 3559 3559 <td class="left">502</td> 3560 3560 <td class="left">Bad Gateway</td> 3561 <td class="left"> 3561 <td class="left"><a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section 6.6.3</a> 3562 3562 </td> 3563 3563 </tr> … … 3565 3565 <td class="left">503</td> 3566 3566 <td class="left">Service Unavailable</td> 3567 <td class="left"> 3567 <td class="left"><a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section 6.6.4</a> 3568 3568 </td> 3569 3569 </tr> … … 3571 3571 <td class="left">504</td> 3572 3572 <td class="left">Gateway Timeout</td> 3573 <td class="left"> 3573 <td class="left"><a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section 6.6.5</a> 3574 3574 </td> 3575 3575 </tr> … … 3577 3577 <td class="left">505</td> 3578 3578 <td class="left">HTTP Version Not Supported</td> 3579 <td class="left"> 3579 <td class="left"><a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section 6.6.6</a> 3580 3580 </td> 3581 3581 </tr> … … 3680 3680 <td class="left">http</td> 3681 3681 <td class="left">standard</td> 3682 <td class="left"> 3682 <td class="left"><a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section 5.3.2</a> 3683 3683 </td> 3684 3684 </tr> … … 3687 3687 <td class="left">http</td> 3688 3688 <td class="left">standard</td> 3689 <td class="left"> 3689 <td class="left"><a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section 5.3.3</a> 3690 3690 </td> 3691 3691 </tr> … … 3694 3694 <td class="left">http</td> 3695 3695 <td class="left">standard</td> 3696 <td class="left"> 3696 <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section 5.3.4</a> 3697 3697 </td> 3698 3698 </tr> … … 3701 3701 <td class="left">http</td> 3702 3702 <td class="left">standard</td> 3703 <td class="left"> 3703 <td class="left"><a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section 5.3.5</a> 3704 3704 </td> 3705 3705 </tr> … … 3708 3708 <td class="left">http</td> 3709 3709 <td class="left">standard</td> 3710 <td class="left"> 3710 <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section 7.4.1</a> 3711 3711 </td> 3712 3712 </tr> … … 3715 3715 <td class="left">http</td> 3716 3716 <td class="left">standard</td> 3717 <td class="left"> 3717 <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.3" title="Content-Encoding">Section 3.1.2.2</a> 3718 3718 </td> 3719 3719 </tr> … … 3722 3722 <td class="left">http</td> 3723 3723 <td class="left">standard</td> 3724 <td class="left"> 3724 <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.2" title="Content-Language">Section 3.1.3.2</a> 3725 3725 </td> 3726 3726 </tr> … … 3729 3729 <td class="left">http</td> 3730 3730 <td class="left">standard</td> 3731 <td class="left"> 3731 <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.4" title="Content-Location">Section 3.1.4.2</a> 3732 3732 </td> 3733 3733 </tr> … … 3736 3736 <td class="left">http</td> 3737 3737 <td class="left">standard</td> 3738 <td class="left"> 3738 <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.4" title="Content-Type">Section 3.1.1.5</a> 3739 3739 </td> 3740 3740 </tr> … … 3743 3743 <td class="left">http</td> 3744 3744 <td class="left">standard</td> 3745 <td class="left"> 3745 <td class="left"><a href="#header.date" id="rfc.xref.header.date.3" title="Date">Section 7.1.1.2</a> 3746 3746 </td> 3747 3747 </tr> … … 3750 3750 <td class="left">http</td> 3751 3751 <td class="left">standard</td> 3752 <td class="left"> 3752 <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section 5.1.1</a> 3753 3753 </td> 3754 3754 </tr> … … 3757 3757 <td class="left">http</td> 3758 3758 <td class="left">standard</td> 3759 <td class="left"> 3759 <td class="left"><a href="#header.from" id="rfc.xref.header.from.2" title="From">Section 5.5.1</a> 3760 3760 </td> 3761 3761 </tr> … … 3764 3764 <td class="left">http</td> 3765 3765 <td class="left">standard</td> 3766 <td class="left"> 3766 <td class="left"><a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section 7.1.2</a> 3767 3767 </td> 3768 3768 </tr> … … 3771 3771 <td class="left">http</td> 3772 3772 <td class="left">standard</td> 3773 <td class="left"> 3773 <td class="left"><a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix A.1</a> 3774 3774 </td> 3775 3775 </tr> … … 3778 3778 <td class="left">http</td> 3779 3779 <td class="left">standard</td> 3780 <td class="left"> 3780 <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section 5.1.2</a> 3781 3781 </td> 3782 3782 </tr> … … 3785 3785 <td class="left">http</td> 3786 3786 <td class="left">standard</td> 3787 <td class="left"> 3787 <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section 5.5.2</a> 3788 3788 </td> 3789 3789 </tr> … … 3792 3792 <td class="left">http</td> 3793 3793 <td class="left">standard</td> 3794 <td class="left"> 3794 <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section 7.1.3</a> 3795 3795 </td> 3796 3796 </tr> … … 3799 3799 <td class="left">http</td> 3800 3800 <td class="left">standard</td> 3801 <td class="left"> 3801 <td class="left"><a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section 7.4.2</a> 3802 3802 </td> 3803 3803 </tr> … … 3806 3806 <td class="left">http</td> 3807 3807 <td class="left">standard</td> 3808 <td class="left"> 3808 <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section 5.5.3</a> 3809 3809 </td> 3810 3810 </tr> … … 3813 3813 <td class="left">http</td> 3814 3814 <td class="left">standard</td> 3815 <td class="left"> 3815 <td class="left"><a href="#header.vary" id="rfc.xref.header.vary.4" title="Vary">Section 7.1.4</a> 3816 3816 </td> 3817 3817 </tr> … … 3851 3851 <td class="left">compress</td> 3852 3852 <td class="left">UNIX "compress" data format <a href="#Welch" id="rfc.xref.Welch.1"><cite title="A Technique for High Performance Data Compression">[Welch]</cite></a></td> 3853 <td class="left"> 3853 <td class="left"><a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> 3854 3854 </td> 3855 3855 </tr> … … 3858 3858 <td class="left">"deflate" compressed data (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>) 3859 3859 </td> 3860 <td class="left"> 3860 <td class="left"><a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> 3861 3861 </td> 3862 3862 </tr> … … 3864 3864 <td class="left">gzip</td> 3865 3865 <td class="left">GZIP file format <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td> 3866 <td class="left"> 3866 <td class="left"><a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> 3867 3867 </td> 3868 3868 </tr> … … 3871 3871 <td class="left">Reserved (synonym for "no encoding" in <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>) 3872 3872 </td> 3873 <td class="left"> 3873 <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.4" title="Accept-Encoding">Section 5.3.4</a> 3874 3874 </td> 3875 3875 </tr> … … 3877 3877 <td class="left">x-compress</td> 3878 3878 <td class="left">Deprecated (alias for compress)</td> 3879 <td class="left"> 3879 <td class="left"><a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> 3880 3880 </td> 3881 3881 </tr> … … 3883 3883 <td class="left">x-gzip</td> 3884 3884 <td class="left">Deprecated (alias for gzip)</td> 3885 <td class="left"> 3885 <td class="left"><a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.45"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> 3886 3886 </td> 3887 3887 </tr> … … 3979 3979 <tr> 3980 3980 <td class="reference"><b id="Part1">[Part1]</b></td> 3981 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), Ju ne 2013.3981 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), July 2013. 3982 3982 </td> 3983 3983 </tr> 3984 3984 <tr> 3985 3985 <td class="reference"><b id="Part4">[Part4]</b></td> 3986 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), Ju ne 2013.3986 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), July 2013. 3987 3987 </td> 3988 3988 </tr> 3989 3989 <tr> 3990 3990 <td class="reference"><b id="Part5">[Part5]</b></td> 3991 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), Ju ne 2013.3991 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), July 2013. 3992 3992 </td> 3993 3993 </tr> 3994 3994 <tr> 3995 3995 <td class="reference"><b id="Part6">[Part6]</b></td> 3996 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), Ju ne 2013.3996 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), July 2013. 3997 3997 </td> 3998 3998 </tr> 3999 3999 <tr> 4000 4000 <td class="reference"><b id="Part7">[Part7]</b></td> 4001 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), Ju ne 2013.4001 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), July 2013. 4002 4002 </td> 4003 4003 </tr> … … 4294 4294 information present): 204, 404, 405, 414, 501. 4295 4295 </p> 4296 <p id="rfc.section.B.p.24"> 4296 <p id="rfc.section.B.p.24"><a href="#header.allow" class="smpl">Allow</a> has been reclassified as a response header field, removing the option to specify it in a PUT request. Requirements relating 4297 4297 to the content of Allow have been relaxed; correspondingly, clients are not required to always trust its value (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section 7.4.1</a>). 4298 4298 </p> … … 4475 4475 <p id="rfc.section.E.2.p.1">Closed issues: </p> 4476 4476 <ul> 4477 <li> 4478 </li> 4479 <li> 4480 </li> 4481 <li> 4482 </li> 4483 <li> 4484 </li> 4485 <li> 4486 </li> 4487 <li> 4488 </li> 4489 <li> 4490 </li> 4491 <li> 4492 </li> 4493 <li> 4494 </li> 4495 <li> 4496 </li> 4497 <li> 4498 </li> 4499 <li> 4500 </li> 4501 <li> 4477 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/22">http://tools.ietf.org/wg/httpbis/trac/ticket/22</a>>: "ETag (and other metadata) in status messages" 4478 </li> 4479 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/96">http://tools.ietf.org/wg/httpbis/trac/ticket/96</a>>: "Conditional GET text" 4480 </li> 4481 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/146">http://tools.ietf.org/wg/httpbis/trac/ticket/146</a>>: "Clarify description of 405 (Not Allowed)" 4482 </li> 4483 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>>: "Allowing heuristic caching for new status codes" 4484 </li> 4485 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/315">http://tools.ietf.org/wg/httpbis/trac/ticket/315</a>>: "method semantics: retrieval/representation" 4486 </li> 4487 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/388">http://tools.ietf.org/wg/httpbis/trac/ticket/388</a>>: "User confirmation for unsafe methods" 4488 </li> 4489 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/404">http://tools.ietf.org/wg/httpbis/trac/ticket/404</a>>: "Tentative Status Codes" 4490 </li> 4491 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>>: "No-Transform" 4492 </li> 4493 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/419">http://tools.ietf.org/wg/httpbis/trac/ticket/419</a>>: "p2 editorial feedback" 4494 </li> 4495 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/424">http://tools.ietf.org/wg/httpbis/trac/ticket/424</a>>: "Absence of Accept-Encoding" 4496 </li> 4497 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/428">http://tools.ietf.org/wg/httpbis/trac/ticket/428</a>>: "Accept-Language ordering for identical qvalues" 4498 </li> 4499 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/432">http://tools.ietf.org/wg/httpbis/trac/ticket/432</a>>: "Identify additional status codes as cacheable by default" 4500 </li> 4501 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/434">http://tools.ietf.org/wg/httpbis/trac/ticket/434</a>>: "mention in header field considerations that leading/trailing WS is lossy" 4502 4502 </li> 4503 4503 </ul> … … 4505 4505 <p id="rfc.section.E.3.p.1">Closed issues: </p> 4506 4506 <ul> 4507 <li> 4508 </li> 4509 <li> 4510 </li> 4511 <li> 4512 </li> 4513 <li> 4514 </li> 4515 <li> 4516 </li> 4517 <li> 4518 </li> 4519 <li> 4507 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>>: "explain list expansion in ABNF appendices" 4508 </li> 4509 <li><<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/448">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/448</a>>: "Fallback for Accept-Language" 4510 </li> 4511 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/449">http://tools.ietf.org/wg/httpbis/trac/ticket/449</a>>: "Receiving a higher minor HTTP version number" 4512 </li> 4513 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/456">http://tools.ietf.org/wg/httpbis/trac/ticket/456</a>>: "Language-tag vs. language-range" 4514 </li> 4515 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/457">http://tools.ietf.org/wg/httpbis/trac/ticket/457</a>>: "Registering x-gzip and x-deflate" 4516 </li> 4517 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/459">http://tools.ietf.org/wg/httpbis/trac/ticket/459</a>>: "RFC2774 and method registrations" 4518 </li> 4519 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/488">http://tools.ietf.org/wg/httpbis/trac/ticket/488</a>>: "Selection based upon request target" 4520 4520 </li> 4521 4521 </ul> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2294 r2301 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 "Ju ne">15 <!ENTITY ID-MONTH "July"> 16 16 <!ENTITY ID-YEAR "2013"> 17 17 <!ENTITY mdash "—"> -
draft-ietf-httpbis/latest/p4-conditional.html
r2280 r2301 440 440 } 441 441 @top-right { 442 content: "Ju ne2013";442 content: "July 2013"; 443 443 } 444 444 @top-center { … … 449 449 } 450 450 @bottom-center { 451 content: "Expires December 5, 2013";451 content: "Expires January 2, 2014"; 452 452 } 453 453 @bottom-right { … … 486 486 <link href="p2-semantics.html" rel="prev"> 487 487 <link href="p5-range.html" rel="next"> 488 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.59 7, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">488 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 489 489 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 490 490 <meta name="dct.creator" content="Fielding, R."> 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2013-0 6-03">493 <meta name="dct.issued" scheme="ISO8601" content="2013-07-01"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 495 495 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false."> … … 517 517 </tr> 518 518 <tr> 519 <td class="left">Expires: December 5, 2013</td>520 <td class="right">Ju ne 3, 2013</td>519 <td class="left">Expires: January 2, 2014</td> 520 <td class="right">July 1, 2013</td> 521 521 </tr> 522 522 </tbody> … … 545 545 in progress”. 546 546 </p> 547 <p>This Internet-Draft will expire on December 5, 2013.</p>547 <p>This Internet-Draft will expire on January 2, 2014.</p> 548 548 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 549 549 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 783 783 <a href="#header.etag" class="smpl">etagc</a> = %x21 / %x23-7E / <a href="#imported.abnf" class="smpl">obs-text</a> 784 784 ; <a href="#imported.abnf" class="smpl">VCHAR</a> except double quotes, plus obs-text 785 </pre><div class="note" id="rfc.section.2.3.p.3"> 786 <p> 785 </pre><div class="note" id="rfc.section.2.3.p.3"> 786 <p><b>Note:</b> Previously, opaque-tag was defined to be a quoted-string (<a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-3.11">Section 3.11</a>), thus some recipients might perform backslash unescaping. Servers therefore ought to avoid backslash characters in entity 787 787 tags. 788 788 </p> … … 897 897 Content-Encoding: gzip 898 898 899 <em>...binary data...</em></pre><div class="note" id="rfc.section.2.3.3.p.7"> 900 <p> 899 <em>...binary data...</em></pre><div class="note" id="rfc.section.2.3.3.p.7"> 900 <p><b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation has to be distinct 901 901 from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings 902 902 (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) apply only during message transfer and do not require distinct entity-tags. … … 1023 1023 selected representation's <a href="#header.last-modified" class="smpl">Last-Modified</a> field will not be able to help the user agent limit its data transfers to only those changed during the specified window. 1024 1024 </p> 1025 <div class="note" id="rfc.section.3.3.p.9"> 1026 <p> 1025 <div class="note" id="rfc.section.3.3.p.9"> 1026 <p><b>Note:</b> If a client uses an arbitrary date in the If-Modified-Since header field instead of a date taken from a <a href="#header.last-modified" class="smpl">Last-Modified</a> or <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field from the origin server, the client ought to be aware that its date will be interpreted according to the server's 1027 1027 understanding of time. 1028 1028 </p> … … 1123 1123 <li id="precedence5">When the method is GET and both <a href="p5-range.html#header.range" class="smpl">Range</a> and <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> are present, evaluate If-Range: 1124 1124 <ul> 1125 <li>if the validator matches and the Range specification is applicable to the selected representation, respond <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> 1125 <li>if the validator matches and the Range specification is applicable to the selected representation, respond <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> <a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></li> 1126 1126 </ul> 1127 1127 </li> … … 1154 1154 <td class="left">304</td> 1155 1155 <td class="left">Not Modified</td> 1156 <td class="left"> 1156 <td class="left"><a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section 4.1</a> 1157 1157 </td> 1158 1158 </tr> … … 1160 1160 <td class="left">412</td> 1161 1161 <td class="left">Precondition Failed</td> 1162 <td class="left"> 1162 <td class="left"><a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section 4.2</a> 1163 1163 </td> 1164 1164 </tr> … … 1188 1188 <td class="left">http</td> 1189 1189 <td class="left">standard</td> 1190 <td class="left"> 1190 <td class="left"><a href="#header.etag" id="rfc.xref.header.etag.2" title="ETag">Section 2.3</a> 1191 1191 </td> 1192 1192 </tr> … … 1195 1195 <td class="left">http</td> 1196 1196 <td class="left">standard</td> 1197 <td class="left"> 1197 <td class="left"><a href="#header.if-match" id="rfc.xref.header.if-match.1" title="If-Match">Section 3.1</a> 1198 1198 </td> 1199 1199 </tr> … … 1202 1202 <td class="left">http</td> 1203 1203 <td class="left">standard</td> 1204 <td class="left"> 1204 <td class="left"><a href="#header.if-modified-since" id="rfc.xref.header.if-modified-since.1" title="If-Modified-Since">Section 3.3</a> 1205 1205 </td> 1206 1206 </tr> … … 1209 1209 <td class="left">http</td> 1210 1210 <td class="left">standard</td> 1211 <td class="left"> 1211 <td class="left"><a href="#header.if-none-match" id="rfc.xref.header.if-none-match.1" title="If-None-Match">Section 3.2</a> 1212 1212 </td> 1213 1213 </tr> … … 1216 1216 <td class="left">http</td> 1217 1217 <td class="left">standard</td> 1218 <td class="left"> 1218 <td class="left"><a href="#header.if-unmodified-since" id="rfc.xref.header.if-unmodified-since.1" title="If-Unmodified-Since">Section 3.4</a> 1219 1219 </td> 1220 1220 </tr> … … 1223 1223 <td class="left">http</td> 1224 1224 <td class="left">standard</td> 1225 <td class="left"> 1225 <td class="left"><a href="#header.last-modified" id="rfc.xref.header.last-modified.2" title="Last-Modified">Section 2.2</a> 1226 1226 </td> 1227 1227 </tr> … … 1256 1256 <tr> 1257 1257 <td class="reference"><b id="Part1">[Part1]</b></td> 1258 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), Ju ne 2013.1258 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), July 2013. 1259 1259 </td> 1260 1260 </tr> 1261 1261 <tr> 1262 1262 <td class="reference"><b id="Part2">[Part2]</b></td> 1263 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), Ju ne 2013.1263 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), July 2013. 1264 1264 </td> 1265 1265 </tr> 1266 1266 <tr> 1267 1267 <td class="reference"><b id="Part5">[Part5]</b></td> 1268 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), Ju ne 2013.1268 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), July 2013. 1269 1269 </td> 1270 1270 </tr> 1271 1271 <tr> 1272 1272 <td class="reference"><b id="Part6">[Part6]</b></td> 1273 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), Ju ne 2013.1273 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), July 2013. 1274 1274 </td> 1275 1275 </tr> … … 1368 1368 <p id="rfc.section.D.1.p.1">Closed issues: </p> 1369 1369 <ul> 1370 <li> 1371 </li> 1372 <li> 1373 </li> 1374 <li> 1375 </li> 1376 <li> 1377 </li> 1378 <li> 1379 </li> 1380 <li> 1381 </li> 1382 <li> 1383 </li> 1384 <li> 1385 </li> 1386 <li> 1370 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/241">http://tools.ietf.org/wg/httpbis/trac/ticket/241</a>>: "Need to clarify eval order/interaction of conditional headers" 1371 </li> 1372 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/345">http://tools.ietf.org/wg/httpbis/trac/ticket/345</a>>: "Required headers on 304 and 206" 1373 </li> 1374 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/350">http://tools.ietf.org/wg/httpbis/trac/ticket/350</a>>: "Optionality of Conditional Request Support" 1375 </li> 1376 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/354">http://tools.ietf.org/wg/httpbis/trac/ticket/354</a>>: "ETags and Conditional Requests" 1377 </li> 1378 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>>: "ABNF requirements for recipients" 1379 </li> 1380 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/363">http://tools.ietf.org/wg/httpbis/trac/ticket/363</a>>: "Rare cases" 1381 </li> 1382 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/365">http://tools.ietf.org/wg/httpbis/trac/ticket/365</a>>: "Conditional Request Security Considerations" 1383 </li> 1384 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/371">http://tools.ietf.org/wg/httpbis/trac/ticket/371</a>>: "If-Modified-Since lacks definition for method != GET" 1385 </li> 1386 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/372">http://tools.ietf.org/wg/httpbis/trac/ticket/372</a>>: "refactor conditional header field descriptions" 1387 1387 </li> 1388 1388 </ul> 1389 1389 <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a> <a id="changes.since.20" href="#changes.since.20">Since draft-ietf-httpbis-p4-conditional-20</a></h2> 1390 <p id="rfc.section.D.2.p.1"> 1390 <p id="rfc.section.D.2.p.1"></p> 1391 1391 <ul> 1392 1392 <li>Conformance criteria and considerations regarding error handling are now defined in Part 1.</li> … … 1395 1395 <p id="rfc.section.D.3.p.1">Closed issues: </p> 1396 1396 <ul> 1397 <li> 1398 </li> 1399 <li> 1400 </li> 1401 <li> 1402 </li> 1403 <li> 1404 </li> 1405 <li> 1406 </li> 1407 <li> 1408 </li> 1409 <li> 1397 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/96">http://tools.ietf.org/wg/httpbis/trac/ticket/96</a>>: "Conditional GET text" 1398 </li> 1399 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/350">http://tools.ietf.org/wg/httpbis/trac/ticket/350</a>>: "Optionality of Conditional Request Support" 1400 </li> 1401 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/384">http://tools.ietf.org/wg/httpbis/trac/ticket/384</a>>: "unclear prose in definition of 304" 1402 </li> 1403 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/401">http://tools.ietf.org/wg/httpbis/trac/ticket/401</a>>: "ETags and Conneg" 1404 </li> 1405 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/402">http://tools.ietf.org/wg/httpbis/trac/ticket/402</a>>: "Comparison function for If-Match and If-None-Match" 1406 </li> 1407 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/406">http://tools.ietf.org/wg/httpbis/trac/ticket/406</a>>: "304 without validator" 1408 </li> 1409 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/427">http://tools.ietf.org/wg/httpbis/trac/ticket/427</a>>: "If-Match and 428" 1410 1410 </li> 1411 1411 </ul> … … 1413 1413 <p id="rfc.section.D.4.p.1">Closed issues: </p> 1414 1414 <ul> 1415 <li> 1416 </li> 1417 <li> 1415 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>>: "explain list expansion in ABNF appendices" 1416 </li> 1417 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/437">http://tools.ietf.org/wg/httpbis/trac/ticket/437</a>>: "incorrect example dates" 1418 1418 </li> 1419 1419 </ul> 1420 1420 <p id="rfc.section.D.4.p.2">Partly resolved issues: </p> 1421 1421 <ul> 1422 <li> 1422 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/461">http://tools.ietf.org/wg/httpbis/trac/ticket/461</a>>: "Editorial suggestions" 1423 1423 </li> 1424 1424 </ul> -
draft-ietf-httpbis/latest/p4-conditional.xml
r2280 r2301 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 "Ju ne">15 <!ENTITY ID-MONTH "July"> 16 16 <!ENTITY ID-YEAR "2013"> 17 17 <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>"> -
draft-ietf-httpbis/latest/p5-range.html
r2299 r2301 440 440 } 441 441 @top-right { 442 content: "Ju ne2013";442 content: "July 2013"; 443 443 } 444 444 @top-center { … … 449 449 } 450 450 @bottom-center { 451 content: "Expires December 22, 2013";451 content: "Expires January 2, 2014"; 452 452 } 453 453 @bottom-right { … … 486 486 <link href="p4-conditional.html" rel="prev"> 487 487 <link href="p6-cache.html" rel="next"> 488 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.59 7, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">488 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 489 489 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 490 490 <meta name="dct.creator" content="Fielding, R."> … … 492 492 <meta name="dct.creator" content="Reschke, J. F."> 493 493 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 494 <meta name="dct.issued" scheme="ISO8601" content="2013-0 6-20">494 <meta name="dct.issued" scheme="ISO8601" content="2013-07-01"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 496 496 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests."> … … 518 518 </tr> 519 519 <tr> 520 <td class="left">Expires: December 22, 2013</td>520 <td class="left">Expires: January 2, 2014</td> 521 521 <td class="right">J. Reschke, Editor</td> 522 522 </tr> … … 527 527 <tr> 528 528 <td class="left"></td> 529 <td class="right">Ju ne 20, 2013</td>529 <td class="right">July 1, 2013</td> 530 530 </tr> 531 531 </tbody> … … 552 552 in progress”. 553 553 </p> 554 <p>This Internet-Draft will expire on December 22, 2013.</p>554 <p>This Internet-Draft will expire on January 2, 2014.</p> 555 555 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 556 556 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 662 662 <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span> <a href="#byte.ranges" class="smpl">bytes-unit</a> = "bytes" 663 663 </pre><div id="rule.ranges-specifier"> 664 <p id="rfc.section.2.1.p.3"> 664 <p id="rfc.section.2.1.p.3"> A byte range request can specify a single range of bytes, or a set of ranges within a single representation.</p> 665 665 </div> 666 666 <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#byte.ranges" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> … … 878 878 </pre><p id="rfc.section.4.2.p.7">and this second example illustrates when the complete length is unknown:</p> 879 879 <div id="rfc.figure.u.21"></div><pre class="text"> Content-Range: bytes 42-1233/* 880 </pre><p id="rfc.section.4.2.p.9">A Content-Range field value is invalid if it contains a <a href="#header.content-range" class="smpl">byte-range-resp</a> that has a <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value less than its <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> value, or a <a href="#header.content-range" class="smpl">complete-length</a> value less than or equal to its <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value. The recipient of an invalid <a href="#header.content-range" class="smpl">Content-Range</a> 880 </pre><p id="rfc.section.4.2.p.9">A Content-Range field value is invalid if it contains a <a href="#header.content-range" class="smpl">byte-range-resp</a> that has a <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value less than its <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> value, or a <a href="#header.content-range" class="smpl">complete-length</a> value less than or equal to its <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value. The recipient of an invalid <a href="#header.content-range" class="smpl">Content-Range</a> <em class="bcp14">MUST NOT</em> attempt to recombine the received content with a stored representation. 881 881 </p> 882 882 <p id="rfc.section.4.2.p.10">A server generating a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response to a byte range request <em class="bcp14">SHOULD</em> send a Content-Range header field with an <a href="#header.content-range" class="smpl">unsatisfied-range</a> value, as in the following example: … … 932 932 Date: Fri, 20 Jan 2012 15:41:54 GMT 933 933 Content-Range: bytes */47022 934 </pre><div class="note" id="rfc.section.4.4.p.4"> 935 <p> 934 </pre><div class="note" id="rfc.section.4.4.p.4"> 935 <p><b>Note:</b> Because servers are free to ignore <a href="#header.range" class="smpl">Range</a>, many implementations will simply respond with the entire selected representation in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. That is partly because most clients are prepared to receive a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> to complete the task (albeit less efficiently) and partly because clients might not stop making an invalid partial request 936 936 until they have received a complete representation. Thus, clients cannot depend on receiving a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response even when it is most appropriate. 937 937 </p> … … 996 996 <td class="left">206</td> 997 997 <td class="left">Partial Content</td> 998 <td class="left"> 998 <td class="left"><a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section 4.1</a> 999 999 </td> 1000 1000 </tr> … … 1002 1002 <td class="left">416</td> 1003 1003 <td class="left">Range Not Satisfiable</td> 1004 <td class="left"> 1004 <td class="left"><a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section 4.4</a> 1005 1005 </td> 1006 1006 </tr> … … 1030 1030 <td class="left">http</td> 1031 1031 <td class="left">standard</td> 1032 <td class="left"> 1032 <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.3" title="Accept-Ranges">Section 2.3</a> 1033 1033 </td> 1034 1034 </tr> … … 1037 1037 <td class="left">http</td> 1038 1038 <td class="left">standard</td> 1039 <td class="left"> 1039 <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section 4.2</a> 1040 1040 </td> 1041 1041 </tr> … … 1044 1044 <td class="left">http</td> 1045 1045 <td class="left">standard</td> 1046 <td class="left"> 1046 <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section 3.2</a> 1047 1047 </td> 1048 1048 </tr> … … 1051 1051 <td class="left">http</td> 1052 1052 <td class="left">standard</td> 1053 <td class="left"> 1053 <td class="left"><a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section 3.1</a> 1054 1054 </td> 1055 1055 </tr> … … 1079 1079 <tr> 1080 1080 <td class="reference"><b id="Part1">[Part1]</b></td> 1081 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), Ju ne 2013.1081 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), July 2013. 1082 1082 </td> 1083 1083 </tr> 1084 1084 <tr> 1085 1085 <td class="reference"><b id="Part2">[Part2]</b></td> 1086 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), Ju ne 2013.1086 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), July 2013. 1087 1087 </td> 1088 1088 </tr> 1089 1089 <tr> 1090 1090 <td class="reference"><b id="Part4">[Part4]</b></td> 1091 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), Ju ne 2013.1091 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), July 2013. 1092 1092 </td> 1093 1093 </tr> 1094 1094 <tr> 1095 1095 <td class="reference"><b id="Part6">[Part6]</b></td> 1096 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), Ju ne 2013.1096 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), July 2013. 1097 1097 </td> 1098 1098 </tr> … … 1156 1156 <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more body parts, each with its own <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-range" class="smpl">Content-Range</a> fields. The required boundary parameter specifies the boundary string used to separate each body part. 1157 1157 </p> 1158 <p id="rfc.section.A.p.3"> 1158 <p id="rfc.section.A.p.3"></p> 1159 1159 <dl> 1160 1160 <dt>Type name:</dt> … … 1178 1178 <dd>HTTP components supporting multiple ranges in a single request.</dd> 1179 1179 <dt>Additional information:</dt> 1180 <dd> 1180 <dd> 1181 1181 <dl> 1182 1182 <dt>Magic number(s):</dt> … … 1310 1310 <p id="rfc.section.E.1.p.1">Closed issues: </p> 1311 1311 <ul> 1312 <li> 1313 </li> 1314 <li> 1315 </li> 1316 <li> 1317 </li> 1318 <li> 1319 </li> 1320 <li> 1312 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/358">http://tools.ietf.org/wg/httpbis/trac/ticket/358</a>>: "ABNF list expansion code problem" 1313 </li> 1314 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>>: "ABNF requirements for recipients" 1315 </li> 1316 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/367">http://tools.ietf.org/wg/httpbis/trac/ticket/367</a>>: "reserve 'none' as byte range unit" 1317 </li> 1318 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>>: "note introduction of new IANA registries as normative changes" 1319 </li> 1320 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/369">http://tools.ietf.org/wg/httpbis/trac/ticket/369</a>>: "range units vs leading zeroes vs size" 1321 1321 </li> 1322 1322 </ul> 1323 1323 <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a> <a id="changes.since.20" href="#changes.since.20">Since draft-ietf-httpbis-p5-range-20</a></h2> 1324 <p id="rfc.section.E.2.p.1"> 1324 <p id="rfc.section.E.2.p.1"></p> 1325 1325 <ul> 1326 1326 <li>Conformance criteria and considerations regarding error handling are now defined in Part 1.</li> … … 1329 1329 <p id="rfc.section.E.3.p.1">Closed issues: </p> 1330 1330 <ul> 1331 <li> 1332 </li> 1333 <li> 1334 </li> 1335 <li> 1336 </li> 1337 <li> 1331 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/175">http://tools.ietf.org/wg/httpbis/trac/ticket/175</a>>: "Security consideration: range flooding" 1332 </li> 1333 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>>: "Allowing heuristic caching for new status codes" 1334 </li> 1335 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/311">http://tools.ietf.org/wg/httpbis/trac/ticket/311</a>>: "Add limitations to Range to reduce its use as a denial-of-service tool" 1336 </li> 1337 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/407">http://tools.ietf.org/wg/httpbis/trac/ticket/407</a>>: "416 and multipart/byteranges" 1338 1338 </li> 1339 1339 </ul> … … 1341 1341 <p id="rfc.section.E.4.p.1">Closed issues: </p> 1342 1342 <ul> 1343 <li> 1344 </li> 1345 <li> 1346 </li> 1347 <li> 1348 </li> 1349 <li> 1350 </li> 1351 <li> 1343 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>>: "explain list expansion in ABNF appendices" 1344 </li> 1345 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/437">http://tools.ietf.org/wg/httpbis/trac/ticket/437</a>>: "incorrect example dates" 1346 </li> 1347 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>>: "media type registration template issues" 1348 </li> 1349 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/462">http://tools.ietf.org/wg/httpbis/trac/ticket/462</a>>: "Editorial suggestions" 1350 </li> 1351 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/485">http://tools.ietf.org/wg/httpbis/trac/ticket/485</a>>: "MUSTs and other feedback" 1352 1352 </li> 1353 1353 </ul> -
draft-ietf-httpbis/latest/p5-range.xml
r2299 r2301 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 "Ju ne">15 <!ENTITY ID-MONTH "July"> 16 16 <!ENTITY ID-YEAR "2013"> 17 17 <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>"> -
draft-ietf-httpbis/latest/p6-cache.html
r2283 r2301 443 443 } 444 444 @top-right { 445 content: "Ju ne2013";445 content: "July 2013"; 446 446 } 447 447 @top-center { … … 452 452 } 453 453 @bottom-center { 454 content: "Expires December 6, 2013";454 content: "Expires January 2, 2014"; 455 455 } 456 456 @bottom-right { … … 492 492 <link href="p5-range.html" rel="prev"> 493 493 <link href="p7-auth.html" rel="next"> 494 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.59 7, 2013/05/27 06:39:42, XSLT vendor: SAXON 9.1.0.8from Saxonica http://www.saxonica.com/">494 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 495 495 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 496 496 <meta name="dct.creator" content="Fielding, R."> … … 498 498 <meta name="dct.creator" content="Reschke, J. F."> 499 499 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 500 <meta name="dct.issued" scheme="ISO8601" content="2013-0 6-04">500 <meta name="dct.issued" scheme="ISO8601" content="2013-07-01"> 501 501 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 502 502 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 524 524 </tr> 525 525 <tr> 526 <td class="left">Expires: December 6, 2013</td>526 <td class="left">Expires: January 2, 2014</td> 527 527 <td class="right">J. Reschke, Editor</td> 528 528 </tr> … … 533 533 <tr> 534 534 <td class="left"></td> 535 <td class="right">Ju ne 4, 2013</td>535 <td class="right">July 1, 2013</td> 536 536 </tr> 537 537 </tbody> … … 559 559 in progress”. 560 560 </p> 561 <p>This Internet-Draft will expire on December 6, 2013.</p>561 <p>This Internet-Draft will expire on January 2, 2014.</p> 562 562 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 563 563 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 886 886 </p> 887 887 <p id="rfc.section.4.1.p.11">When calculating freshness, to avoid common problems in date parsing:</p> 888 <p id="rfc.section.4.1.p.12"> 888 <p id="rfc.section.4.1.p.12"></p> 889 889 <ul> 890 890 <li>Although all date formats are specified to be case-sensitive, cache recipients <em class="bcp14">SHOULD</em> match day, week and timezone names case-insensitively. … … 932 932 present. 933 933 </p> 934 <div class="note" id="rfc.section.4.1.2.p.5"> 935 <p> <b>Note:</b><a href="http://tools.ietf.org/html/rfc2616#section-13.9">Section 13.9</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> prohibited caches from calculating heuristic freshness for URIs with query components (i.e., those containing '?'). In practice,934 <div class="note" id="rfc.section.4.1.2.p.5"> 935 <p><b>Note:</b> <a href="http://tools.ietf.org/html/rfc2616#section-13.9">Section 13.9</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> prohibited caches from calculating heuristic freshness for URIs with query components (i.e., those containing '?'). In practice, 936 936 this has not been widely implemented. Therefore, origin servers are encouraged to send explicit directives (e.g., Cache-Control: 937 937 no-cache) if they wish to preclude caching. … … 945 945 </p> 946 946 <p id="rfc.section.4.1.3.p.2">The following data is used for the age calculation:</p> 947 <p id="rfc.section.4.1.3.p.3"> <dfn>age_value</dfn>947 <p id="rfc.section.4.1.3.p.3"><dfn>age_value</dfn> 948 948 </p> 949 949 <ul class="empty"> … … 951 951 </li> 952 952 </ul> 953 <p id="rfc.section.4.1.3.p.4"> <dfn>date_value</dfn>953 <p id="rfc.section.4.1.3.p.4"><dfn>date_value</dfn> 954 954 </p> 955 955 <ul class="empty"> … … 957 957 </li> 958 958 </ul> 959 <p id="rfc.section.4.1.3.p.5"> <dfn>now</dfn>959 <p id="rfc.section.4.1.3.p.5"><dfn>now</dfn> 960 960 </p> 961 961 <ul class="empty"> … … 963 963 </li> 964 964 </ul> 965 <p id="rfc.section.4.1.3.p.6"> <dfn>request_time</dfn>965 <p id="rfc.section.4.1.3.p.6"><dfn>request_time</dfn> 966 966 </p> 967 967 <ul class="empty"> 968 968 <li>The current value of the clock at the host at the time the request resulting in the stored response was made.</li> 969 969 </ul> 970 <p id="rfc.section.4.1.3.p.7"> <dfn>response_time</dfn>970 <p id="rfc.section.4.1.3.p.7"><dfn>response_time</dfn> 971 971 </p> 972 972 <ul class="empty"> … … 1027 1027 </p> 1028 1028 <p id="rfc.section.4.2.p.5">Cache handling of a response to a conditional request is dependent upon its status code:</p> 1029 <p id="rfc.section.4.2.p.6"> 1029 <p id="rfc.section.4.2.p.6"></p> 1030 1030 <ul> 1031 1031 <li>A <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response status code indicates that the stored response can be updated and reused; see <a href="#freshening.responses" title="Freshening Stored Responses upon Validation">Section 4.2.1</a>. … … 1149 1149 <p id="rfc.section.7.2.p.2">A cache <em class="bcp14">MUST</em> obey the requirements of the Cache-Control directives defined in this section. See <a href="#cache.control.extensions" title="Cache Control Extensions">Section 7.2.3</a> for information about how Cache-Control directives defined elsewhere are handled. 1150 1150 </p> 1151 <div class="note" id="rfc.section.7.2.p.3"> 1152 <p> 1151 <div class="note" id="rfc.section.7.2.p.3"> 1152 <p><b>Note:</b> Some HTTP/1.0 caches might not implement Cache-Control. 1153 1153 </p> 1154 1154 </div> … … 1170 1170 <p id="rfc.section.7.2.1.1.p.1">Argument syntax: </p> 1171 1171 <ul class="empty"> 1172 <li> 1172 <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section 1.2.1</a>) 1173 1173 </li> 1174 1174 </ul> … … 1177 1177 stale response. 1178 1178 </p> 1179 <p id="rfc.section.7.2.1.1.p.3"> 1179 <p id="rfc.section.7.2.1.1.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form. 1180 1180 </p> 1181 1181 <div id="rfc.iref.m.2"></div> … … 1183 1183 <p id="rfc.section.7.2.1.2.p.1">Argument syntax: </p> 1184 1184 <ul class="empty"> 1185 <li> 1185 <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section 1.2.1</a>) 1186 1186 </li> 1187 1187 </ul> … … 1191 1191 to accept a stale response of any age. 1192 1192 </p> 1193 <p id="rfc.section.7.2.1.2.p.3"> 1193 <p id="rfc.section.7.2.1.2.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-stale=10', not 'max-stale="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form. 1194 1194 </p> 1195 1195 <div id="rfc.iref.m.3"></div> … … 1197 1197 <p id="rfc.section.7.2.1.3.p.1">Argument syntax: </p> 1198 1198 <ul class="empty"> 1199 <li> 1199 <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section 1.2.1</a>) 1200 1200 </li> 1201 1201 </ul> … … 1204 1204 for at least the specified number of seconds. 1205 1205 </p> 1206 <p id="rfc.section.7.2.1.3.p.3"> 1206 <p id="rfc.section.7.2.1.3.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'min-fresh=20', not 'min-fresh="20"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form. 1207 1207 </p> 1208 1208 <div id="rfc.iref.n.1"></div> … … 1257 1257 </p> 1258 1258 <p id="rfc.section.7.2.2.2.p.4">The field-names given are not limited to the set of header fields defined by this specification. Field names are case-insensitive.</p> 1259 <p id="rfc.section.7.2.2.2.p.5"> 1259 <p id="rfc.section.7.2.2.2.p.5"><b>Note:</b> Although it has been back-ported to many implementations, some HTTP/1.0 caches will not recognize or obey this directive. 1260 1260 Also, no-cache response directives with field-names are often handled by caches as if an unqualified no-cache directive was 1261 1261 received; i.e., the special handling for the qualified form is not widely implemented. 1262 1262 </p> 1263 <p id="rfc.section.7.2.2.2.p.6"> 1263 <p id="rfc.section.7.2.2.2.p.6"><b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists). 1264 1264 </p> 1265 1265 <div id="rfc.iref.n.5"></div> … … 1292 1292 </p> 1293 1293 <p id="rfc.section.7.2.2.6.p.4">The field-names given are not limited to the set of header fields defined by this specification. Field names are case-insensitive.</p> 1294 <p id="rfc.section.7.2.2.6.p.5"> 1294 <p id="rfc.section.7.2.2.6.p.5"><b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message 1295 1295 content. Also, private response directives with field-names are often handled by caches as if an unqualified private directive 1296 1296 was received; i.e., the special handling for the qualified form is not widely implemented. 1297 1297 </p> 1298 <p id="rfc.section.7.2.2.6.p.6"> 1298 <p id="rfc.section.7.2.2.6.p.6"><b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists). 1299 1299 </p> 1300 1300 <div id="rfc.iref.p.4"></div> … … 1307 1307 <p id="rfc.section.7.2.2.8.p.1">Argument syntax: </p> 1308 1308 <ul class="empty"> 1309 <li> 1309 <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section 1.2.1</a>) 1310 1310 </li> 1311 1311 </ul> … … 1313 1313 number of seconds. 1314 1314 </p> 1315 <p id="rfc.section.7.2.2.8.p.3"> 1315 <p id="rfc.section.7.2.2.8.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form. 1316 1316 </p> 1317 1317 <div id="rfc.iref.s.4"></div> … … 1319 1319 <p id="rfc.section.7.2.2.9.p.1">Argument syntax: </p> 1320 1320 <ul class="empty"> 1321 <li> 1321 <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section 1.2.1</a>) 1322 1322 </li> 1323 1323 </ul> … … 1325 1325 the maximum age specified by either the max-age directive or the <a href="#header.expires" class="smpl">Expires</a> header field. The s-maxage directive also implies the semantics of the proxy-revalidate response directive. 1326 1326 </p> 1327 <p id="rfc.section.7.2.2.9.p.3"> 1327 <p id="rfc.section.7.2.2.9.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 's-maxage=10', not 's-maxage="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form. 1328 1328 </p> 1329 1329 <h3 id="rfc.section.7.2.3"><a href="#rfc.section.7.2.3">7.2.3</a> <a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3> … … 1404 1404 understand <a href="#header.cache-control" class="smpl">Cache-Control</a> from serving a cached response. 1405 1405 </p> 1406 <div class="note" id="rfc.section.7.4.p.8"> 1407 <p> 1406 <div class="note" id="rfc.section.7.4.p.8"> 1407 <p><b>Note:</b> Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement for "Cache-Control: 1408 1408 no-cache" in them. 1409 1409 </p> … … 1483 1483 <div id="rfc.iref.50"></div> 1484 1484 <h3 id="rfc.section.7.5.6"><a href="#rfc.section.7.5.6">7.5.6</a> <a id="warn.214" href="#warn.214">214 Transformation Applied</a></h3> 1485 <p id="rfc.section.7.5.6.p.1"> 1485 <p id="rfc.section.7.5.6.p.1"><em class="bcp14">MUST</em> be added by a proxy if it applies any transformation to the representation, such as changing the content-coding, media-type, 1486 1486 or modifying the representation data, unless this Warning code already appears in the response. 1487 1487 </p> … … 1518 1518 <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a> <a id="cache.directive.considerations" href="#cache.directive.considerations">Considerations for New Cache Control Directives</a></h3> 1519 1519 <p id="rfc.section.9.1.2.p.1">New extension directives ought to consider defining:</p> 1520 <p id="rfc.section.9.1.2.p.2"> 1520 <p id="rfc.section.9.1.2.p.2"></p> 1521 1521 <ul> 1522 1522 <li>What it means for a directive to be specified multiple times,</li> … … 1541 1541 <tr> 1542 1542 <td class="left">max-age</td> 1543 <td class="left"> 1543 <td class="left"><a href="#cache-request-directive.max-age" title="max-age">Section 7.2.1.1</a>, <a href="#cache-response-directive.max-age" title="max-age">Section 7.2.2.8</a> 1544 1544 </td> 1545 1545 </tr> 1546 1546 <tr> 1547 1547 <td class="left">max-stale</td> 1548 <td class="left"> 1548 <td class="left"><a href="#cache-request-directive.max-stale" title="max-stale">Section 7.2.1.2</a> 1549 1549 </td> 1550 1550 </tr> 1551 1551 <tr> 1552 1552 <td class="left">min-fresh</td> 1553 <td class="left"> 1553 <td class="left"><a href="#cache-request-directive.min-fresh" title="min-fresh">Section 7.2.1.3</a> 1554 1554 </td> 1555 1555 </tr> 1556 1556 <tr> 1557 1557 <td class="left">must-revalidate</td> 1558 <td class="left"> 1558 <td class="left"><a href="#cache-response-directive.must-revalidate" title="must-revalidate">Section 7.2.2.1</a> 1559 1559 </td> 1560 1560 </tr> 1561 1561 <tr> 1562 1562 <td class="left">no-cache</td> 1563 <td class="left"> 1563 <td class="left"><a href="#cache-request-directive.no-cache" title="no-cache">Section 7.2.1.4</a>, <a href="#cache-response-directive.no-cache" title="no-cache">Section 7.2.2.2</a> 1564 1564 </td> 1565 1565 </tr> 1566 1566 <tr> 1567 1567 <td class="left">no-store</td> 1568 <td class="left"> 1568 <td class="left"><a href="#cache-request-directive.no-store" title="no-store">Section 7.2.1.5</a>, <a href="#cache-response-directive.no-store" title="no-store">Section 7.2.2.3</a> 1569 1569 </td> 1570 1570 </tr> 1571 1571 <tr> 1572 1572 <td class="left">no-transform</td> 1573 <td class="left"> 1573 <td class="left"><a href="#cache-request-directive.no-transform" title="no-transform">Section 7.2.1.6</a>, <a href="#cache-response-directive.no-transform" title="no-transform">Section 7.2.2.4</a> 1574 1574 </td> 1575 1575 </tr> 1576 1576 <tr> 1577 1577 <td class="left">only-if-cached</td> 1578 <td class="left"> 1578 <td class="left"><a href="#cache-request-directive.only-if-cached" title="only-if-cached">Section 7.2.1.7</a> 1579 1579 </td> 1580 1580 </tr> 1581 1581 <tr> 1582 1582 <td class="left">private</td> 1583 <td class="left"> 1583 <td class="left"><a href="#cache-response-directive.private" title="private">Section 7.2.2.6</a> 1584 1584 </td> 1585 1585 </tr> 1586 1586 <tr> 1587 1587 <td class="left">proxy-revalidate</td> 1588 <td class="left"> 1588 <td class="left"><a href="#cache-response-directive.proxy-revalidate" title="proxy-revalidate">Section 7.2.2.7</a> 1589 1589 </td> 1590 1590 </tr> 1591 1591 <tr> 1592 1592 <td class="left">public</td> 1593 <td class="left"> 1593 <td class="left"><a href="#cache-response-directive.public" title="public">Section 7.2.2.5</a> 1594 1594 </td> 1595 1595 </tr> 1596 1596 <tr> 1597 1597 <td class="left">s-maxage</td> 1598 <td class="left"> 1598 <td class="left"><a href="#cache-response-directive.s-maxage" title="s-maxage">Section 7.2.2.9</a> 1599 1599 </td> 1600 1600 </tr> 1601 1601 <tr> 1602 1602 <td class="left">stale-if-error</td> 1603 <td class="left"> 1603 <td class="left"><a href="#RFC5861" id="rfc.xref.RFC5861.1"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-4">Section 4</a> 1604 1604 </td> 1605 1605 </tr> 1606 1606 <tr> 1607 1607 <td class="left">stale-while-revalidate</td> 1608 <td class="left"> 1608 <td class="left"><a href="#RFC5861" id="rfc.xref.RFC5861.2"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-3">Section 3</a> 1609 1609 </td> 1610 1610 </tr> … … 1641 1641 <td class="left">110</td> 1642 1642 <td class="left">Response is Stale</td> 1643 <td class="left"> 1643 <td class="left"><a href="#warn.110" id="rfc.xref.warn.110.1" title="110 Response is Stale">Section 7.5.1</a> 1644 1644 </td> 1645 1645 </tr> … … 1647 1647 <td class="left">111</td> 1648 1648 <td class="left">Revalidation Failed</td> 1649 <td class="left"> 1649 <td class="left"><a href="#warn.111" id="rfc.xref.warn.111.1" title="111 Revalidation Failed">Section 7.5.2</a> 1650 1650 </td> 1651 1651 </tr> … … 1653 1653 <td class="left">112</td> 1654 1654 <td class="left">Disconnected Operation</td> 1655 <td class="left"> 1655 <td class="left"><a href="#warn.112" id="rfc.xref.warn.112.1" title="112 Disconnected Operation">Section 7.5.3</a> 1656 1656 </td> 1657 1657 </tr> … … 1659 1659 <td class="left">113</td> 1660 1660 <td class="left">Heuristic Expiration</td> 1661 <td class="left"> 1661 <td class="left"><a href="#warn.113" id="rfc.xref.warn.113.1" title="113 Heuristic Expiration">Section 7.5.4</a> 1662 1662 </td> 1663 1663 </tr> … … 1665 1665 <td class="left">199</td> 1666 1666 <td class="left">Miscellaneous Warning</td> 1667 <td class="left"> 1667 <td class="left"><a href="#warn.199" id="rfc.xref.warn.199.1" title="199 Miscellaneous Warning">Section 7.5.5</a> 1668 1668 </td> 1669 1669 </tr> … … 1671 1671 <td class="left">214</td> 1672 1672 <td class="left">Transformation Applied</td> 1673 <td class="left"> 1673 <td class="left"><a href="#warn.214" id="rfc.xref.warn.214.1" title="214 Transformation Applied">Section 7.5.6</a> 1674 1674 </td> 1675 1675 </tr> … … 1677 1677 <td class="left">299</td> 1678 1678 <td class="left">Miscellaneous Persistent Warning</td> 1679 <td class="left"> 1679 <td class="left"><a href="#warn.299" id="rfc.xref.warn.299.1" title="299 Miscellaneous Persistent Warning">Section 7.5.7</a> 1680 1680 </td> 1681 1681 </tr> … … 1705 1705 <td class="left">http</td> 1706 1706 <td class="left">standard</td> 1707 <td class="left"> 1707 <td class="left"><a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section 7.1</a> 1708 1708 </td> 1709 1709 </tr> … … 1712 1712 <td class="left">http</td> 1713 1713 <td class="left">standard</td> 1714 <td class="left"> 1714 <td class="left"><a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section 7.2</a> 1715 1715 </td> 1716 1716 </tr> … … 1719 1719 <td class="left">http</td> 1720 1720 <td class="left">standard</td> 1721 <td class="left"> 1721 <td class="left"><a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section 7.3</a> 1722 1722 </td> 1723 1723 </tr> … … 1726 1726 <td class="left">http</td> 1727 1727 <td class="left">standard</td> 1728 <td class="left"> 1728 <td class="left"><a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section 7.4</a> 1729 1729 </td> 1730 1730 </tr> … … 1733 1733 <td class="left">http</td> 1734 1734 <td class="left">standard</td> 1735 <td class="left"> 1735 <td class="left"><a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section 7.5</a> 1736 1736 </td> 1737 1737 </tr> … … 1773 1773 <tr> 1774 1774 <td class="reference"><b id="Part1">[Part1]</b></td> 1775 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), Ju ne 2013.1775 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), July 2013. 1776 1776 </td> 1777 1777 </tr> 1778 1778 <tr> 1779 1779 <td class="reference"><b id="Part2">[Part2]</b></td> 1780 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), Ju ne 2013.1780 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), July 2013. 1781 1781 </td> 1782 1782 </tr> 1783 1783 <tr> 1784 1784 <td class="reference"><b id="Part4">[Part4]</b></td> 1785 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), Ju ne 2013.1785 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), July 2013. 1786 1786 </td> 1787 1787 </tr> 1788 1788 <tr> 1789 1789 <td class="reference"><b id="Part5">[Part5]</b></td> 1790 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), Ju ne 2013.1790 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), July 2013. 1791 1791 </td> 1792 1792 </tr> 1793 1793 <tr> 1794 1794 <td class="reference"><b id="Part7">[Part7]</b></td> 1795 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), Ju ne 2013.1795 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), July 2013. 1796 1796 </td> 1797 1797 </tr> … … 1965 1965 <p id="rfc.section.D.1.p.1">Closed issues: </p> 1966 1966 <ul> 1967 <li> 1968 </li> 1969 <li> 1970 </li> 1971 <li> 1972 </li> 1973 <li> 1974 </li> 1975 <li> 1976 </li> 1977 <li> 1978 </li> 1979 <li> 1980 </li> 1981 <li> 1967 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/307">http://tools.ietf.org/wg/httpbis/trac/ticket/307</a>>: "untangle Cache-Control ABNF" 1968 </li> 1969 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/353">http://tools.ietf.org/wg/httpbis/trac/ticket/353</a>>: "Multiple values in Cache-Control header fields" 1970 </li> 1971 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/355">http://tools.ietf.org/wg/httpbis/trac/ticket/355</a>>: "Case sensitivity of header fields in CC values" 1972 </li> 1973 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/356">http://tools.ietf.org/wg/httpbis/trac/ticket/356</a>>: "Spurious 'MAYs'" 1974 </li> 1975 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/360">http://tools.ietf.org/wg/httpbis/trac/ticket/360</a>>: "enhance considerations for new cache control directives" 1976 </li> 1977 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>>: "ABNF requirements for recipients" 1978 </li> 1979 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>>: "note introduction of new IANA registries as normative changes" 1980 </li> 1981 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/373">http://tools.ietf.org/wg/httpbis/trac/ticket/373</a>>: "broken prose in description of 'Vary'" 1982 1982 </li> 1983 1983 </ul> … … 1985 1985 <p id="rfc.section.D.2.p.1">Closed issues: </p> 1986 1986 <ul> 1987 <li> 1987 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/375">http://tools.ietf.org/wg/httpbis/trac/ticket/375</a>>: "'Most Conservative'" 1988 1988 </li> 1989 1989 </ul> … … 1997 1997 <p id="rfc.section.D.3.p.1">Closed issues: </p> 1998 1998 <ul> 1999 <li> 2000 </li> 2001 <li> 2002 </li> 2003 <li> 2004 </li> 2005 <li> 1999 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>>: "Allowing heuristic caching for new status codes" 2000 </li> 2001 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/406">http://tools.ietf.org/wg/httpbis/trac/ticket/406</a>>: "304 without validator" 2002 </li> 2003 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>>: "No-Transform" 2004 </li> 2005 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/430">http://tools.ietf.org/wg/httpbis/trac/ticket/430</a>>: "Revert prior change to the meaning of the public cache response directive. 2006 2006 </li> 2007 2007 </ul> … … 2009 2009 <p id="rfc.section.D.4.p.1">Closed issues: </p> 2010 2010 <ul> 2011 <li> 2012 </li> 2013 <li> 2014 </li> 2015 <li> 2016 </li> 2017 <li> 2018 </li> 2019 <li> 2011 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>>: "explain list expansion in ABNF appendices" 2012 </li> 2013 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/453">http://tools.ietf.org/wg/httpbis/trac/ticket/453</a>>: "Returning the freshest response" 2014 </li> 2015 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/464">http://tools.ietf.org/wg/httpbis/trac/ticket/464</a>>: "placement of extension point considerations" 2016 </li> 2017 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/469">http://tools.ietf.org/wg/httpbis/trac/ticket/469</a>>: "Editorial notes for p6" 2018 </li> 2019 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/471">http://tools.ietf.org/wg/httpbis/trac/ticket/471</a>>: "Vary and future requests" 2020 2020 </li> 2021 2021 </ul> -
draft-ietf-httpbis/latest/p6-cache.xml
r2283 r2301 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 "Ju ne">15 <!ENTITY ID-MONTH "July"> 16 16 <!ENTITY ID-YEAR "2013"> 17 17 <!ENTITY mdash "—"> -
draft-ietf-httpbis/latest/p7-auth.html
r2289 r2301 440 440 } 441 441 @top-right { 442 content: "Ju ne2013";442 content: "July 2013"; 443 443 } 444 444 @top-center { … … 449 449 } 450 450 @bottom-center { 451 content: "Expires December 11, 2013";451 content: "Expires January 2, 2014"; 452 452 } 453 453 @bottom-right { … … 484 484 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 485 485 <link href="p6-cache.html" rel="prev"> 486 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.59 7, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">486 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 487 487 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 488 488 <meta name="dct.creator" content="Fielding, R."> 489 489 <meta name="dct.creator" content="Reschke, J. F."> 490 490 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 491 <meta name="dct.issued" scheme="ISO8601" content="2013-0 6-09">491 <meta name="dct.issued" scheme="ISO8601" content="2013-07-01"> 492 492 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 493 493 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework."> … … 517 517 <tr> 518 518 <td class="left">Intended status: Standards Track</td> 519 <td class="right">Ju ne 9, 2013</td>519 <td class="right">July 1, 2013</td> 520 520 </tr> 521 521 <tr> 522 <td class="left">Expires: December 11, 2013</td>522 <td class="left">Expires: January 2, 2014</td> 523 523 <td class="right"></td> 524 524 </tr> … … 546 546 in progress”. 547 547 </p> 548 <p>This Internet-Draft will expire on December 11, 2013.</p>548 <p>This Internet-Draft will expire on January 2, 2014.</p> 549 549 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 550 550 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 659 659 </p> 660 660 <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span> <a href="#challenge.and.response" class="smpl">challenge</a> = <a href="#challenge.and.response" class="smpl">auth-scheme</a> [ 1*<a href="#imported.abnf" class="smpl">SP</a> ( <a href="#challenge.and.response" class="smpl">token68</a> / #<a href="#challenge.and.response" class="smpl">auth-param</a> ) ] 661 </pre><div class="note" id="rfc.section.2.1.p.8"> 662 <p> 661 </pre><div class="note" id="rfc.section.2.1.p.8"> 662 <p><b>Note:</b> User agents will need to take special care in parsing the <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> and <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> header field values because they can contain more than one challenge, or if more than one of each is provided, since the contents 663 663 of a challenge can itself contain a comma-separated list of authentication parameters. 664 664 </p> 665 665 </div> 666 <div class="note" id="rfc.section.2.1.p.9"> 667 <p> 666 <div class="note" id="rfc.section.2.1.p.9"> 667 <p><b>Note:</b> Many clients fail to parse challenges containing unknown schemes. A workaround for this problem is to list well-supported 668 668 schemes (such as "basic") first. 669 669 </p> … … 779 779 "type" and "title", and another one for the "Basic" scheme with a realm value of "simple". 780 780 </p> 781 <div class="note" id="rfc.section.4.4.p.6"> 782 <p> 781 <div class="note" id="rfc.section.4.4.p.6"> 782 <p><b>Note:</b> The challenge grammar production uses the list syntax as well. Therefore, a sequence of comma, whitespace, and comma can be 783 783 considered both as applying to the preceding challenge, or to be an empty entry in the list of challenges. In practice, this 784 784 ambiguity does not affect the semantics of the header field value and thus is harmless. … … 804 804 work: 805 805 </p> 806 <p id="rfc.section.5.1.2.p.2"> 806 <p id="rfc.section.5.1.2.p.2"></p> 807 807 <ul> 808 808 <li> … … 828 828 can use a generic parser that applies to all authentication schemes. 829 829 </p> 830 <p> 830 <p><b>Note:</b> The fact that the value syntax for the "realm" parameter is restricted to quoted-string was a bad design choice not to be 831 831 repeated for new parameters. 832 832 </p> … … 869 869 <td class="left">401</td> 870 870 <td class="left">Unauthorized</td> 871 <td class="left"> 871 <td class="left"><a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section 3.1</a> 872 872 </td> 873 873 </tr> … … 875 875 <td class="left">407</td> 876 876 <td class="left">Proxy Authentication Required</td> 877 <td class="left"> 877 <td class="left"><a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section 3.2</a> 878 878 </td> 879 879 </tr> … … 903 903 <td class="left">http</td> 904 904 <td class="left">standard</td> 905 <td class="left"> 905 <td class="left"><a href="#header.authorization" id="rfc.xref.header.authorization.3" title="Authorization">Section 4.1</a> 906 906 </td> 907 907 </tr> … … 910 910 <td class="left">http</td> 911 911 <td class="left">standard</td> 912 <td class="left"> 912 <td class="left"><a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.2" title="Proxy-Authenticate">Section 4.2</a> 913 913 </td> 914 914 </tr> … … 917 917 <td class="left">http</td> 918 918 <td class="left">standard</td> 919 <td class="left"> 919 <td class="left"><a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.2" title="Proxy-Authorization">Section 4.3</a> 920 920 </td> 921 921 </tr> … … 924 924 <td class="left">http</td> 925 925 <td class="left">standard</td> 926 <td class="left"> 926 <td class="left"><a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.3" title="WWW-Authenticate">Section 4.4</a> 927 927 </td> 928 928 </tr> … … 978 978 <tr> 979 979 <td class="reference"><b id="Part1">[Part1]</b></td> 980 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), Ju ne 2013.980 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), July 2013. 981 981 </td> 982 982 </tr> 983 983 <tr> 984 984 <td class="reference"><b id="Part2">[Part2]</b></td> 985 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), Ju ne 2013.985 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), July 2013. 986 986 </td> 987 987 </tr> 988 988 <tr> 989 989 <td class="reference"><b id="Part6">[Part6]</b></td> 990 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), Ju ne 2013.990 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), July 2013. 991 991 </td> 992 992 </tr> … … 1102 1102 <p id="rfc.section.D.1.p.1">Closed issues: </p> 1103 1103 <ul> 1104 <li> 1105 </li> 1106 <li> 1107 </li> 1108 <li> 1109 </li> 1110 <li> 1111 </li> 1112 <li> 1104 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/348">http://tools.ietf.org/wg/httpbis/trac/ticket/348</a>>: "Realms and scope" 1105 </li> 1106 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/349">http://tools.ietf.org/wg/httpbis/trac/ticket/349</a>>: "Strength" 1107 </li> 1108 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/357">http://tools.ietf.org/wg/httpbis/trac/ticket/357</a>>: "Authentication exchanges" 1109 </li> 1110 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>>: "ABNF requirements for recipients" 1111 </li> 1112 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>>: "note introduction of new IANA registries as normative changes" 1113 1113 </li> 1114 1114 </ul> … … 1116 1116 <p id="rfc.section.D.2.p.1">Closed issues: </p> 1117 1117 <ul> 1118 <li> 1118 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/376">http://tools.ietf.org/wg/httpbis/trac/ticket/376</a>>: "rename b64token for clarity" 1119 1119 </li> 1120 1120 </ul> … … 1126 1126 <p id="rfc.section.D.3.p.1">Closed issues: </p> 1127 1127 <ul> 1128 <li> 1128 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/403">http://tools.ietf.org/wg/httpbis/trac/ticket/403</a>>: "Authentication and caching - max-age" 1129 1129 </li> 1130 1130 </ul> … … 1132 1132 <p id="rfc.section.D.4.p.1">Closed issues: </p> 1133 1133 <ul> 1134 <li> 1135 </li> 1136 <li> 1137 </li> 1138 <li> 1139 </li> 1140 <li> 1134 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>>: "explain list expansion in ABNF appendices" 1135 </li> 1136 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/439">http://tools.ietf.org/wg/httpbis/trac/ticket/439</a>>: "terminology: mechanism vs framework vs scheme" 1137 </li> 1138 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/463">http://tools.ietf.org/wg/httpbis/trac/ticket/463</a>>: "Editorial suggestions" 1139 </li> 1140 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/464">http://tools.ietf.org/wg/httpbis/trac/ticket/464</a>>: "placement of extension point considerations" 1141 1141 </li> 1142 1142 </ul> -
draft-ietf-httpbis/latest/p7-auth.xml
r2289 r2301 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 "Ju ne">15 <!ENTITY ID-MONTH "July"> 16 16 <!ENTITY ID-YEAR "2013"> 17 17 <!ENTITY mdash "—">
Note: See TracChangeset
for help on using the changeset viewer.