Ignore:
Timestamp:
Aug 26, 2011, 7:51:22 AM (8 years ago)
Author:
julian.reschke@…
Message:

consistent anchors (does not affect actual spec text)

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1408 r1415  
    359359  }
    360360  @bottom-center {
    361        content: "Expires February 25, 2012";
     361       content: "Expires February 27, 2012";
    362362  }
    363363  @bottom-right {
     
    409409      <meta name="dct.creator" content="Reschke, J. F.">
    410410      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    411       <meta name="dct.issued" scheme="ISO8601" content="2011-08-24">
     411      <meta name="dct.issued" scheme="ISO8601" content="2011-08-26">
    412412      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    413413      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields.">
     
    440440            </tr>
    441441            <tr>
    442                <td class="left">Expires: February 25, 2012</td>
     442               <td class="left">Expires: February 27, 2012</td>
    443443               <td class="right">HP</td>
    444444            </tr>
     
    493493            <tr>
    494494               <td class="left"></td>
    495                <td class="right">August 24, 2011</td>
     495               <td class="right">August 26, 2011</td>
    496496            </tr>
    497497         </tbody>
     
    523523         in progress”.
    524524      </p>
    525       <p>This Internet-Draft will expire on February 25, 2012.</p>
     525      <p>This Internet-Draft will expire on February 27, 2012.</p>
    526526      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    527527      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    651651            </ul>
    652652         </li>
    653          <li>9.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     653         <li>9.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
    654654               <li>9.1&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
    655655               <li>9.2&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
     
    18021802      <h3 id="rfc.section.8.4.7"><a href="#rfc.section.8.4.7">8.4.7</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
    18031803      <p id="rfc.section.8.4.7.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics
    1804          not acceptable according to the Accept and Accept-* header fields sent in the request (see <a href="p3-payload.html#header.fields" title="Header Field Definitions">Section 6</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>).
     1804         not acceptable according to the Accept and Accept-* header fields sent in the request (see <a href="p3-payload.html#header.field.definitions" title="Header Field Definitions">Section 6</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>).
    18051805      </p>
    18061806      <p id="rfc.section.8.4.7.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of available representation characteristics and location(s) from which the user
     
    19651965         in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain a representation describing why that version is not supported and what other protocols are supported by that server.
    19661966      </p>
    1967       <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
     1967      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
    19681968      <p id="rfc.section.9.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics.</p>
    19691969      <div id="rfc.iref.a.1"></div>
     
    27292729      <p id="rfc.section.A.p.8">Define status 426 (Upgrade Required) (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section&nbsp;8.4.19</a>)
    27302730      </p>
    2731       <p id="rfc.section.A.p.9">Change ABNF productions for header fields to only define the field value. (<a href="#header.fields" title="Header Field Definitions">Section&nbsp;9</a>)
     2731      <p id="rfc.section.A.p.9">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;9</a>)
    27322732      </p>
    27332733      <p id="rfc.section.A.p.10">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1401 r1415  
    7575  <!ENTITY status-412                 "<xref target='Part4' x:rel='#status.412' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7676  <!ENTITY status-416                 "<xref target='Part5' x:rel='#status.416' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    77   <!ENTITY p3-header-fields           "<xref target='Part3' x:rel='#header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     77  <!ENTITY p3-header-fields           "<xref target='Part3' x:rel='#header.field.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7878  <!ENTITY p4-status-codes            "<xref target='Part4' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7979  <!ENTITY p5-status-codes            "<xref target='Part5' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    21362136
    21372137
    2138 <section title="Header Field Definitions" anchor="header.fields">
     2138<section title="Header Field Definitions" anchor="header.field.definitions">
    21392139<t>
    21402140   This section defines the syntax and semantics of HTTP/1.1 header fields
     
    35503550<t>
    35513551  Change ABNF productions for header fields to only define the field value.
    3552   (<xref target="header.fields"/>)
     3552  (<xref target="header.field.definitions"/>)
    35533553</t>
    35543554<t>
  • draft-ietf-httpbis/latest/p3-payload.html

    r1414 r1415  
    576576            </ul>
    577577         </li>
    578          <li>6.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     578         <li>6.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
    579579               <li>6.1&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
    580580               <li>6.2&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
     
    10181018         when the server is unwilling or unable to provide a varying response using server-driven negotiation.
    10191019      </p>
    1020       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
     1020      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
    10211021      <p id="rfc.section.6.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to the payload of messages.</p>
    10221022      <div id="rfc.iref.a.1"></div>
     
    17361736      <p id="rfc.section.C.p.2">Remove the default character encoding for text media types; the default now is whatever the media type definition says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a>)
    17371737      </p>
    1738       <p id="rfc.section.C.p.3">Change ABNF productions for header fields to only define the field value. (<a href="#header.fields" title="Header Field Definitions">Section&nbsp;6</a>)
     1738      <p id="rfc.section.C.p.3">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;6</a>)
    17391739      </p>
    17401740      <p id="rfc.section.C.p.4">Remove definition of Content-MD5 header field because it was inconsistently implemented with respect to partial responses,
    1741          and also because of known deficiencies in the hash algorithm itself (see <a href="#RFC6151" id="rfc.xref.RFC6151.1"><cite title="Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms">[RFC6151]</cite></a> for details). (<a href="#header.fields" title="Header Field Definitions">Section&nbsp;6</a>)
     1741         and also because of known deficiencies in the hash algorithm itself (see <a href="#RFC6151" id="rfc.xref.RFC6151.1"><cite title="Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms">[RFC6151]</cite></a> for details). (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;6</a>)
    17421742      </p>
    17431743      <p id="rfc.section.C.p.5">Remove ISO-8859-1 special-casing in Accept-Charset. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section&nbsp;6.2</a>)
  • draft-ietf-httpbis/latest/p3-payload.xml

    r1414 r1415  
    910910</section>
    911911
    912 <section title="Header Field Definitions" anchor="header.fields">
     912<section title="Header Field Definitions" anchor="header.field.definitions">
    913913<t>
    914914   This section defines the syntax and semantics of HTTP/1.1 header fields
     
    25072507<t>
    25082508  Change ABNF productions for header fields to only define the field value.
    2509   (<xref target="header.fields"/>)
     2509  (<xref target="header.field.definitions"/>)
    25102510</t>
    25112511<t>
     
    25132513  implemented with respect to partial responses, and also because of known
    25142514  deficiencies in the hash algorithm itself (see <xref target="RFC6151"/> for details).
    2515   (<xref target="header.fields"/>)
     2515  (<xref target="header.field.definitions"/>)
    25162516</t>
    25172517<t>
  • draft-ietf-httpbis/latest/p4-conditional.html

    r1408 r1415  
    359359  }
    360360  @bottom-center {
    361        content: "Expires February 25, 2012";
     361       content: "Expires February 27, 2012";
    362362  }
    363363  @bottom-right {
     
    404404      <meta name="dct.creator" content="Reschke, J. F.">
    405405      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    406       <meta name="dct.issued" scheme="ISO8601" content="2011-08-24">
     406      <meta name="dct.issued" scheme="ISO8601" content="2011-08-26">
    407407      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    408408      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.">
     
    430430            </tr>
    431431            <tr>
    432                <td class="left">Expires: February 25, 2012</td>
     432               <td class="left">Expires: February 27, 2012</td>
    433433               <td class="right">J. Mogul</td>
    434434            </tr>
     
    487487            <tr>
    488488               <td class="left"></td>
    489                <td class="right">August 24, 2011</td>
     489               <td class="right">August 26, 2011</td>
    490490            </tr>
    491491         </tbody>
     
    517517         in progress”.
    518518      </p>
    519       <p>This Internet-Draft will expire on February 25, 2012.</p>
     519      <p>This Internet-Draft will expire on February 27, 2012.</p>
    520520      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    521521      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    556556            </ul>
    557557         </li>
    558          <li>3.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Precondition Header Fields</a><ul>
     558         <li>3.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Precondition Header Fields</a><ul>
    559559               <li>3.1&nbsp;&nbsp;&nbsp;<a href="#header.if-match">If-Match</a></li>
    560560               <li>3.2&nbsp;&nbsp;&nbsp;<a href="#header.if-none-match">If-None-Match</a></li>
     
    934934         </li>
    935935      </ul>
    936       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.fields" href="#header.fields">Precondition Header Fields</a></h1>
     936      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Precondition Header Fields</a></h1>
    937937      <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields for applying preconditions on requests.</p>
    938938      <div id="rfc.iref.i.1"></div>
     
    12651265      <p id="rfc.section.A.p.1">Allow weak entity-tags in all requests except range requests (Sections <a href="#weak.and.strong.validators" title="Weak versus Strong">2.1</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.2" title="If-None-Match">3.2</a>).
    12661266      </p>
    1267       <p id="rfc.section.A.p.2">Change ABNF productions for header fields to only define the field value. (<a href="#header.fields" title="Precondition Header Fields">Section&nbsp;3</a>)
     1267      <p id="rfc.section.A.p.2">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Precondition Header Fields">Section&nbsp;3</a>)
    12681268      </p>
    12691269      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r1401 r1415  
    778778</section>
    779779
    780 <section title="Precondition Header Fields" anchor="header.fields">
     780<section title="Precondition Header Fields" anchor="header.field.definitions">
    781781<t>
    782782   This section defines the syntax and semantics of HTTP/1.1 header fields
     
    15001500<t>
    15011501  Change ABNF productions for header fields to only define the field value.
    1502   (<xref target="header.fields"/>)
     1502  (<xref target="header.field.definitions"/>)
    15031503</t>
    15041504</section>
  • draft-ietf-httpbis/latest/p5-range.html

    r1408 r1415  
    359359  }
    360360  @bottom-center {
    361        content: "Expires February 25, 2012";
     361       content: "Expires February 27, 2012";
    362362  }
    363363  @bottom-right {
     
    406406      <meta name="dct.creator" content="Reschke, J. F.">
    407407      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    408       <meta name="dct.issued" scheme="ISO8601" content="2011-08-24">
     408      <meta name="dct.issued" scheme="ISO8601" content="2011-08-26">
    409409      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    410410      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.">
     
    432432            </tr>
    433433            <tr>
    434                <td class="left">Expires: February 25, 2012</td>
     434               <td class="left">Expires: February 27, 2012</td>
    435435               <td class="right">J. Mogul</td>
    436436            </tr>
     
    489489            <tr>
    490490               <td class="left"></td>
    491                <td class="right">August 24, 2011</td>
     491               <td class="right">August 26, 2011</td>
    492492            </tr>
    493493         </tbody>
     
    517517         in progress”.
    518518      </p>
    519       <p>This Internet-Draft will expire on February 25, 2012.</p>
     519      <p>This Internet-Draft will expire on February 27, 2012.</p>
    520520      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    521521      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    554554         </li>
    555555         <li>4.&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
    556          <li>5.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     556         <li>5.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
    557557               <li>5.1&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
    558558               <li>5.2&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
     
    728728         of a discontinuous range of the representation, then the client <em class="bcp14">MAY</em> store it as either a multipart range response or as multiple 206 responses with one continuous range each.
    729729      </p>
    730       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
     730      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
    731731      <p id="rfc.section.5.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to range requests and partial responses.</p>
    732732      <div id="rfc.iref.a.1"></div>
     
    12211221      <p id="rfc.section.B.1.p.1">Clarify that it is not ok to use a weak validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
    12221222      </p>
    1223       <p id="rfc.section.B.1.p.2">Change ABNF productions for header fields to only define the field value. (<a href="#header.fields" title="Header Field Definitions">Section&nbsp;5</a>)
     1223      <p id="rfc.section.B.1.p.2">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;5</a>)
    12241224      </p>
    12251225      <p id="rfc.section.B.1.p.3">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
  • draft-ietf-httpbis/latest/p5-range.xml

    r1401 r1415  
    480480</section>
    481481
    482 <section title="Header Field Definitions" anchor="header.fields">
     482<section title="Header Field Definitions" anchor="header.field.definitions">
    483483<t>
    484484   This section defines the syntax and semantics of HTTP/1.1 header fields
     
    13991399<t>
    14001400  Change ABNF productions for header fields to only define the field value.
    1401   (<xref target="header.fields"/>)
     1401  (<xref target="header.field.definitions"/>)
    14021402</t>
    14031403<t>
  • draft-ietf-httpbis/latest/p6-cache.html

    r1408 r1415  
    362362  }
    363363  @bottom-center {
    364        content: "Expires February 25, 2012";
     364       content: "Expires February 27, 2012";
    365365  }
    366366  @bottom-right {
     
    408408      <meta name="dct.creator" content="Reschke, J. F.">
    409409      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    410       <meta name="dct.issued" scheme="ISO8601" content="2011-08-24">
     410      <meta name="dct.issued" scheme="ISO8601" content="2011-08-26">
    411411      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    412412      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     
    434434            </tr>
    435435            <tr>
    436                <td class="left">Expires: February 25, 2012</td>
     436               <td class="left">Expires: February 27, 2012</td>
    437437               <td class="right">J. Mogul</td>
    438438            </tr>
     
    495495            <tr>
    496496               <td class="left"></td>
    497                <td class="right">August 24, 2011</td>
     497               <td class="right">August 26, 2011</td>
    498498            </tr>
    499499         </tbody>
     
    525525         in progress”.
    526526      </p>
    527       <p>This Internet-Draft will expire on February 25, 2012.</p>
     527      <p>This Internet-Draft will expire on February 27, 2012.</p>
    528528      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    529529      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    575575            </ul>
    576576         </li>
    577          <li>3.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     577         <li>3.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
    578578               <li>3.1&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
    579579               <li>3.2&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
     
    11101110         </li>
    11111111      </ul>
    1112       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
     1112      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
    11131113      <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</p>
    11141114      <div id="rfc.iref.a.2"></div>
     
    17831783      <p id="rfc.section.A.p.3">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>)
    17841784      </p>
    1785       <p id="rfc.section.A.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.fields" title="Header Field Definitions">Section&nbsp;3</a>)
     1785      <p id="rfc.section.A.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;3</a>)
    17861786      </p>
    17871787      <p id="rfc.section.A.p.5">Do not mention RFC 2047 encoding and multiple languages in Warning header fields anymore, as these aspects never were implemented.
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1401 r1415  
    11671167</section>
    11681168
    1169 <section anchor="header.fields" title="Header Field Definitions">
     1169<section anchor="header.field.definitions" title="Header Field Definitions">
    11701170<t>
    11711171   This section defines the syntax and semantics of HTTP/1.1 header fields
     
    24402440<t>
    24412441  Change ABNF productions for header fields to only define the field value.
    2442   (<xref target="header.fields"/>)
     2442  (<xref target="header.field.definitions"/>)
    24432443</t>
    24442444<t>
  • draft-ietf-httpbis/latest/p7-auth.html

    r1408 r1415  
    359359  }
    360360  @bottom-center {
    361        content: "Expires February 25, 2012";
     361       content: "Expires February 27, 2012";
    362362  }
    363363  @bottom-right {
     
    404404      <meta name="dct.creator" content="Reschke, J. F.">
    405405      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    406       <meta name="dct.issued" scheme="ISO8601" content="2011-08-24">
     406      <meta name="dct.issued" scheme="ISO8601" content="2011-08-26">
    407407      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    408408      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework.">
     
    435435            </tr>
    436436            <tr>
    437                <td class="left">Expires: February 25, 2012</td>
     437               <td class="left">Expires: February 27, 2012</td>
    438438               <td class="right">HP</td>
    439439            </tr>
     
    488488            <tr>
    489489               <td class="left"></td>
    490                <td class="right">August 24, 2011</td>
     490               <td class="right">August 26, 2011</td>
    491491            </tr>
    492492         </tbody>
     
    516516         in progress”.
    517517      </p>
    518       <p>This Internet-Draft will expire on February 25, 2012.</p>
     518      <p>This Internet-Draft will expire on February 27, 2012.</p>
    519519      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    520520      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    556556            </ul>
    557557         </li>
    558          <li>4.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     558         <li>4.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
    559559               <li>4.1&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
    560560               <li>4.2&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
     
    770770         The proxy <em class="bcp14">MUST</em> return a Proxy-Authenticate header field (<a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.1" title="Proxy-Authenticate">Section&nbsp;4.2</a>) containing a challenge applicable to the proxy for the target resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Proxy-Authorization header field (<a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.1" title="Proxy-Authorization">Section&nbsp;4.3</a>).
    771771      </p>
    772       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
     772      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
    773773      <p id="rfc.section.4.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to authentication.</p>
    774774      <div id="rfc.iref.a.3"></div>
     
    10311031         (<a href="#access.authentication.framework" title="Access Authentication Framework">Section&nbsp;2</a>)
    10321032      </p>
    1033       <p id="rfc.section.A.p.3">Change ABNF productions for header fields to only define the field value. (<a href="#header.fields" title="Header Field Definitions">Section&nbsp;4</a>)
     1033      <p id="rfc.section.A.p.3">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;4</a>)
    10341034      </p>
    10351035      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
  • draft-ietf-httpbis/latest/p7-auth.xml

    r1401 r1415  
    553553</section>
    554554
    555 <section title="Header Field Definitions" anchor="header.fields">
     555<section title="Header Field Definitions" anchor="header.field.definitions">
    556556<t>
    557557   This section defines the syntax and semantics of HTTP/1.1 header fields
     
    11261126<t>
    11271127  Change ABNF productions for header fields to only define the field value.
    1128   (<xref target="header.fields"/>)
     1128  (<xref target="header.field.definitions"/>)
    11291129</t>
    11301130</section>
Note: See TracChangeset for help on using the changeset viewer.