Changeset 115 for draft-ietf-httpbis


Ignore:
Timestamp:
30/12/07 14:56:05 (15 years ago)
Author:
julian.reschke@…
Message:

Add templates for Changes sections throughout, remove intro specific to draft -00, enhance a few more inter-document references, cleanup some leftovers of the symref switchover.

Location:
draft-ietf-httpbis/latest
Files:
14 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p1-messaging.html

    r113 r115  
    348348      <link rel="Appendix" title="C Conversion of Date Formats" href="#rfc.section.C">
    349349      <link rel="Appendix" title="D Compatibility with Previous Versions" href="#rfc.section.D">
     350      <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
    350351      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.353, 2007/12/11 23:20:44, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    351352      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    … …  
    478479      </p>
    479480      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    480       <p>This version of the HTTP specification contains only minimal editorial changes from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> (abstract, introductory paragraph, and authors' addresses). All other changes are due to partitioning the original into seven
    481          mostly independent parts. The intent is for readers of future drafts to able to use draft 00 as the basis for comparison when
    482          the WG makes later changes to the specification text. This draft will shortly be followed by draft 01 (containing the first
    483          round of changes that have already been agreed to on the mailing list). There is no point in reviewing this draft other than
    484          to verify that the partitioning has been done correctly. Roy T. Fielding, Yves Lafon, and Julian Reschke will be the editors
    485          after draft 00 is submitted.
    486       </p> 
    487481      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    488482         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
    … …  
    607601            </ul>
    608602         </li>
     603         <li class="tocline0">E.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
     604               <li class="tocline1">E.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since RFC2616</a></li>
     605               <li class="tocline1">E.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-ietf-httpbis-p1-messaging-00</a></li>
     606            </ul>
     607         </li>
    609608         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    610609         <li class="tocline0"><a href="#rfc.index">Index</a></li>
    … …  
    612611      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    613612      <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to overall network operation, message framing, interaction with transport
    614          protocols, and URI schemes. Right now it only includes the extracted relevant sections of <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     613         protocols, and URI schemes. Right now it only includes the extracted relevant sections of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    615614      </p>
    616615      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.purpose" href="#intro.purpose">Purpose</a></h2>
    … …  
    927926    &lt;"&gt;            = &lt;US-ASCII double-quote mark (34)&gt;
    928927</pre><p id="rfc.section.2.2.p.3">HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity-body (see <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;B</a> for tolerant applications). The end-of-line marker within an entity-body is defined by its associated media type, as described
    929          in <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
     928         in <a href="p3-payload.html#media.types" title="Media Types">Section 2.3</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    930929      </p>
    931930      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.13"></span>    CRLF           = CR LF
    … …  
    11001099      </p>
    11011100      <p id="rfc.section.3.4.p.8">The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry
    1102          contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.4.1</a>), "gzip" (<a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>), "compress" (<a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>), and "deflate" (<a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
    1103       </p>
    1104       <p id="rfc.section.3.4.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1101         contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.4.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1102      </p>
     1103      <p id="rfc.section.3.4.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
    11051104      </p>
    11061105      <p id="rfc.section.3.4.p.10">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Unimplemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client.
    … …  
    11851184      </p>
    11861185      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="message.headers" href="#message.headers">Message Headers</a></h2>
    1187       <p id="rfc.section.4.2.p.1">HTTP header fields, which include general-header (<a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>), request-header (<a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), response-header (<a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), and entity-header (<a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) fields, follow the same generic format as that given in <a href="http://tools.ietf.org/html/rfc822#section-3.1">Section 3.1</a> of <a href="#RFC822" id="rfc.xref.RFC822.5"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The
     1186      <p id="rfc.section.4.2.p.1">HTTP header fields, which include general-header (<a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>), request-header (<a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), response-header (<a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), and entity-header (<a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) fields, follow the same generic format as that given in <a href="http://tools.ietf.org/html/rfc822#section-3.1">Section 3.1</a> of <a href="#RFC822" id="rfc.xref.RFC822.5"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The
    11881187         field value <em class="bcp14">MAY</em> be preceded by any amount of LWS, though a single SP is preferred. Header fields can be extended over multiple lines by preceding
    11891188         each extra line with at least one SP or HT. Applications ought to follow "common form", where one is known or indicated, when
    … …  
    13001299                     *(( general-header        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    13011300                      | request-header         ; <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a>
    1302                       | entity-header ) CRLF)  ; <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>
     1301                      | entity-header ) CRLF)  ; <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>
    13031302                     CRLF
    13041303                     [ message-body ]          ; <a href="#message.body" title="Message Body">Section&nbsp;4.3</a>
    … …  
    13781377                    *(( general-header        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    13791378                     | response-header        ; <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a>
    1380                      | entity-header ) CRLF)  ; <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>
     1379                     | entity-header ) CRLF)  ; <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>
    13811380                    CRLF
    13821381                    [ message-body ]          ; <a href="#message.body" title="Message Body">Section&nbsp;4.3</a>
    … …  
    17191718         <li>
    17201719            <p>If the transfer-coding being tested is one of the transfer-codings listed in the TE field, then it is acceptable unless it
    1721                is accompanied by a qvalue of 0. (As defined in <a href="p3-payload.html#quality.values" title="Quality Values">Section 2.4</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, a qvalue of 0 means "not acceptable.")
     1720               is accompanied by a qvalue of 0. (As defined in <a href="p3-payload.html#quality.values" title="Quality Values">Section 2.4</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, a qvalue of 0 means "not acceptable.")
    17221721            </p>
    17231722         </li>
    … …  
    19271926      </p>
    19281927      <p id="rfc.section.11.p.5">Thanks to the "cave men" of Palo Alto. You know who you are.</p>
    1929       <p id="rfc.section.11.p.6">Jim Gettys (the current editor of this document) wishes particularly to thank Roy Fielding, the previous editor of this document,
    1930          along with John Klensin, Jeff Mogul, Paul Leach, Dave Kristol, Koen Holtman, John Franks, Josh Cohen, Alex Hopmann, Scott
     1928      <p id="rfc.section.11.p.6">Jim Gettys (the editor of <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>) wishes particularly to thank Roy Fielding, the editor of <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, along with John Klensin, Jeff Mogul, Paul Leach, Dave Kristol, Koen Holtman, John Franks, Josh Cohen, Alex Hopmann, Scott
    19311929         Lawrence, and Larry Masinter for their help. And thanks go particularly to Jeff Mogul and Scott Lawrence for performing the
    19321930         "MUST/MAY/SHOULD" audit.
    … …  
    21892187      </p>
    21902188      <p id="rfc.section.B.p.4">The character set of an entity-body <em class="bcp14">SHOULD</em> be labeled as the lowest common denominator of the character codes used within that body, with the exception that not labeling
    2191          the entity is preferred over labeling the entity with the labels US-ASCII or ISO-8859-1. See <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
     2189         the entity is preferred over labeling the entity with the labels US-ASCII or ISO-8859-1. See <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    21922190      </p>
    21932191      <p id="rfc.section.B.p.5">Additional rules for requirements on parsing and encoding of dates and other potential problems with date encodings include:</p>
    … …  
    22242222      <p id="rfc.section.D.p.3">For most implementations of HTTP/1.0, each connection is established by the client prior to the request and closed by the
    22252223         server after sending the response. Some implementations implement the Keep-Alive version of persistent connections described
    2226          in <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
     2224         in <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
    22272225      </p>
    22282226      <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;<a id="changes.from.1.0" href="#changes.from.1.0">Changes from HTTP/1.0</a></h2>
    … …  
    22642262         a new keyword (Connection: close) for declaring non-persistence. See <a href="#header.connection" id="rfc.xref.header.connection.6" title="Connection">Section&nbsp;8.1</a>.
    22652263      </p>
    2266       <p id="rfc.section.D.2.p.3">The original HTTP/1.0 form of persistent connections (the Connection: Keep-Alive and Keep-Alive header) is documented in <a href="#RFC2068" id="rfc.xref.RFC2068.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
     2264      <p id="rfc.section.D.2.p.3">The original HTTP/1.0 form of persistent connections (the Connection: Keep-Alive and Keep-Alive header) is documented in <a href="#RFC2068" id="rfc.xref.RFC2068.7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
    22672265      </p>
    22682266      <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
    … …  
    22952293      <p id="rfc.section.D.4.p.5">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.7" title="Connection">Section&nbsp;8.1</a>)
    22962294      </p>
     2295      <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
     2296      </h1>
     2297      <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;Since RFC2616
     2298      </h2>
     2299      <p id="rfc.section.E.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     2300      </p>
     2301      <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;Since draft-ietf-httpbis-p1-messaging-00
     2302      </h2>
     2303      <p id="rfc.section.E.2.p.1">TBD.</p>
    22972304      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    22982305      <p>Copyright © The IETF Trust (2007).</p>
    … …  
    24992506                     </ul>
    25002507                  </li>
    2501                   <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.3</a>, <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.4</a>, <a class="iref" href="#rfc.xref.Part3.5">2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">3.4</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a>, <a class="iref" href="#rfc.xref.Part3.8">3.4</a>, <a class="iref" href="#rfc.xref.Part3.9">3.4</a>, <a class="iref" href="#rfc.xref.Part3.10">4.2</a>, <a class="iref" href="#rfc.xref.Part3.11">5</a>, <a class="iref" href="#rfc.xref.Part3.12">6</a>, <a class="iref" href="#rfc.xref.Part3.13">8.5</a>, <a class="iref" href="#Part3"><b>12</b></a>, <a class="iref" href="#rfc.xref.Part3.14">B</a><ul class="ind">
    2502                         <li class="indline1"><em>Section 2.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.13">8.5</a></li>
     2508                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.3</a>, <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.4</a>, <a class="iref" href="#rfc.xref.Part3.5">2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">3.4</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a>, <a class="iref" href="#rfc.xref.Part3.8">4.2</a>, <a class="iref" href="#rfc.xref.Part3.9">5</a>, <a class="iref" href="#rfc.xref.Part3.10">6</a>, <a class="iref" href="#rfc.xref.Part3.11">8.5</a>, <a class="iref" href="#Part3"><b>12</b></a>, <a class="iref" href="#rfc.xref.Part3.12">B</a><ul class="ind">
     2509                        <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.6">3.4</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a></li>
     2510                        <li class="indline1"><em>Section 2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.5">2.2</a></li>
     2511                        <li class="indline1"><em>Section 2.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.11">8.5</a></li>
    25032512                        <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.3</a></li>
    2504                         <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.10">4.2</a>, <a class="iref" href="#rfc.xref.Part3.11">5</a>, <a class="iref" href="#rfc.xref.Part3.12">6</a></li>
     2513                        <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.8">4.2</a>, <a class="iref" href="#rfc.xref.Part3.9">5</a>, <a class="iref" href="#rfc.xref.Part3.10">6</a></li>
    25052514                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a></li>
    25062515                        <li class="indline1"><em>Section A</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.4</a></li>
    … …  
    25332542                  <li class="indline1"><em>RFC2045</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2045.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC2045.2">3.4</a>, <a class="iref" href="#rfc.xref.RFC2045.3">11</a>, <a class="iref" href="#RFC2045"><b>12</b></a></li>
    25342543                  <li class="indline1"><em>RFC2047</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2047.1">2.2</a>, <a class="iref" href="#RFC2047"><b>12</b></a></li>
    2535                   <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2068.2">7.1.1</a>, <a class="iref" href="#rfc.xref.RFC2068.3">7.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.4">7.2.3</a>, <a class="iref" href="#RFC2068"><b>12</b></a>, <a class="iref" href="#rfc.xref.RFC2068.5">D</a>, <a class="iref" href="#rfc.xref.RFC2068.6">D.2</a><ul class="ind">
    2536                         <li class="indline1"><em>Section 19.7.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.5">D</a></li>
     2544                  <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2068.2">7.1.1</a>, <a class="iref" href="#rfc.xref.RFC2068.3">7.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.4">7.2.3</a>, <a class="iref" href="#rfc.xref.RFC2068.5">11</a>, <a class="iref" href="#RFC2068"><b>12</b></a>, <a class="iref" href="#rfc.xref.RFC2068.6">D</a>, <a class="iref" href="#rfc.xref.RFC2068.7">D.2</a><ul class="ind">
     2545                        <li class="indline1"><em>Section 19.7.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.6">D</a></li>
    25372546                     </ul>
    25382547                  </li>
    … …  
    25442553                     </ul>
    25452554                  </li>
    2546                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#RFC2616"><b>12</b></a></li>
     2555                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">11</a>, <a class="iref" href="#RFC2616"><b>12</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3">E.1</a></li>
    25472556                  <li class="indline1"><em>RFC3977</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3977.1">1.1</a>, <a class="iref" href="#RFC3977"><b>12</b></a></li>
    25482557                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#RFC4288"><b>12</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li>

  • draft-ietf-httpbis/latest/p1-messaging.xml

    r113 r115  
    1717  <!ENTITY caching                "<xref target='Part6' x:rel='#caching' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1818  <!ENTITY payload                "<xref target='Part3' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     19  <!ENTITY media-types            "<xref target='Part3' x:rel='#media.types' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     20  <!ENTITY content-codings        "<xref target='Part3' x:rel='#content.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1921  <!ENTITY CONNECT                "<xref target='Part2' x:rel='#CONNECT' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2022  <!ENTITY content.negotiation    "<xref target='Part3' x:rel='#content.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    … …  
    208210<note title="Editorial Note (To be removed by RFC Editor)">
    209211  <t>
    210     This version of the HTTP specification contains only minimal editorial
    211     changes from <xref target="RFC2616"/> (abstract, introductory paragraph,
    212     and authors' addresses).  All other changes are due to partitioning the
    213     original into seven mostly independent parts.  The intent is for readers
    214     of future drafts to able to use draft 00 as the basis for comparison
    215     when the WG makes later changes to the specification text.  This draft
    216     will shortly be followed by draft 01 (containing the first round of changes
    217     that have already been agreed to on the mailing list). There is no point in
    218     reviewing this draft other than to verify that the partitioning has been
    219     done correctly.  Roy T. Fielding, Yves Lafon, and Julian Reschke
    220     will be the editors after draft 00 is submitted.
    221   </t>
    222   <t>
    223212    Discussion of this draft should take place on the HTTPBIS working group
    224213    mailing list (ietf-http-wg@w3.org). The current issues list is
    … …  
    847836   protocol elements except the entity-body (see <xref target="tolerant.applications"/> for
    848837   tolerant applications). The end-of-line marker within an entity-body
    849    is defined by its associated media type, as described in &payload;.
     838   is defined by its associated media type, as described in &media-types;.
    850839</t>
    851840<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="CRLF"/>
    … …  
    12081197   transfer-coding value tokens. Initially, the registry contains the
    12091198   following tokens: "chunked" (<xref target="chunked.transfer.encoding"/>),
    1210    "gzip" (&payload;), "compress" (&payload;), and "deflate" (&payload;).
     1199   "gzip", "compress", and "deflate" (&content-codings;).
    12111200</t>
    12121201<t>
    12131202   New transfer-coding value tokens &SHOULD; be registered in the same way
    1214    as new content-coding value tokens (&payload;).
     1203   as new content-coding value tokens (&content-codings;).
    12151204</t>
    12161205<t>
    … …  
    29022891</t>
    29032892<t>
    2904    Jim Gettys (the current editor of this document) wishes particularly
    2905    to thank Roy Fielding, the previous editor of this document, along
     2893   Jim Gettys (the editor of <xref target="RFC2616"/>) wishes particularly
     2894   to thank Roy Fielding, the editor of <xref target="RFC2068"/>, along
    29062895   with John Klensin, Jeff Mogul, Paul Leach, Dave Kristol, Koen
    29072896   Holtman, John Franks, Josh Cohen, Alex Hopmann, Scott Lawrence, and
    … …  
    39843973</t>
    39853974</section>
    3986 
    3987 </section>
     3975</section>
     3976
     3977<section title="Change Log (to be removed by RFC Editor before publication)">
     3978
     3979<section title="Since RFC2616">
     3980<t>
     3981  Extracted relevant partitions from <xref target="RFC2616"/>.
     3982</t>
     3983</section>
     3984
     3985<section title="Since draft-ietf-httpbis-p1-messaging-00">
     3986<t>
     3987  TBD.
     3988</t>
     3989</section>
     3990
     3991</section>
     3992
    39883993</back>
    39893994</rfc>

  • draft-ietf-httpbis/latest/p2-semantics.html

    r114 r115  
    347347      <link rel="Chapter" href="#rfc.section.14" title="14 References">
    348348      <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A">
     349      <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
    349350      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.353, 2007/12/11 23:20:44, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    350351      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    … …  
    476477      </p>
    477478      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    478       <p>This version of the HTTP specification contains only minimal editorial changes from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> (abstract, introductory paragraph, and authors' addresses). All other changes are due to partitioning the original into seven
    479          mostly independent parts. The intent is for readers of future drafts to able to use draft 00 as the basis for comparison when
    480          the WG makes later changes to the specification text. This draft will shortly be followed by draft 01 (containing the first
    481          round of changes that have already been agreed to on the mailing list). There is no point in reviewing this draft other than
    482          to verify that the partitioning has been done correctly. Roy T. Fielding, Yves Lafon, and Julian Reschke will be the editors
    483          after draft 00 is submitted.
    484       </p> 
    485479      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    486480         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
    … …  
    601595            </ul>
    602596         </li>
     597         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
     598               <li class="tocline1">B.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Since RFC2616</a></li>
     599               <li class="tocline1">B.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>
     600            </ul>
     601         </li>
    603602         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    604603         <li class="tocline0"><a href="#rfc.index">Index</a></li>
    … …  
    16781677         in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;10.8</a>)
    16791678      </p>
     1679      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
     1680      </h1>
     1681      <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;Since RFC2616
     1682      </h2>
     1683      <p id="rfc.section.B.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     1684      </p>
     1685      <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-00
     1686      </h2>
     1687      <p id="rfc.section.B.2.p.1">TBD.</p>
    16801688      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    16811689      <p>Copyright © The IETF Trust (2007).</p>
    … …  
    19201928                  <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">9.3.3</a>, <a class="iref" href="#rfc.xref.RFC2068.2">9.3.6</a>, <a class="iref" href="#RFC2068"><b>14</b></a>, <a class="iref" href="#rfc.xref.RFC2068.3">A.1</a></li>
    19211929                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>14</b></a></li>
    1922                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#RFC2616"><b>14</b></a></li>
     1930                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>14</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">B.1</a></li>
    19231931                  <li class="indline1"><em>RFC822</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC822.1">10.3</a>, <a class="iref" href="#RFC822"><b>14</b></a></li>
    19241932               </ul>

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r114 r115  
    229229<note title="Editorial Note (To be removed by RFC Editor)">
    230230  <t>
    231     This version of the HTTP specification contains only minimal editorial
    232     changes from <xref target="RFC2616"/> (abstract, introductory paragraph,
    233     and authors' addresses).  All other changes are due to partitioning the
    234     original into seven mostly independent parts.  The intent is for readers
    235     of future drafts to able to use draft 00 as the basis for comparison
    236     when the WG makes later changes to the specification text.  This draft
    237     will shortly be followed by draft 01 (containing the first round of changes
    238     that have already been agreed to on the mailing list). There is no point in
    239     reviewing this draft other than to verify that the partitioning has been
    240     done correctly.  Roy T. Fielding, Yves Lafon, and Julian Reschke
    241     will be the editors after draft 00 is submitted.
    242   </t>
    243   <t>
    244231    Discussion of this draft should take place on the HTTPBIS working group
    245232    mailing list (ietf-http-wg@w3.org). The current issues list is
    … …  
    25882575</section>
    25892576
     2577<section title="Change Log (to be removed by RFC Editor before publication)">
     2578
     2579<section title="Since RFC2616">
     2580<t>
     2581  Extracted relevant partitions from <xref target="RFC2616"/>.
     2582</t>
     2583</section>
     2584
     2585<section title="Since draft-ietf-httpbis-p2-semantics-00">
     2586<t>
     2587  TBD.
     2588</t>
     2589</section>
     2590
     2591</section>
     2592
    25902593</back>
    25912594</rfc>

  • draft-ietf-httpbis/latest/p3-payload.html

    r113 r115  
    344344      <link rel="Appendix" title="B Additional Features" href="#rfc.section.B">
    345345      <link rel="Appendix" title="C Compatibility with Previous Versions" href="#rfc.section.C">
     346      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    346347      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.353, 2007/12/11 23:20:44, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    347348      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    … …  
    472473      </p>
    473474      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    474       <p>This version of the HTTP specification contains only minimal editorial changes from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> (abstract, introductory paragraph, and authors' addresses). All other changes are due to partitioning the original into seven
    475          mostly independent parts. The intent is for readers of future drafts to able to use draft 00 as the basis for comparison when
    476          the WG makes later changes to the specification text. This draft will shortly be followed by draft 01 (containing the first
    477          round of changes that have already been agreed to on the mailing list). There is no point in reviewing this draft other than
    478          to verify that the partitioning has been done correctly. Roy T. Fielding, Yves Lafon, and Julian Reschke will be the editors
    479          after draft 00 is submitted.
    480       </p> 
    481475      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    482476         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
    … …  
    558552            </ul>
    559553         </li>
     554         <li class="tocline0">D.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
     555               <li class="tocline1">D.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC2616</a></li>
     556               <li class="tocline1">D.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-ietf-httpbis-p3-payload-00</a></li>
     557            </ul>
     558         </li>
    560559         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    561560         <li class="tocline0"><a href="#rfc.index">Index</a></li>
    … …  
    596595      </p>
    597596      <p id="rfc.section.2.1.p.7">HTTP uses charset in two contexts: within an Accept-Charset request header (in which the charset value is an unquoted token)
    598          and as the value of a parameter in a Content-type header (within a request or response), in which case the parameter value
     597         and as the value of a parameter in a Content-Type header (within a request or response), in which case the parameter value
    599598         of the charset parameter may be quoted.
    600599      </p>
    … …  
    674673      </p>
    675674      <p id="rfc.section.2.3.p.7">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
    676          outlined in RFC 4288 <a href="#RFC4288" id="rfc.xref.RFC4288.2"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. Use of non-registered media types is discouraged.
     675         outlined in <a href="#RFC4288" id="rfc.xref.RFC4288.2"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. Use of non-registered media types is discouraged.
    677676      </p>
    678677      <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
    … …  
    832831         header fields not defined by this specification.
    833832      </p>
    834       <p id="rfc.section.4.1.p.5">The Vary header field <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a> can be used to express the parameters the server uses to select a representation that is subject to server-driven negotiation.
     833      <p id="rfc.section.4.1.p.5">The Vary header field (<a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can be used to express the parameters the server uses to select a representation that is subject to server-driven negotiation.
    835834      </p>
    836835      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="agent-driven.negotiation" href="#agent-driven.negotiation">Agent-driven Negotiation</a></h2>
    … …  
    11101109      <p id="rfc.section.5.7.p.5">A cache cannot assume that an entity with a Content-Location different from the URI used to retrieve it can be used to respond
    11111110         to later requests on that Content-Location URI. However, the Content-Location can be used to differentiate between multiple
    1112          entities retrieved from a single requested resource, as described in <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
     1111         entities retrieved from a single requested resource, as described in <a href="p6-cache.html#caching.negotiated.responses" title="Caching Negotiated Responses">Section 2.6</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
    11131112      </p>
    11141113      <p id="rfc.section.5.7.p.6">If the Content-Location is a relative URI, the relative URI is interpreted relative to the Request-URI.</p>
    … …  
    11221121      </p>
    11231122      <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>     Content-MD5   = "Content-MD5" ":" md5-digest
    1124      md5-digest   = &lt;base64 of 128 bit MD5 digest as per RFC 1864&gt;
     1123     md5-digest   = &lt;base64 of 128 bit MD5 digest as per <a href="#RFC1864" id="rfc.xref.RFC1864.2"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>&gt;
    11251124</pre><p id="rfc.section.5.8.p.3">The Content-MD5 header field <em class="bcp14">MAY</em> be generated by an origin server or client to function as an integrity check of the entity-body. Only origin servers or clients <em class="bcp14">MAY</em> generate the Content-MD5 header field; proxies and gateways <em class="bcp14">MUST NOT</em> generate it, as this would defeat its value as an end-to-end integrity check. Any recipient of the entity-body, including
    11261125         gateways and proxies, <em class="bcp14">MAY</em> check that the digest value in this header field matches that of the entity-body as received.
    … …  
    13571356      <p id="rfc.section.A.1.p.1">HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages <em class="bcp14">MAY</em> include a single MIME-Version general-header field to indicate what version of the MIME protocol was used to construct the
    13581357         message. Use of the MIME-Version header field indicates that the message is in full compliance with the MIME protocol (as
    1359          defined in RFC 2045<a href="#RFC2045" id="rfc.xref.RFC2045.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>). Proxies/gateways are responsible for ensuring full compliance (where possible) when exporting HTTP messages to strict MIME
     1358         defined in <a href="#RFC2045" id="rfc.xref.RFC2045.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>). Proxies/gateways are responsible for ensuring full compliance (where possible) when exporting HTTP messages to strict MIME
    13601359         environments.
    13611360      </p>
    … …  
    13651364      </p>
    13661365      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="conversion.to.canonical.form" href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h2>
    1367       <p id="rfc.section.A.2.p.1"> <a href="#RFC2045" id="rfc.xref.RFC2045.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> requires that an Internet mail entity be converted to canonical form prior to being transferred, as described in section <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line
     1366      <p id="rfc.section.A.2.p.1"> <a href="#RFC2045" id="rfc.xref.RFC2045.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> requires that an Internet mail entity be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line
    13681367         break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted
    13691368         over HTTP.
    … …  
    14491448      <p id="rfc.section.C.2.p.2">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix&nbsp;A.4</a>)
    14501449      </p>
     1450      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
     1451      </h1>
     1452      <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC2616
     1453      </h2>
     1454      <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     1455      </p>
     1456      <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p3-payload-00
     1457      </h2>
     1458      <p id="rfc.section.D.2.p.1">TBD.</p>
    14511459      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    14521460      <p>Copyright © The IETF Trust (2007).</p>
    … …  
    16061614                  </li>
    16071615                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">3.1</a>, <a class="iref" href="#rfc.xref.Part6.2">4.1</a>, <a class="iref" href="#rfc.xref.Part6.3">5.7</a>, <a class="iref" href="#Part6"><b>9</b></a><ul class="ind">
     1616                        <li class="indline1"><em>Section 2.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.3">5.7</a></li>
    16081617                        <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">3.1</a></li>
     1618                        <li class="indline1"><em>Section 3.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.2">4.1</a></li>
    16091619                     </ul>
    16101620                  </li>
    … …  
    16151625                  <li class="indline1"><em>RFC1766</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1766.1">2.5</a>, <a class="iref" href="#RFC1766"><b>9</b></a></li>
    16161626                  <li class="indline1"><em>RFC1806</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1806.1">7.2</a>, <a class="iref" href="#rfc.xref.RFC1806.2">7.2</a>, <a class="iref" href="#RFC1806"><b>9</b></a>, <a class="iref" href="#rfc.xref.RFC1806.3">B.1</a></li>
    1617                   <li class="indline1"><em>RFC1864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1864.1">5.8</a>, <a class="iref" href="#RFC1864"><b>9</b></a></li>
     1627                  <li class="indline1"><em>RFC1864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1864.1">5.8</a>, <a class="iref" href="#rfc.xref.RFC1864.2">5.8</a>, <a class="iref" href="#RFC1864"><b>9</b></a></li>
    16181628                  <li class="indline1"><em>RFC1867</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1867.1">2.3.2</a>, <a class="iref" href="#RFC1867"><b>9</b></a></li>
    16191629                  <li class="indline1"><em>RFC1945</em>&nbsp;&nbsp;<a class="iref" href="#RFC1945"><b>9</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li>
    … …  
    16371647                  <li class="indline1"><em>RFC2277</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2277.1">2.1</a>, <a class="iref" href="#RFC2277"><b>9</b></a></li>
    16381648                  <li class="indline1"><em>RFC2279</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2279.1">2.1</a>, <a class="iref" href="#RFC2279"><b>9</b></a></li>
    1639                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#RFC2616"><b>9</b></a></li>
     1649                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>9</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">D.1</a></li>
    16401650                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4288.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC4288.2">2.3</a>, <a class="iref" href="#RFC4288"><b>9</b></a></li>
    16411651                  <li class="indline1"><em>RFC822</em>&nbsp;&nbsp;<a class="iref" href="#RFC822"><b>9</b></a>, <a class="iref" href="#rfc.xref.RFC822.1">A</a></li>

  • draft-ietf-httpbis/latest/p3-payload.xml

    r113 r115  
    1515  <!ENTITY ID-MONTH "December">
    1616  <!ENTITY ID-YEAR "2007">
    17   <!ENTITY caching                  "<xref target='Part6' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     17  <!ENTITY caching-neg-resp         "<xref target='Part6' x:rel='#caching.negotiated.responses' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1818  <!ENTITY header-transfer-encoding "<xref target='Part1' x:rel='#header.transfer-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1919  <!ENTITY header-allow             "<xref target='Part2' x:rel='#header.allow' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    … …  
    2323  <!ENTITY header-last-modified     "<xref target='Part4' x:rel='#header.last-modified' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2424  <!ENTITY header-user-agent        "<xref target='Part2' x:rel='#header.user-agent' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     25  <!ENTITY header-vary              "<xref target='Part6' x:rel='#header.vary' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2526  <!ENTITY message-body             "<xref target='Part1' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2627  <!ENTITY message-length           "<xref target='Part1' x:rel='#message.length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    … …  
    196197<note title="Editorial Note (To be removed by RFC Editor)">
    197198  <t>
    198     This version of the HTTP specification contains only minimal editorial
    199     changes from <xref target="RFC2616"/> (abstract, introductory paragraph,
    200     and authors' addresses).  All other changes are due to partitioning the
    201     original into seven mostly independent parts.  The intent is for readers
    202     of future drafts to able to use draft 00 as the basis for comparison
    203     when the WG makes later changes to the specification text.  This draft
    204     will shortly be followed by draft 01 (containing the first round of changes
    205     that have already been agreed to on the mailing list). There is no point in
    206     reviewing this draft other than to verify that the partitioning has been
    207     done correctly.  Roy T. Fielding, Yves Lafon, and Julian Reschke
    208     will be the editors after draft 00 is submitted.
    209   </t>
    210   <t>
    211199    Discussion of this draft should take place on the HTTPBIS working group
    212200    mailing list (ietf-http-wg@w3.org). The current issues list is
    … …  
    290278   HTTP uses charset in two contexts: within an Accept-Charset request
    291279   header (in which the charset value is an unquoted token) and as the
    292    value of a parameter in a Content-type header (within a request or
     280   value of a parameter in a Content-Type header (within a request or
    293281   response), in which case the parameter value of the charset parameter
    294282   may be quoted.
    … …  
    432420   Media-type values are registered with the Internet Assigned Number
    433421   Authority (IANA). The media type registration process is
    434    outlined in RFC 4288 <xref target="RFC4288"/>. Use of non-registered media types is
     422   outlined in <xref target="RFC4288"/>. Use of non-registered media types is
    435423   discouraged.
    436424</t>
    … …  
    760748</t>
    761749<t>
    762    The Vary header field &caching; can be used to express the parameters the
     750   The Vary header field (&header-vary;) can be used to express the parameters the
    763751   server uses to select a representation that is subject to server-driven
    764752   negotiation.
    … …  
    12781266   later requests on that Content-Location URI. However, the Content-Location
    12791267   can be used to differentiate between multiple entities
    1280    retrieved from a single requested resource, as described in &caching;.
     1268   retrieved from a single requested resource, as described in &caching-neg-resp;.
    12811269</t>
    12821270<t>
    … …  
    13021290<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-MD5"/><iref primary="true" item="Grammar" subitem="md5-digest"/>
    13031291     Content-MD5   = "Content-MD5" ":" md5-digest
    1304      md5-digest   = &lt;base64 of 128 bit MD5 digest as per RFC 1864&gt;
     1292     md5-digest   = &lt;base64 of 128 bit MD5 digest as per <xref target="RFC1864"/>&gt;
    13051293</artwork></figure>
    13061294<t>
    … …  
    21132101   version of the MIME protocol was used to construct the message. Use
    21142102   of the MIME-Version header field indicates that the message is in
    2115    full compliance with the MIME protocol (as defined in RFC 2045<xref target="RFC2045"/>).
     2103   full compliance with the MIME protocol (as defined in <xref target="RFC2045"/>).
    21162104   Proxies/gateways are responsible for ensuring full compliance (where
    21172105   possible) when exporting HTTP messages to strict MIME environments.
    … …  
    21302118<t>
    21312119   <xref target="RFC2045"/> requires that an Internet mail entity be converted to
    2132    canonical form prior to being transferred, as described in section <xref target="RFC2049" x:fmt="of" x:sec="4"/>.
     2120   canonical form prior to being transferred, as described in <xref target="RFC2049" x:fmt="of" x:sec="4"/>.
    21332121   <xref target="canonicalization.and.text.defaults"/> of this document describes the forms
    21342122   allowed for subtypes of the "text" media type when transmitted over
    … …  
    23092297</section>
    23102298
     2299<section title="Change Log (to be removed by RFC Editor before publication)">
     2300
     2301<section title="Since RFC2616">
     2302<t>
     2303  Extracted relevant partitions from <xref target="RFC2616"/>.
     2304</t>
     2305</section>
     2306
     2307<section title="Since draft-ietf-httpbis-p3-payload-00">
     2308<t>
     2309  TBD.
     2310</t>
     2311</section>
     2312
     2313</section>
     2314
    23112315</back>
    23122316</rfc>

  • draft-ietf-httpbis/latest/p4-conditional.html

    r113 r115  
    343343      <link rel="Chapter" href="#rfc.section.10" title="10 References">
    344344      <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A">
     345      <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
    345346      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.353, 2007/12/11 23:20:44, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    346347      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    … …  
    471472      </p>
    472473      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    473       <p>This version of the HTTP specification contains only minimal editorial changes from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> (abstract, introductory paragraph, and authors' addresses). All other changes are due to partitioning the original into seven
    474          mostly independent parts. The intent is for readers of future drafts to able to use draft 00 as the basis for comparison when
    475          the WG makes later changes to the specification text. This draft will shortly be followed by draft 01 (containing the first
    476          round of changes that have already been agreed to on the mailing list). There is no point in reviewing this draft other than
    477          to verify that the partitioning has been done correctly. Roy T. Fielding, Yves Lafon, and Julian Reschke will be the editors
    478          after draft 00 is submitted.
    479       </p> 
    480474      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    481475         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
    … …  
    514508            </ul>
    515509         </li>
     510         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
     511               <li class="tocline1">B.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Since RFC2616</a></li>
     512               <li class="tocline1">B.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.2">Since draft-ietf-httpbis-p4-conditional-00</a></li>
     513            </ul>
     514         </li>
    516515         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    517516         <li class="tocline0"><a href="#rfc.index">Index</a></li>
    … …  
    519518      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    520519      <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to conditional request messages based on time stamps and entity-tags. Right
    521          now it only includes the extracted relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.2">[RFC2616]</cite> without edit.
     520         now it only includes the extracted relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">[RFC2616]</cite> without edit.
    522521      </p>
    523522      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
    … …  
    563562         </li>
    564563      </ul>
    565       <p id="rfc.section.3.1.p.4">If the conditional GET used a strong cache validator (see <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>), the response <em class="bcp14">SHOULD NOT</em> include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response <em class="bcp14">MUST NOT</em> include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.
     564      <p id="rfc.section.3.1.p.4">If the conditional GET used a strong cache validator (see <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;4</a>), the response <em class="bcp14">SHOULD NOT</em> include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response <em class="bcp14">MUST NOT</em> include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.
    566565      </p>
    567566      <p id="rfc.section.3.1.p.5">If a 304 response indicates an entity not currently cached, then the cache <em class="bcp14">MUST</em> disregard the response and repeat the request without the conditional.
    … …  
    723722      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="header.etag" href="#header.etag">ETag</a></h2>
    724723      <p id="rfc.section.6.1.p.1">The ETag response-header field provides the current value of the entity tag for the requested variant. The headers used with
    725          entity tags are described in Sections <a href="#header.if-match" id="rfc.xref.header.if-match.2" title="If-Match">6.2</a>, <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.2" title="If-None-Match">6.4</a> and <a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The entity tag <em class="bcp14">MAY</em> be used for comparison with other entities from the same resource (see <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;4</a>).
     724         entity tags are described in Sections <a href="#header.if-match" id="rfc.xref.header.if-match.2" title="If-Match">6.2</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.2" title="If-None-Match">6.4</a> of this document, and in <a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The entity tag <em class="bcp14">MAY</em> be used for comparison with other entities from the same resource (see <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;4</a>).
    726725      </p>
    727726      <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span>    ETag = "ETag" ":" entity-tag
    … …  
    752751         header <em class="bcp14">MUST</em> be ignored.
    753752      </p>
    754       <p id="rfc.section.6.2.p.7">The meaning of "If-Match: *" is that the method <em class="bcp14">SHOULD</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) exists, and <em class="bcp14">MUST NOT</em> be performed if the representation does not exist.
     753      <p id="rfc.section.6.2.p.7">The meaning of "If-Match: *" is that the method <em class="bcp14">SHOULD</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) exists, and <em class="bcp14">MUST NOT</em> be performed if the representation does not exist.
    755754      </p>
    756755      <p id="rfc.section.6.2.p.8">A request intended to update a resource (e.g., a PUT) <em class="bcp14">MAY</em> include an If-Match header field to signal that the request method <em class="bcp14">MUST NOT</em> be applied if the entity corresponding to the If-Match value (a single entity tag) is no longer a representation of that resource.
    … …  
    833832         If-None-Match header <em class="bcp14">MUST</em> be ignored. (See <a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates" title="Rules for When to Use Entity Tags and Last-Modified Dates">Section&nbsp;5</a> for a discussion of server behavior when both If-Modified-Since and If-None-Match appear in the same request.)
    834833      </p>
    835       <p id="rfc.section.6.4.p.8">The meaning of "If-None-Match: *" is that the method <em class="bcp14">MUST NOT</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) exists, and <em class="bcp14">SHOULD</em> be performed if the representation does not exist. This feature is intended to be useful in preventing races between PUT operations.
     834      <p id="rfc.section.6.4.p.8">The meaning of "If-None-Match: *" is that the method <em class="bcp14">MUST NOT</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) exists, and <em class="bcp14">SHOULD</em> be performed if the representation does not exist. This feature is intended to be useful in preventing races between PUT operations.
    836835      </p>
    837836      <p id="rfc.section.6.4.p.9">Examples:</p>
    … …  
    943942      <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    944943      <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
     944      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
     945      </h1>
     946      <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;Since RFC2616
     947      </h2>
     948      <p id="rfc.section.B.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     949      </p>
     950      <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p4-conditional-00
     951      </h2>
     952      <p id="rfc.section.B.2.p.1">TBD.</p>
    945953      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    946954      <p>Copyright © The IETF Trust (2007).</p>
    … …  
    10371045                     </ul>
    10381046                  </li>
    1039                   <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">3.1</a>, <a class="iref" href="#rfc.xref.Part6.2">6.2</a>, <a class="iref" href="#rfc.xref.Part6.3">6.4</a>, <a class="iref" href="#Part6"><b>10</b></a><ul class="ind">
    1040                         <li class="indline1"><em>Section 3.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.2">6.2</a>, <a class="iref" href="#rfc.xref.Part6.3">6.4</a></li>
     1047                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">6.2</a>, <a class="iref" href="#rfc.xref.Part6.2">6.4</a>, <a class="iref" href="#Part6"><b>10</b></a><ul class="ind">
     1048                        <li class="indline1"><em>Section 3.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">6.2</a>, <a class="iref" href="#rfc.xref.Part6.2">6.4</a></li>
    10411049                     </ul>
    10421050                  </li>
    … …  
    10491057                  </li>
    10501058                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>10</b></a></li>
    1051                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#RFC2616"><b>10</b></a></li>
     1059                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>10</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li>
    10521060               </ul>
    10531061            </li>

  • draft-ietf-httpbis/latest/p4-conditional.xml

    r113 r115  
    1616  <!ENTITY ID-YEAR "2007">
    1717  <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    18   <!ENTITY caching                    "<xref target='Part6' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1918  <!ENTITY header-if-range            "<xref target='Part5' x:rel='#header.if-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2019  <!ENTITY header-range               "<xref target='Part5' x:rel='#header.range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    … …  
    192191<note title="Editorial Note (To be removed by RFC Editor)">
    193192  <t>
    194     This version of the HTTP specification contains only minimal editorial
    195     changes from <xref target="RFC2616"/> (abstract, introductory paragraph,
    196     and authors' addresses).  All other changes are due to partitioning the
    197     original into seven mostly independent parts.  The intent is for readers
    198     of future drafts to able to use draft 00 as the basis for comparison
    199     when the WG makes later changes to the specification text.  This draft
    200     will shortly be followed by draft 01 (containing the first round of changes
    201     that have already been agreed to on the mailing list). There is no point in
    202     reviewing this draft other than to verify that the partitioning has been
    203     done correctly.  Roy T. Fielding, Yves Lafon, and Julian Reschke
    204     will be the editors after draft 00 is submitted.
    205   </t>
    206   <t>
    207193    Discussion of this draft should take place on the HTTPBIS working group
    208194    mailing list (ietf-http-wg@w3.org). The current issues list is
    … …  
    306292</t>
    307293<t>
    308    If the conditional GET used a strong cache validator (see &caching;),
     294   If the conditional GET used a strong cache validator (see <xref target="weak.and.strong.validators"/>),
    309295   the response &SHOULD-NOT;  include other entity-headers.
    310296   Otherwise (i.e., the conditional GET used a weak validator), the
    … …  
    587573   The ETag response-header field provides the current value of the
    588574   entity tag for the requested variant. The headers used with entity
    589    tags are described in Sections <xref target="header.if-match" format="counter"/>, <xref target="header.if-none-match" format="counter"/> and &header-if-range;. The entity tag
     575   tags are described in Sections <xref target="header.if-match" format="counter"/>
     576   and <xref target="header.if-none-match" format="counter"/> of this document,
     577   and in &header-if-range;. The entity tag
    590578   &MAY; be used for comparison with other entities from the same resource
    591579   (see <xref target="weak.and.strong.validators"/>).
    … …  
    11671155</section>
    11681156
     1157<section title="Change Log (to be removed by RFC Editor before publication)">
     1158
     1159<section title="Since RFC2616">
     1160<t>
     1161  Extracted relevant partitions from <xref target="RFC2616"/>.
     1162</t>
     1163</section>
     1164
     1165<section title="Since draft-ietf-httpbis-p4-conditional-00">
     1166<t>
     1167  TBD.
     1168</t>
     1169</section>
     1170
     1171</section>
     1172
    11691173</back>
    11701174</rfc>

  • draft-ietf-httpbis/latest/p5-range.html

    r113 r115  
    343343      <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A">
    344344      <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B">
     345      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
    345346      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.353, 2007/12/11 23:20:44, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    346347      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    … …  
    471472      </p>
    472473      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    473       <p>This version of the HTTP specification contains only minimal editorial changes from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> (abstract, introductory paragraph, and authors' addresses). All other changes are due to partitioning the original into seven
    474          mostly independent parts. The intent is for readers of future drafts to able to use draft 00 as the basis for comparison when
    475          the WG makes later changes to the specification text. This draft will shortly be followed by draft 01 (containing the first
    476          round of changes that have already been agreed to on the mailing list). There is no point in reviewing this draft other than
    477          to verify that the partitioning has been done correctly. Roy T. Fielding, Yves Lafon, and Julian Reschke will be the editors
    478          after draft 00 is submitted.
    479       </p> 
    480474      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    481475         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
    … …  
    517511            </ul>
    518512         </li>
     513         <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
     514               <li class="tocline1">C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC2616</a></li>
     515               <li class="tocline1">C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p5-range-00</a></li>
     516            </ul>
     517         </li>
    519518         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    520519         <li class="tocline0"><a href="#rfc.index">Index</a></li>
    … …  
    522521      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    523522      <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to range requests, partial responses, and the multipart/byteranges media
    524          type. Right now it only includes the extracted relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.2">[RFC2616]</cite> without edit.
     523         type. Right now it only includes the extracted relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">[RFC2616]</cite> without edit.
    525524      </p>
    526525      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
    … …  
    889888      <p id="rfc.section.B.2.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;3.1</a>)
    890889      </p>
     890      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
     891      </h1>
     892      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
     893      </h2>
     894      <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     895      </p>
     896      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
     897      </h2>
     898      <p id="rfc.section.C.2.p.1">TBD.</p>
    891899      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    892900      <p>Copyright © The IETF Trust (2007).</p>
    … …  
    10021010                  <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#RFC2046"><b>9</b></a>, <a class="iref" href="#rfc.xref.RFC2046.1">A</a></li>
    10031011                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9</b></a></li>
    1004                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#RFC2616"><b>9</b></a></li>
     1012                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>9</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">C.1</a></li>
    10051013               </ul>
    10061014            </li>

  • draft-ietf-httpbis/latest/p5-range.xml

    r113 r115  
    187187<note title="Editorial Note (To be removed by RFC Editor)">
    188188  <t>
    189     This version of the HTTP specification contains only minimal editorial
    190     changes from <xref target="RFC2616"/> (abstract, introductory paragraph,
    191     and authors' addresses).  All other changes are due to partitioning the
    192     original into seven mostly independent parts.  The intent is for readers
    193     of future drafts to able to use draft 00 as the basis for comparison
    194     when the WG makes later changes to the specification text.  This draft
    195     will shortly be followed by draft 01 (containing the first round of changes
    196     that have already been agreed to on the mailing list). There is no point in
    197     reviewing this draft other than to verify that the partitioning has been
    198     done correctly.  Roy T. Fielding, Yves Lafon, and Julian Reschke
    199     will be the editors after draft 00 is submitted.
    200   </t>
    201   <t>
    202189    Discussion of this draft should take place on the HTTPBIS working group
    203190    mailing list (ietf-http-wg@w3.org). The current issues list is
    … …  
    10141001</section>
    10151002
     1003<section title="Change Log (to be removed by RFC Editor before publication)">
     1004
     1005<section title="Since RFC2616">
     1006<t>
     1007  Extracted relevant partitions from <xref target="RFC2616"/>.
     1008</t>
     1009</section>
     1010
     1011<section title="Since draft-ietf-httpbis-p5-range-00">
     1012<t>
     1013  TBD.
     1014</t>
     1015</section>
     1016
     1017</section>
    10161018
    10171019</back>

  • draft-ietf-httpbis/latest/p6-cache.html

    r113 r115  
    340340      <link rel="Chapter" href="#rfc.section.7" title="7 References">
    341341      <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A">
     342      <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
    342343      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.353, 2007/12/11 23:20:44, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    343344      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    … …  
    469470      </p>
    470471      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    471       <p>This version of the HTTP specification contains only minimal editorial changes from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> (abstract, introductory paragraph, and authors' addresses). All other changes are due to partitioning the original into seven
    472          mostly independent parts. The intent is for readers of future drafts to able to use draft 00 as the basis for comparison when
    473          the WG makes later changes to the specification text. This draft will shortly be followed by draft 01 (containing the first
    474          round of changes that have already been agreed to on the mailing list). There is no point in reviewing this draft other than
    475          to verify that the partitioning has been done correctly. Roy T. Fielding, Yves Lafon, and Julian Reschke will be the editors
    476          after draft 00 is submitted.
    477       </p> 
    478472      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    479473         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
    … …  
    557551            </ul>
    558552         </li>
     553         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
     554               <li class="tocline1">B.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Since RFC2616</a></li>
     555               <li class="tocline1">B.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.2">Since draft-ietf-httpbis-p6-cache-00</a></li>
     556            </ul>
     557         </li>
    559558         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    560559         <li class="tocline0"><a href="#rfc.index">Index</a></li>
    … …  
    562561      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    563562      <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to caching response messages. Right now it only includes the extracted relevant
    564          sections of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.2">RFC 2616</cite> without edit.
     563         sections of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite> without edit.
    565564      </p>
    566565      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
    … …  
    969968         dates.
    970969      </p>
    971       <p id="rfc.section.2.3.2.p.2">Entity Tags are described in <a href="p4-conditional.html#entity.tags" title="Entity Tags">Section 2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
     970      <p id="rfc.section.2.3.2.p.2">Entity Tags are described in <a href="p4-conditional.html#entity.tags" title="Entity Tags">Section 2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. The headers used with entity tags are described in <a href="p4-conditional.html#header.fields" title="Header Field Definitions">Section 6</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    972971      </p>
    973972      <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a id="non-validating.conditionals" href="#non-validating.conditionals">Non-validating Conditionals</a></h3>
    … …  
    18061805      <p id="rfc.section.A.2.p.1">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Invalidation After Updates or Deletions">Section&nbsp;2.10</a>)
    18071806      </p>
     1807      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
     1808      </h1>
     1809      <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;Since RFC2616
     1810      </h2>
     1811      <p id="rfc.section.B.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     1812      </p>
     1813      <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p6-cache-00
     1814      </h2>
     1815      <p id="rfc.section.B.2.p.1">TBD.</p>
    18081816      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    18091817      <p>Copyright © The IETF Trust (2007).</p>
    … …  
    19831991                     </ul>
    19841992                  </li>
    1985                   <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">2.3</a>, <a class="iref" href="#rfc.xref.Part4.2">2.3.2</a>, <a class="iref" href="#Part4"><b>7</b></a><ul class="ind">
     1993                  <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">2.3</a>, <a class="iref" href="#rfc.xref.Part4.2">2.3.2</a>, <a class="iref" href="#rfc.xref.Part4.3">2.3.2</a>, <a class="iref" href="#Part4"><b>7</b></a><ul class="ind">
    19861994                        <li class="indline1"><em>Section 2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.2">2.3.2</a></li>
    19871995                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">2.3</a></li>
     1996                        <li class="indline1"><em>Section 6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.3">2.3.2</a></li>
    19881997                     </ul>
    19891998                  </li>
    … …  
    20182027                  <li class="indline1"><em>RFC2047</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2047.1">3.6</a>, <a class="iref" href="#RFC2047"><b>7</b></a></li>
    20192028                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>7</b></a></li>
    2020                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#RFC2616"><b>7</b></a></li>
     2029                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>7</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li>
    20212030               </ul>
    20222031            </li>

  • draft-ietf-httpbis/latest/p6-cache.xml

    r113 r115  
    1818  <!ENTITY combining-byte-ranges       "<xref target='Part5' x:rel='#combining.byte.ranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1919  <!ENTITY entity-length               "<xref target='Part3' x:rel='#entity.length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     20  <!ENTITY entity-header-fields        "<xref target='Part4' x:rel='#header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2021  <!ENTITY entity-tags                 "<xref target='Part4' x:rel='#entity.tags' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2122  <!ENTITY full-date                   "<xref target='Part1' x:rel='#full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    … …  
    199200<note title="Editorial Note (To be removed by RFC Editor)">
    200201  <t>
    201     This version of the HTTP specification contains only minimal editorial
    202     changes from <xref target="RFC2616"/> (abstract, introductory paragraph,
    203     and authors' addresses).  All other changes are due to partitioning the
    204     original into seven mostly independent parts.  The intent is for readers
    205     of future drafts to able to use draft 00 as the basis for comparison
    206     when the WG makes later changes to the specification text.  This draft
    207     will shortly be followed by draft 01 (containing the first round of changes
    208     that have already been agreed to on the mailing list). There is no point in
    209     reviewing this draft other than to verify that the partitioning has been
    210     done correctly.  Roy T. Fielding, Yves Lafon, and Julian Reschke
    211     will be the editors after draft 00 is submitted.
    212   </t>
    213   <t>
    214202    Discussion of this draft should take place on the HTTPBIS working group
    215203    mailing list (ietf-http-wg@w3.org). The current issues list is
    … …  
    10551043</t>
    10561044<t>
    1057    Entity Tags are described in &entity-tags;.
     1045   Entity Tags are described in &entity-tags;. The headers used with entity
     1046   tags are described in &entity-header-fields;.
    10581047</t>
    10591048</section>
    … …  
    28442833</section>
    28452834
     2835<section title="Change Log (to be removed by RFC Editor before publication)">
     2836
     2837<section title="Since RFC2616">
     2838<t>
     2839  Extracted relevant partitions from <xref target="RFC2616"/>.
     2840</t>
     2841</section>
     2842
     2843<section title="Since draft-ietf-httpbis-p6-cache-00">
     2844<t>
     2845  TBD.
     2846</t>
     2847</section>
     2848
     2849</section>
     2850
    28462851</back>
    28472852</rfc>

  • draft-ietf-httpbis/latest/p7-auth.html

    r113 r115  
    340340      <link rel="Chapter" href="#rfc.section.7" title="7 References">
    341341      <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A">
     342      <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
    342343      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.353, 2007/12/11 23:20:44, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    343344      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    … …  
    469470      </p>
    470471      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    471       <p>This version of the HTTP specification contains only minimal editorial changes from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> (abstract, introductory paragraph, and authors' addresses). All other changes are due to partitioning the original into seven
    472          mostly independent parts. The intent is for readers of future drafts to able to use draft 00 as the basis for comparison when
    473          the WG makes later changes to the specification text. This draft will shortly be followed by draft 01 (containing the first
    474          round of changes that have already been agreed to on the mailing list). There is no point in reviewing this draft other than
    475          to verify that the partitioning has been done correctly. Roy T. Fielding, Yves Lafon, and Julian Reschke will be the editors
    476          after draft 00 is submitted.
    477       </p> 
    478472      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    479473         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
    … …  
    510504            </ul>
    511505         </li>
     506         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
     507               <li class="tocline1">B.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Since RFC2616</a></li>
     508               <li class="tocline1">B.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.2">Since draft-ietf-httpbis-p7-auth-00</a></li>
     509            </ul>
     510         </li>
    512511         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    513512         <li class="tocline0"><a href="#rfc.index">Index</a></li>
    … …  
    515514      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    516515      <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to access control and authentication. Right now it only includes the extracted
    517          relevant sections of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.2">RFC 2616</cite> with only minor edits.
     516         relevant sections of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite> with only minor edits.
    518517      </p>
    519518      <p id="rfc.section.1.p.2">HTTP provides several <em class="bcp14">OPTIONAL</em> challenge-response authentication mechanisms which can be used by a server to challenge a client request and by a client to
    … …  
    675674      <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    676675      <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
     676      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
     677      </h1>
     678      <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;Since RFC2616
     679      </h2>
     680      <p id="rfc.section.B.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     681      </p>
     682      <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p7-auth-00
     683      </h2>
     684      <p id="rfc.section.B.2.p.1">TBD.</p>
    677685      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    678686      <p>Copyright © The IETF Trust (2007).</p>
    … …  
    749757            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    750758                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>7</b></a></li>
    751                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#RFC2616"><b>7</b></a></li>
     759                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>7</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li>
    752760                  <li class="indline1"><em>RFC2617</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2617.1">1</a>, <a class="iref" href="#rfc.xref.RFC2617.2">2.1</a>, <a class="iref" href="#rfc.xref.RFC2617.3">2.2</a>, <a class="iref" href="#rfc.xref.RFC2617.4">3.1</a>, <a class="iref" href="#rfc.xref.RFC2617.5">3.2</a>, <a class="iref" href="#rfc.xref.RFC2617.6">3.3</a>, <a class="iref" href="#rfc.xref.RFC2617.7">3.4</a>, <a class="iref" href="#RFC2617"><b>7</b></a></li>
    753761               </ul>

  • draft-ietf-httpbis/latest/p7-auth.xml

    r113 r115  
    185185<note title="Editorial Note (To be removed by RFC Editor)">
    186186  <t>
    187     This version of the HTTP specification contains only minimal editorial
    188     changes from <xref target="RFC2616"/> (abstract, introductory paragraph,
    189     and authors' addresses).  All other changes are due to partitioning the
    190     original into seven mostly independent parts.  The intent is for readers
    191     of future drafts to able to use draft 00 as the basis for comparison
    192     when the WG makes later changes to the specification text.  This draft
    193     will shortly be followed by draft 01 (containing the first round of changes
    194     that have already been agreed to on the mailing list). There is no point in
    195     reviewing this draft other than to verify that the partitioning has been
    196     done correctly.  Roy T. Fielding, Yves Lafon, and Julian Reschke
    197     will be the editors after draft 00 is submitted.
    198   </t>
    199   <t>
    200187    Discussion of this draft should take place on the HTTPBIS working group
    201188    mailing list (ietf-http-wg@w3.org). The current issues list is
    … …  
    598585</section>
    599586
     587<section title="Change Log (to be removed by RFC Editor before publication)">
     588
     589<section title="Since RFC2616">
     590<t>
     591  Extracted relevant partitions from <xref target="RFC2616"/>.
     592</t>
     593</section>
     594
     595<section title="Since draft-ietf-httpbis-p7-auth-00">
     596<t>
     597  TBD.
     598</t>
     599</section>
     600
     601</section>
     602
    600603</back>
    601604</rfc>
Note: See TracChangeset for help on using the changeset viewer.