Changeset 1415 for draft-ietf-httpbis/latest
- Timestamp:
- 26/08/11 14:51:22 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 12 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1408 r1415 359 359 } 360 360 @bottom-center { 361 content: "Expires February 2 5, 2012";361 content: "Expires February 27, 2012"; 362 362 } 363 363 @bottom-right { … … 409 409 <meta name="dct.creator" content="Reschke, J. F."> 410 410 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 411 <meta name="dct.issued" scheme="ISO8601" content="2011-08-2 4">411 <meta name="dct.issued" scheme="ISO8601" content="2011-08-26"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 413 413 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields."> … … 440 440 </tr> 441 441 <tr> 442 <td class="left">Expires: February 2 5, 2012</td>442 <td class="left">Expires: February 27, 2012</td> 443 443 <td class="right">HP</td> 444 444 </tr> … … 493 493 <tr> 494 494 <td class="left"></td> 495 <td class="right">August 2 4, 2011</td>495 <td class="right">August 26, 2011</td> 496 496 </tr> 497 497 </tbody> … … 523 523 in progress”. 524 524 </p> 525 <p>This Internet-Draft will expire on February 2 5, 2012.</p>525 <p>This Internet-Draft will expire on February 27, 2012.</p> 526 526 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 527 527 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 651 651 </ul> 652 652 </li> 653 <li>9. <a href="#header.field s">Header Field Definitions</a><ul>653 <li>9. <a href="#header.field.definitions">Header Field Definitions</a><ul> 654 654 <li>9.1 <a href="#header.allow">Allow</a></li> 655 655 <li>9.2 <a href="#header.expect">Expect</a></li> … … 1802 1802 <h3 id="rfc.section.8.4.7"><a href="#rfc.section.8.4.7">8.4.7</a> <a id="status.406" href="#status.406">406 Not Acceptable</a></h3> 1803 1803 <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.field s" 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>). 1805 1805 </p> 1806 1806 <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 … … 1965 1965 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. 1966 1966 </p> 1967 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="header.field s" href="#header.fields">Header Field Definitions</a></h1>1967 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1> 1968 1968 <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> 1969 1969 <div id="rfc.iref.a.1"></div> … … 2729 2729 <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 8.4.19</a>) 2730 2730 </p> 2731 <p id="rfc.section.A.p.9">Change ABNF productions for header fields to only define the field value. (<a href="#header.field s" title="Header Field Definitions">Section 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 9</a>) 2732 2732 </p> 2733 2733 <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 75 75 <!ENTITY status-412 "<xref target='Part4' x:rel='#status.412' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 76 76 <!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.field s' 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'/>"> 78 78 <!ENTITY p4-status-codes "<xref target='Part4' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 79 79 <!ENTITY p5-status-codes "<xref target='Part5' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 2136 2136 2137 2137 2138 <section title="Header Field Definitions" anchor="header.field s">2138 <section title="Header Field Definitions" anchor="header.field.definitions"> 2139 2139 <t> 2140 2140 This section defines the syntax and semantics of HTTP/1.1 header fields … … 3550 3550 <t> 3551 3551 Change ABNF productions for header fields to only define the field value. 3552 (<xref target="header.field s"/>)3552 (<xref target="header.field.definitions"/>) 3553 3553 </t> 3554 3554 <t> -
draft-ietf-httpbis/latest/p3-payload.html
r1414 r1415 576 576 </ul> 577 577 </li> 578 <li>6. <a href="#header.field s">Header Field Definitions</a><ul>578 <li>6. <a href="#header.field.definitions">Header Field Definitions</a><ul> 579 579 <li>6.1 <a href="#header.accept">Accept</a></li> 580 580 <li>6.2 <a href="#header.accept-charset">Accept-Charset</a></li> … … 1018 1018 when the server is unwilling or unable to provide a varying response using server-driven negotiation. 1019 1019 </p> 1020 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="header.field s" href="#header.fields">Header Field Definitions</a></h1>1020 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1> 1021 1021 <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> 1022 1022 <div id="rfc.iref.a.1"></div> … … 1736 1736 <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 2.3.1</a>) 1737 1737 </p> 1738 <p id="rfc.section.C.p.3">Change ABNF productions for header fields to only define the field value. (<a href="#header.field s" title="Header Field Definitions">Section 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 6</a>) 1739 1739 </p> 1740 1740 <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.field s" title="Header Field Definitions">Section 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 6</a>) 1742 1742 </p> 1743 1743 <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 6.2</a>) -
draft-ietf-httpbis/latest/p3-payload.xml
r1414 r1415 910 910 </section> 911 911 912 <section title="Header Field Definitions" anchor="header.field s">912 <section title="Header Field Definitions" anchor="header.field.definitions"> 913 913 <t> 914 914 This section defines the syntax and semantics of HTTP/1.1 header fields … … 2507 2507 <t> 2508 2508 Change ABNF productions for header fields to only define the field value. 2509 (<xref target="header.field s"/>)2509 (<xref target="header.field.definitions"/>) 2510 2510 </t> 2511 2511 <t> … … 2513 2513 implemented with respect to partial responses, and also because of known 2514 2514 deficiencies in the hash algorithm itself (see <xref target="RFC6151"/> for details). 2515 (<xref target="header.field s"/>)2515 (<xref target="header.field.definitions"/>) 2516 2516 </t> 2517 2517 <t> -
draft-ietf-httpbis/latest/p4-conditional.html
r1408 r1415 359 359 } 360 360 @bottom-center { 361 content: "Expires February 2 5, 2012";361 content: "Expires February 27, 2012"; 362 362 } 363 363 @bottom-right { … … 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2011-08-2 4">406 <meta name="dct.issued" scheme="ISO8601" content="2011-08-26"> 407 407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 408 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> … … 430 430 </tr> 431 431 <tr> 432 <td class="left">Expires: February 2 5, 2012</td>432 <td class="left">Expires: February 27, 2012</td> 433 433 <td class="right">J. Mogul</td> 434 434 </tr> … … 487 487 <tr> 488 488 <td class="left"></td> 489 <td class="right">August 2 4, 2011</td>489 <td class="right">August 26, 2011</td> 490 490 </tr> 491 491 </tbody> … … 517 517 in progress”. 518 518 </p> 519 <p>This Internet-Draft will expire on February 2 5, 2012.</p>519 <p>This Internet-Draft will expire on February 27, 2012.</p> 520 520 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 521 521 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 556 556 </ul> 557 557 </li> 558 <li>3. <a href="#header.field s">Precondition Header Fields</a><ul>558 <li>3. <a href="#header.field.definitions">Precondition Header Fields</a><ul> 559 559 <li>3.1 <a href="#header.if-match">If-Match</a></li> 560 560 <li>3.2 <a href="#header.if-none-match">If-None-Match</a></li> … … 934 934 </li> 935 935 </ul> 936 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="header.field s" href="#header.fields">Precondition Header Fields</a></h1>936 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="header.field.definitions" href="#header.field.definitions">Precondition Header Fields</a></h1> 937 937 <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> 938 938 <div id="rfc.iref.i.1"></div> … … 1265 1265 <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>). 1266 1266 </p> 1267 <p id="rfc.section.A.p.2">Change ABNF productions for header fields to only define the field value. (<a href="#header.field s" title="Precondition Header Fields">Section 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 3</a>) 1268 1268 </p> 1269 1269 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> -
draft-ietf-httpbis/latest/p4-conditional.xml
r1401 r1415 778 778 </section> 779 779 780 <section title="Precondition Header Fields" anchor="header.field s">780 <section title="Precondition Header Fields" anchor="header.field.definitions"> 781 781 <t> 782 782 This section defines the syntax and semantics of HTTP/1.1 header fields … … 1500 1500 <t> 1501 1501 Change ABNF productions for header fields to only define the field value. 1502 (<xref target="header.field s"/>)1502 (<xref target="header.field.definitions"/>) 1503 1503 </t> 1504 1504 </section> -
draft-ietf-httpbis/latest/p5-range.html
r1408 r1415 359 359 } 360 360 @bottom-center { 361 content: "Expires February 2 5, 2012";361 content: "Expires February 27, 2012"; 362 362 } 363 363 @bottom-right { … … 406 406 <meta name="dct.creator" content="Reschke, J. F."> 407 407 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 408 <meta name="dct.issued" scheme="ISO8601" content="2011-08-2 4">408 <meta name="dct.issued" scheme="ISO8601" content="2011-08-26"> 409 409 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 410 410 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> … … 432 432 </tr> 433 433 <tr> 434 <td class="left">Expires: February 2 5, 2012</td>434 <td class="left">Expires: February 27, 2012</td> 435 435 <td class="right">J. Mogul</td> 436 436 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right">August 2 4, 2011</td>491 <td class="right">August 26, 2011</td> 492 492 </tr> 493 493 </tbody> … … 517 517 in progress”. 518 518 </p> 519 <p>This Internet-Draft will expire on February 2 5, 2012.</p>519 <p>This Internet-Draft will expire on February 27, 2012.</p> 520 520 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 521 521 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 554 554 </li> 555 555 <li>4. <a href="#combining.byte.ranges">Combining Ranges</a></li> 556 <li>5. <a href="#header.field s">Header Field Definitions</a><ul>556 <li>5. <a href="#header.field.definitions">Header Field Definitions</a><ul> 557 557 <li>5.1 <a href="#header.accept-ranges">Accept-Ranges</a></li> 558 558 <li>5.2 <a href="#header.content-range">Content-Range</a></li> … … 728 728 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. 729 729 </p> 730 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="header.field s" href="#header.fields">Header Field Definitions</a></h1>730 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1> 731 731 <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> 732 732 <div id="rfc.iref.a.1"></div> … … 1221 1221 <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 3.1</a>) 1222 1222 </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.field s" title="Header Field Definitions">Section 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 5</a>) 1224 1224 </p> 1225 1225 <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 A</a>) -
draft-ietf-httpbis/latest/p5-range.xml
r1401 r1415 480 480 </section> 481 481 482 <section title="Header Field Definitions" anchor="header.field s">482 <section title="Header Field Definitions" anchor="header.field.definitions"> 483 483 <t> 484 484 This section defines the syntax and semantics of HTTP/1.1 header fields … … 1399 1399 <t> 1400 1400 Change ABNF productions for header fields to only define the field value. 1401 (<xref target="header.field s"/>)1401 (<xref target="header.field.definitions"/>) 1402 1402 </t> 1403 1403 <t> -
draft-ietf-httpbis/latest/p6-cache.html
r1408 r1415 362 362 } 363 363 @bottom-center { 364 content: "Expires February 2 5, 2012";364 content: "Expires February 27, 2012"; 365 365 } 366 366 @bottom-right { … … 408 408 <meta name="dct.creator" content="Reschke, J. F."> 409 409 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 410 <meta name="dct.issued" scheme="ISO8601" content="2011-08-2 4">410 <meta name="dct.issued" scheme="ISO8601" content="2011-08-26"> 411 411 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 412 412 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: February 2 5, 2012</td>436 <td class="left">Expires: February 27, 2012</td> 437 437 <td class="right">J. Mogul</td> 438 438 </tr> … … 495 495 <tr> 496 496 <td class="left"></td> 497 <td class="right">August 2 4, 2011</td>497 <td class="right">August 26, 2011</td> 498 498 </tr> 499 499 </tbody> … … 525 525 in progress”. 526 526 </p> 527 <p>This Internet-Draft will expire on February 2 5, 2012.</p>527 <p>This Internet-Draft will expire on February 27, 2012.</p> 528 528 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 529 529 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 575 575 </ul> 576 576 </li> 577 <li>3. <a href="#header.field s">Header Field Definitions</a><ul>577 <li>3. <a href="#header.field.definitions">Header Field Definitions</a><ul> 578 578 <li>3.1 <a href="#header.age">Age</a></li> 579 579 <li>3.2 <a href="#header.cache-control">Cache-Control</a><ul> … … 1110 1110 </li> 1111 1111 </ul> 1112 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="header.field s" href="#header.fields">Header Field Definitions</a></h1>1112 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1> 1113 1113 <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</p> 1114 1114 <div id="rfc.iref.a.2"></div> … … 1783 1783 <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 2.5</a>) 1784 1784 </p> 1785 <p id="rfc.section.A.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field s" title="Header Field Definitions">Section 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 3</a>) 1786 1786 </p> 1787 1787 <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 1167 1167 </section> 1168 1168 1169 <section anchor="header.field s" title="Header Field Definitions">1169 <section anchor="header.field.definitions" title="Header Field Definitions"> 1170 1170 <t> 1171 1171 This section defines the syntax and semantics of HTTP/1.1 header fields … … 2440 2440 <t> 2441 2441 Change ABNF productions for header fields to only define the field value. 2442 (<xref target="header.field s"/>)2442 (<xref target="header.field.definitions"/>) 2443 2443 </t> 2444 2444 <t> -
draft-ietf-httpbis/latest/p7-auth.html
r1408 r1415 359 359 } 360 360 @bottom-center { 361 content: "Expires February 2 5, 2012";361 content: "Expires February 27, 2012"; 362 362 } 363 363 @bottom-right { … … 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2011-08-2 4">406 <meta name="dct.issued" scheme="ISO8601" content="2011-08-26"> 407 407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 408 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework."> … … 435 435 </tr> 436 436 <tr> 437 <td class="left">Expires: February 2 5, 2012</td>437 <td class="left">Expires: February 27, 2012</td> 438 438 <td class="right">HP</td> 439 439 </tr> … … 488 488 <tr> 489 489 <td class="left"></td> 490 <td class="right">August 2 4, 2011</td>490 <td class="right">August 26, 2011</td> 491 491 </tr> 492 492 </tbody> … … 516 516 in progress”. 517 517 </p> 518 <p>This Internet-Draft will expire on February 2 5, 2012.</p>518 <p>This Internet-Draft will expire on February 27, 2012.</p> 519 519 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 520 520 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 556 556 </ul> 557 557 </li> 558 <li>4. <a href="#header.field s">Header Field Definitions</a><ul>558 <li>4. <a href="#header.field.definitions">Header Field Definitions</a><ul> 559 559 <li>4.1 <a href="#header.authorization">Authorization</a></li> 560 560 <li>4.2 <a href="#header.proxy-authenticate">Proxy-Authenticate</a></li> … … 770 770 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 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 4.3</a>). 771 771 </p> 772 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="header.field s" href="#header.fields">Header Field Definitions</a></h1>772 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1> 773 773 <p id="rfc.section.4.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to authentication.</p> 774 774 <div id="rfc.iref.a.3"></div> … … 1031 1031 (<a href="#access.authentication.framework" title="Access Authentication Framework">Section 2</a>) 1032 1032 </p> 1033 <p id="rfc.section.A.p.3">Change ABNF productions for header fields to only define the field value. (<a href="#header.field s" title="Header Field Definitions">Section 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 4</a>) 1034 1034 </p> 1035 1035 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> -
draft-ietf-httpbis/latest/p7-auth.xml
r1401 r1415 553 553 </section> 554 554 555 <section title="Header Field Definitions" anchor="header.field s">555 <section title="Header Field Definitions" anchor="header.field.definitions"> 556 556 <t> 557 557 This section defines the syntax and semantics of HTTP/1.1 header fields … … 1126 1126 <t> 1127 1127 Change ABNF productions for header fields to only define the field value. 1128 (<xref target="header.field s"/>)1128 (<xref target="header.field.definitions"/>) 1129 1129 </t> 1130 1130 </section>
Note: See TracChangeset
for help on using the changeset viewer.