Changeset 1764
- Timestamp:
- 13/07/12 10:21:00 (10 years ago)
- Files:
-
- 16 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis-authscheme-registrations/latest/draft-ietf-httpbis-authscheme-registrations.html
r1699 r1764 422 422 } 423 423 @bottom-center { 424 content: "Expires January 3, 2013";424 content: "Expires January 14, 2013"; 425 425 } 426 426 @bottom-right { … … 453 453 <meta name="dct.creator" content="Reschke, J. F."> 454 454 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-authscheme-registrations-latest"> 455 <meta name="dct.issued" scheme="ISO8601" content="2012-07- 02">455 <meta name="dct.issued" scheme="ISO8601" content="2012-07-13"> 456 456 <meta name="dct.abstract" content="This document registers Hypertext Transfer Protocol (HTTP) authentication schemes which have been defined in standards-track RFCs before the IANA HTTP Authentication Scheme Registry was established."> 457 457 <meta name="description" content="This document registers Hypertext Transfer Protocol (HTTP) authentication schemes which have been defined in standards-track RFCs before the IANA HTTP Authentication Scheme Registry was established."> … … 470 470 <tr> 471 471 <td class="left">Intended status: Informational</td> 472 <td class="right">July 2, 2012</td>472 <td class="right">July 13, 2012</td> 473 473 </tr> 474 474 <tr> 475 <td class="left">Expires: January 3, 2013</td>475 <td class="left">Expires: January 14, 2013</td> 476 476 <td class="right"></td> 477 477 </tr> … … 484 484 </p> 485 485 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 486 <p>Discussion of this draft ought to take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived 487 at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 486 <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 488 487 </p> 489 488 <p>The current issues list is at <<a href="http://trac.tools.ietf.org/wg/httpbis/trac/query?component=authscheme-registrations">http://trac.tools.ietf.org/wg/httpbis/trac/query?component=authscheme-registrations</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. … … 500 499 in progress”. 501 500 </p> 502 <p>This Internet-Draft will expire on January 3, 2013.</p>501 <p>This Internet-Draft will expire on January 14, 2013.</p> 503 502 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 504 503 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis-authscheme-registrations/latest/draft-ietf-httpbis-authscheme-registrations.xml
r1699 r1764 55 55 <note title="Editorial Note (To be removed by RFC Editor)"> 56 56 <t> 57 Discussion of this draft ought to takeplace on the HTTPBIS working group57 Discussion of this draft takes place on the HTTPBIS working group 58 58 mailing list (ietf-http-wg@w3.org), which is archived at 59 59 <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>. -
draft-ietf-httpbis-method-registrations/latest/draft-ietf-httpbis-method-registrations.html
r1729 r1764 422 422 } 423 423 @bottom-center { 424 content: "Expires January 6, 2013";424 content: "Expires January 14, 2013"; 425 425 } 426 426 @bottom-right { … … 453 453 <meta name="dct.creator" content="Reschke, J. F."> 454 454 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-method-registrations-latest"> 455 <meta name="dct.issued" scheme="ISO8601" content="2012-07- 05">455 <meta name="dct.issued" scheme="ISO8601" content="2012-07-13"> 456 456 <meta name="dct.abstract" content="This document registers those Hypertext Transfer Protocol (HTTP) methods which have been defined in standards-track RFCs before the IANA HTTP Method Registry was established."> 457 457 <meta name="description" content="This document registers those Hypertext Transfer Protocol (HTTP) methods which have been defined in standards-track RFCs before the IANA HTTP Method Registry was established."> … … 470 470 <tr> 471 471 <td class="left">Intended status: Informational</td> 472 <td class="right">July 5, 2012</td>472 <td class="right">July 13, 2012</td> 473 473 </tr> 474 474 <tr> 475 <td class="left">Expires: January 6, 2013</td>475 <td class="left">Expires: January 14, 2013</td> 476 476 <td class="right"></td> 477 477 </tr> … … 484 484 </p> 485 485 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 486 <p>Discussion of this draft ought to take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived 487 at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 486 <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 488 487 </p> 489 488 <p>The current issues list is at <<a href="http://trac.tools.ietf.org/wg/httpbis/trac/query?component=method-registrations">http://trac.tools.ietf.org/wg/httpbis/trac/query?component=method-registrations</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. … … 500 499 in progress”. 501 500 </p> 502 <p>This Internet-Draft will expire on January 6, 2013.</p>501 <p>This Internet-Draft will expire on January 14, 2013.</p> 503 502 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 504 503 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis-method-registrations/latest/draft-ietf-httpbis-method-registrations.xml
r1729 r1764 55 55 <note title="Editorial Note (To be removed by RFC Editor)"> 56 56 <t> 57 Discussion of this draft ought to takeplace on the HTTPBIS working group57 Discussion of this draft takes place on the HTTPBIS working group 58 58 mailing list (ietf-http-wg@w3.org), which is archived at 59 59 <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>. -
draft-ietf-httpbis/latest/p0-introduction.html
r1756 r1764 393 393 } 394 394 @bottom-center { 395 content: "Expires January 1 1, 2013";395 content: "Expires January 14, 2013"; 396 396 } 397 397 @bottom-right { … … 426 426 <meta name="dct.creator" content="Reschke, J. F."> 427 427 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p0-introduction-latest"> 428 <meta name="dct.issued" scheme="ISO8601" content="2012-07-1 0">428 <meta name="dct.issued" scheme="ISO8601" content="2012-07-13"> 429 429 <meta name="dct.abstract" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1."> 430 430 <meta name="description" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1."> … … 446 446 </tr> 447 447 <tr> 448 <td class="left">Expires: January 1 1, 2013</td>448 <td class="left">Expires: January 14, 2013</td> 449 449 <td class="right">W3C</td> 450 450 </tr> … … 467 467 <tr> 468 468 <td class="left"></td> 469 <td class="right">July 1 0, 2012</td>469 <td class="right">July 13, 2012</td> 470 470 </tr> 471 471 </tbody> … … 477 477 </p> 478 478 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 479 <p>Discussion of this draft ought to take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived 480 at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 479 <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 481 480 </p> 482 481 <p>The current issues list is at <<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. … … 491 490 in progress”. 492 491 </p> 493 <p>This Internet-Draft will expire on January 1 1, 2013.</p>492 <p>This Internet-Draft will expire on January 14, 2013.</p> 494 493 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 495 494 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p0-introduction.xml
r1726 r1764 105 105 <note title="Editorial Note (To be removed by RFC Editor)"> 106 106 <t> 107 Discussion of this draft ought to takeplace on the HTTPBIS working group107 Discussion of this draft takes place on the HTTPBIS working group 108 108 mailing list (ietf-http-wg@w3.org), which is archived at 109 109 <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>. -
draft-ietf-httpbis/latest/p2-semantics.html
r1760 r1764 449 449 } 450 450 @bottom-center { 451 content: "Expires January 1 2, 2013";451 content: "Expires January 14, 2013"; 452 452 } 453 453 @bottom-right { … … 497 497 <meta name="dct.creator" content="Reschke, J. F."> 498 498 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 499 <meta name="dct.issued" scheme="ISO8601" content="2012-07-1 1">499 <meta name="dct.issued" scheme="ISO8601" content="2012-07-13"> 500 500 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 501 501 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation."> … … 528 528 </tr> 529 529 <tr> 530 <td class="left">Expires: January 1 2, 2013</td>530 <td class="left">Expires: January 14, 2013</td> 531 531 <td class="right">greenbytes</td> 532 532 </tr> 533 533 <tr> 534 534 <td class="left"></td> 535 <td class="right">July 1 1, 2012</td>535 <td class="right">July 13, 2012</td> 536 536 </tr> 537 537 </tbody> … … 547 547 </p> 548 548 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 549 <p>Discussion of this draft ought to take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived 550 at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 549 <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 551 550 </p> 552 551 <p>The current issues list is at <<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. … … 563 562 in progress”. 564 563 </p> 565 <p>This Internet-Draft will expire on January 1 2, 2013.</p>564 <p>This Internet-Draft will expire on January 14, 2013.</p> 566 565 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 567 566 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 880 879 </pre><h3 id="rfc.section.1.3.2"><a href="#rfc.section.1.3.2">1.3.2</a> <a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3> 881 880 <p id="rfc.section.1.3.2.p.1">The ABNF rules below are defined in other parts:</p> 882 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2. 7</a>>881 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>> 883 882 <a href="#abnf.dependencies" class="smpl">comment</a> = <comment, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>> 884 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2. 7</a>>883 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>> 885 884 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a>> 886 <a href="#abnf.dependencies" class="smpl">URI-reference</a> = <URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2. 7</a>>885 <a href="#abnf.dependencies" class="smpl">URI-reference</a> = <URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>> 887 886 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="methods" href="#methods">Methods</a></h1> 888 887 <p id="rfc.section.2.p.1">The method token indicates the request method to be performed on the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The method is case-sensitive. … … 1729 1728 <div id="rfc.iref.s.10"></div> 1730 1729 <h3 id="rfc.section.4.4.4"><a href="#rfc.section.4.4.4">4.4.4</a> <a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3> 1731 <p id="rfc.section.4.4.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2. 3</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).1730 <p id="rfc.section.4.4.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.4</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1732 1731 </p> 1733 1732 <p id="rfc.section.4.4.4.p.2">This status code is only appropriate when the response status code would have been <a href="#status.200" class="smpl">200 (OK)</a> otherwise. When the status code before transformation would have been different, the 214 Transformation Applied warn-code … … 2088 2087 <p id="rfc.section.4.7.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server 2089 2088 is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described 2090 in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2. 6</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain a representation describing why that version is not supported and what other protocols are supported by that server.2089 in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.7</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain a representation describing why that version is not supported and what other protocols are supported by that server. 2091 2090 </p> 2092 2091 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1> … … 4954 4953 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.3">1.3</a></li> 4955 4954 <li><em>Section 2</em> <a href="#rfc.xref.Part1.2">1.2</a></li> 4956 <li><em>Section 2. 3</em> <a href="#rfc.xref.Part1.34">4.4.4</a></li>4957 <li><em>Section 2. 6</em> <a href="#rfc.xref.Part1.37">4.7.6</a></li>4958 <li><em>Section 2. 7</em> <a href="#rfc.xref.Part1.12">1.3.2</a>, <a href="#rfc.xref.Part1.14">1.3.2</a>, <a href="#rfc.xref.Part1.16">1.3.2</a></li>4955 <li><em>Section 2.4</em> <a href="#rfc.xref.Part1.34">4.4.4</a></li> 4956 <li><em>Section 2.7</em> <a href="#rfc.xref.Part1.37">4.7.6</a></li> 4957 <li><em>Section 2.8</em> <a href="#rfc.xref.Part1.12">1.3.2</a>, <a href="#rfc.xref.Part1.14">1.3.2</a>, <a href="#rfc.xref.Part1.16">1.3.2</a></li> 4959 4958 <li><em>Section 3.2.1</em> <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.1</a>, <a href="#rfc.xref.Part1.7">1.3.1</a></li> 4960 4959 <li><em>Section 3.2</em> <a href="#rfc.xref.Part1.23">3</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.52">9.17</a>, <a href="#rfc.xref.Part1.54">9.18</a></li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1760 r1764 201 201 <note title="Editorial Note (To be removed by RFC Editor)"> 202 202 <t> 203 Discussion of this draft ought to takeplace on the HTTPBIS working group203 Discussion of this draft takes place on the HTTPBIS working group 204 204 mailing list (ietf-http-wg@w3.org), which is archived at 205 205 <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>. -
draft-ietf-httpbis/latest/p4-conditional.html
r1761 r1764 449 449 } 450 450 @bottom-center { 451 content: "Expires January 1 3, 2013";451 content: "Expires January 14, 2013"; 452 452 } 453 453 @bottom-right { … … 490 490 <meta name="dct.creator" content="Reschke, J. F."> 491 491 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 492 <meta name="dct.issued" scheme="ISO8601" content="2012-07-1 2">492 <meta name="dct.issued" scheme="ISO8601" content="2012-07-13"> 493 493 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 494 494 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> … … 516 516 </tr> 517 517 <tr> 518 <td class="left">Expires: January 1 3, 2013</td>518 <td class="left">Expires: January 14, 2013</td> 519 519 <td class="right">J. Reschke, Editor</td> 520 520 </tr> … … 525 525 <tr> 526 526 <td class="left"></td> 527 <td class="right">July 1 2, 2012</td>527 <td class="right">July 13, 2012</td> 528 528 </tr> 529 529 </tbody> … … 539 539 </p> 540 540 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 541 <p>Discussion of this draft ought to take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived 542 at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 541 <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 543 542 </p> 544 543 <p>The current issues list is at <<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. … … 555 554 in progress”. 556 555 </p> 557 <p>This Internet-Draft will expire on January 1 3, 2013.</p>556 <p>This Internet-Draft will expire on January 14, 2013.</p> 558 557 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 559 558 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p4-conditional.xml
r1761 r1764 118 118 <note title="Editorial Note (To be removed by RFC Editor)"> 119 119 <t> 120 Discussion of this draft ought to takeplace on the HTTPBIS working group120 Discussion of this draft takes place on the HTTPBIS working group 121 121 mailing list (ietf-http-wg@w3.org), which is archived at 122 122 <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>. -
draft-ietf-httpbis/latest/p5-range.html
r1760 r1764 449 449 } 450 450 @bottom-center { 451 content: "Expires January 1 2, 2013";451 content: "Expires January 14, 2013"; 452 452 } 453 453 @bottom-right { … … 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="2012-07-1 1">494 <meta name="dct.issued" scheme="ISO8601" content="2012-07-13"> 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. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range requests and the rules for constructing and combining responses to those requests."> … … 518 518 </tr> 519 519 <tr> 520 <td class="left">Expires: January 1 2, 2013</td>520 <td class="left">Expires: January 14, 2013</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">July 1 1, 2012</td>529 <td class="right">July 13, 2012</td> 530 530 </tr> 531 531 </tbody> … … 539 539 <p>Part 5 defines range requests and the rules for constructing and combining responses to those requests.</p> 540 540 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 541 <p>Discussion of this draft ought to take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived 542 at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 541 <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 543 542 </p> 544 543 <p>The current issues list is at <<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. … … 555 554 in progress”. 556 555 </p> 557 <p>This Internet-Draft will expire on January 1 2, 2013.</p>556 <p>This Internet-Draft will expire on January 14, 2013.</p> 558 557 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 559 558 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p5-range.xml
r1760 r1764 114 114 <note title="Editorial Note (To be removed by RFC Editor)"> 115 115 <t> 116 Discussion of this draft ought to takeplace on the HTTPBIS working group116 Discussion of this draft takes place on the HTTPBIS working group 117 117 mailing list (ietf-http-wg@w3.org), which is archived at 118 118 <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>. -
draft-ietf-httpbis/latest/p6-cache.html
r1760 r1764 452 452 } 453 453 @bottom-center { 454 content: "Expires January 1 2, 2013";454 content: "Expires January 14, 2013"; 455 455 } 456 456 @bottom-right { … … 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="2012-07-1 1">500 <meta name="dct.issued" scheme="ISO8601" content="2012-07-13"> 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. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 524 524 </tr> 525 525 <tr> 526 <td class="left">Expires: January 1 2, 2013</td>526 <td class="left">Expires: January 14, 2013</td> 527 527 <td class="right">M. Nottingham, Editor</td> 528 528 </tr> … … 541 541 <tr> 542 542 <td class="left"></td> 543 <td class="right">July 1 1, 2012</td>543 <td class="right">July 13, 2012</td> 544 544 </tr> 545 545 </tbody> … … 555 555 </p> 556 556 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 557 <p>Discussion of this draft ought to take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived 558 at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 557 <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 559 558 </p> 560 559 <p>The current issues list is at <<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. … … 571 570 in progress”. 572 571 </p> 573 <p>This Internet-Draft will expire on January 1 2, 2013.</p>572 <p>This Internet-Draft will expire on January 14, 2013.</p> 574 573 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 575 574 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 819 818 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">field-name</a> = <field-name, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>> 820 819 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 5.1</a>> 821 <a href="#abnf.dependencies" class="smpl">port</a> = <port, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2. 7</a>>820 <a href="#abnf.dependencies" class="smpl">port</a> = <port, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>> 822 821 <a href="#abnf.dependencies" class="smpl">pseudonym</a> = <pseudonym, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a>> 823 <a href="#abnf.dependencies" class="smpl">uri-host</a> = <uri-host, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2. 7</a>>822 <a href="#abnf.dependencies" class="smpl">uri-host</a> = <uri-host, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>> 824 823 </pre><h3 id="rfc.section.1.4.3"><a href="#rfc.section.1.4.3">1.4.3</a> <a id="delta-seconds" href="#delta-seconds">Delta Seconds</a></h3> 825 824 <p id="rfc.section.1.4.3.p.1">The delta-seconds rule specifies a non-negative integer, representing time in seconds.</p> … … 2207 2206 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.2">1.4</a></li> 2208 2207 <li><em>Section 2</em> <a href="#rfc.xref.Part1.1">1.3</a></li> 2209 <li><em>Section 2. 7</em> <a href="#rfc.xref.Part1.8">1.4.2</a>, <a href="#rfc.xref.Part1.10">1.4.2</a></li>2208 <li><em>Section 2.8</em> <a href="#rfc.xref.Part1.8">1.4.2</a>, <a href="#rfc.xref.Part1.10">1.4.2</a></li> 2210 2209 <li><em>Section 3.2.1</em> <a href="#rfc.xref.Part1.4">1.4.1</a></li> 2211 2210 <li><em>Section 3.2</em> <a href="#rfc.xref.Part1.7">1.4.2</a>, <a href="#rfc.xref.Part1.13">4.3</a></li> -
draft-ietf-httpbis/latest/p6-cache.xml
r1760 r1764 135 135 <note title="Editorial Note (To be removed by RFC Editor)"> 136 136 <t> 137 Discussion of this draft ought to takeplace on the HTTPBIS working group137 Discussion of this draft takes place on the HTTPBIS working group 138 138 mailing list (ietf-http-wg@w3.org), which is archived at 139 139 <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>. -
draft-ietf-httpbis/latest/p7-auth.html
r1760 r1764 449 449 } 450 450 @bottom-center { 451 content: "Expires January 1 2, 2013";451 content: "Expires January 14, 2013"; 452 452 } 453 453 @bottom-right { … … 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="2012-07-1 1">491 <meta name="dct.issued" scheme="ISO8601" content="2012-07-13"> 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. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework."> … … 520 520 </tr> 521 521 <tr> 522 <td class="left">Expires: January 1 2, 2013</td>522 <td class="left">Expires: January 14, 2013</td> 523 523 <td class="right">greenbytes</td> 524 524 </tr> 525 525 <tr> 526 526 <td class="left"></td> 527 <td class="right">July 1 1, 2012</td>527 <td class="right">July 13, 2012</td> 528 528 </tr> 529 529 </tbody> … … 537 537 <p>Part 7 defines the HTTP Authentication framework.</p> 538 538 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 539 <p>Discussion of this draft ought to take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived 540 at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 539 <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 541 540 </p> 542 541 <p>The current issues list is at <<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. … … 553 552 in progress”. 554 553 </p> 555 <p>This Internet-Draft will expire on January 1 2, 2013.</p>554 <p>This Internet-Draft will expire on January 14, 2013.</p> 556 555 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 557 556 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 762 761 <p>HTTP authentication is presumed to be stateless: all of the information necessary to authenticate a request <em class="bcp14">MUST</em> be provided in the request, rather than be dependent on the server remembering prior requests. Authentication based on, or 763 762 bound to, the underlying connection is outside the scope of this specification and inherently flawed unless steps are taken 764 to ensure that the connection cannot be used by any party other than the authenticated user (see <a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2. 3</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).763 to ensure that the connection cannot be used by any party other than the authenticated user (see <a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.4</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 765 764 </p> 766 765 </li> … … 1212 1211 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.2">1.2</a></li> 1213 1212 <li><em>Section 2</em> <a href="#rfc.xref.Part1.1">1.1</a></li> 1214 <li><em>Section 2. 3</em> <a href="#rfc.xref.Part1.9">2.3.1</a></li>1213 <li><em>Section 2.4</em> <a href="#rfc.xref.Part1.9">2.3.1</a></li> 1215 1214 <li><em>Section 3.2.1</em> <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a></li> 1216 1215 <li><em>Section 3.2.4</em> <a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a></li> -
draft-ietf-httpbis/latest/p7-auth.xml
r1760 r1764 112 112 <note title="Editorial Note (To be removed by RFC Editor)"> 113 113 <t> 114 Discussion of this draft ought to takeplace on the HTTPBIS working group114 Discussion of this draft takes place on the HTTPBIS working group 115 115 mailing list (ietf-http-wg@w3.org), which is archived at 116 116 <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
Note: See TracChangeset
for help on using the changeset viewer.