Changeset 746
- Timestamp:
- 17/01/10 14:33:08 (13 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 11 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r744 r746 404 404 <meta name="DC.Creator" content="Reschke, J. F."> 405 405 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 406 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01- 08">406 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-17"> 407 407 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 408 408 <meta name="DC.Description.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 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> … … 435 435 </tr> 436 436 <tr> 437 <td class="left">Expires: July 12, 2010</td>437 <td class="left">Expires: July 21, 2010</td> 438 438 <td class="right">HP</td> 439 439 </tr> … … 488 488 <tr> 489 489 <td class="left"></td> 490 <td class="right">January 8, 2010</td>490 <td class="right">January 17, 2010</td> 491 491 </tr> 492 492 </tbody> … … 520 520 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 521 521 </p> 522 <p>This Internet-Draft will expire in July 12, 2010.</p>522 <p>This Internet-Draft will expire in July 21, 2010.</p> 523 523 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 524 524 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1640 1640 <p id="rfc.section.6.4.p.1">Both transfer codings (TE request header, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section 9.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</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>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight 1641 1641 is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has 1642 a quality value of 0, then content with this parameter is `not acceptable'for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion.1642 a quality value of 0, then content with this parameter is "not acceptable" for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion. 1643 1643 </p> 1644 1644 <div id="rfc.figure.u.55"></div><pre class="inline"><span id="rfc.iref.g.92"></span> <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] ) … … 1877 1877 </p> 1878 1878 <div id="rfc.figure.u.57"></div><pre class="text"> Connection: close 1879 </pre><p id="rfc.section.9.1.p.8">in either the request or the response header fields indicates that the connection <em class="bcp14">SHOULD NOT</em> be considered `persistent'(<a href="#persistent.connections" title="Persistent Connections">Section 7.1</a>) after the current request/response is complete.1879 </pre><p id="rfc.section.9.1.p.8">in either the request or the response header fields indicates that the connection <em class="bcp14">SHOULD NOT</em> be considered "persistent" (<a href="#persistent.connections" title="Persistent Connections">Section 7.1</a>) after the current request/response is complete. 1880 1880 </p> 1881 1881 <p id="rfc.section.9.1.p.9">An HTTP/1.1 client that does not support persistent connections <em class="bcp14">MUST</em> include the "close" connection option in every request message. -
draft-ietf-httpbis/latest/p1-messaging.xml
r744 r746 2088 2088 the range 0 through 1, where 0 is the minimum and 1 the maximum 2089 2089 value. If a parameter has a quality value of 0, then content with 2090 this parameter is `not acceptable'for the client. HTTP/1.12090 this parameter is "not acceptable" for the client. HTTP/1.1 2091 2091 applications &MUST-NOT; generate more than three digits after the 2092 2092 decimal point. User configuration of these values &SHOULD; also be … … 2606 2606 <t> 2607 2607 in either the request or the response header fields indicates that 2608 the connection &SHOULD-NOT; be considered `persistent'(<xref target="persistent.connections"/>)2608 the connection &SHOULD-NOT; be considered "persistent" (<xref target="persistent.connections"/>) 2609 2609 after the current request/response is complete. 2610 2610 </t> -
draft-ietf-httpbis/latest/p2-semantics.html
r741 r746 403 403 <meta name="DC.Creator" content="Reschke, J. F."> 404 404 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 405 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01- 01">405 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-17"> 406 406 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 407 407 <meta name="DC.Description.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 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."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: July 5, 2010</td>436 <td class="left">Expires: July 21, 2010</td> 437 437 <td class="right">HP</td> 438 438 </tr> … … 487 487 <tr> 488 488 <td class="left"></td> 489 <td class="right">January 1 , 2010</td>489 <td class="right">January 17, 2010</td> 490 490 </tr> 491 491 </tbody> … … 518 518 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 519 519 </p> 520 <p>This Internet-Draft will expire in July 5, 2010.</p>520 <p>This Internet-Draft will expire in July 21, 2010.</p> 521 521 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 522 522 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 927 927 <li>Otherwise, the response is a representation of an anonymous (i.e., unidentified) resource.</li> 928 928 </ol> 929 <p id="rfc.section.6.1.p.5"> <span class="comment" id="TODO-req-uri">[<a href="#TODO-req-uri" class="smpl">TODO-req-uri</a>: Note that 'request-URI'is used here; however, we need to come up with a term to denote "the URI that can be inferred from929 <p id="rfc.section.6.1.p.5"> <span class="comment" id="TODO-req-uri">[<a href="#TODO-req-uri" class="smpl">TODO-req-uri</a>: Note that "request-URI" is used here; however, we need to come up with a term to denote "the URI that can be inferred from 930 930 examining the request-target and the Host header." (see <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>>). Also, the comparison function is going to have to be defined somewhere, because we already need to compare URIs for things 931 931 like cache invalidation.]</span> … … 1050 1050 the resource with that URI. If a new resource is created at the request-target, the origin server <em class="bcp14">MUST</em> inform the user agent via the 201 (Created) response. If an existing resource is modified, either the 200 (OK) or 204 (No 1051 1051 Content) response codes <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request. If the resource could not be created or modified with the request-target, 1052 an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the entity <em class="bcp14">MUST NOT</em> ignore any Content-* headers (headers starting with the prefix 'Content-') that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.1052 an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the entity <em class="bcp14">MUST NOT</em> ignore any Content-* headers (headers starting with the prefix "Content-") that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases. 1053 1053 </p> 1054 1054 <p id="rfc.section.7.6.p.2">If the request passes through a cache and the request-target identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable. -
draft-ietf-httpbis/latest/p2-semantics.xml
r741 r746 691 691 <t> 692 692 <cref anchor="TODO-req-uri"> 693 Note that 'request-URI'is used here; however, we need to come up with a693 Note that "request-URI" is used here; however, we need to come up with a 694 694 term to denote "the URI that can be inferred from examining the 695 695 request-target and the Host header." (see <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/196" />). … … 956 956 error response &SHOULD; be given that reflects the nature of the 957 957 problem. The recipient of the entity &MUST-NOT; ignore any Content-* 958 headers (headers starting with the prefix 'Content-') that it does958 headers (headers starting with the prefix "Content-") that it does 959 959 not understand or implement 960 960 and &MUST; return a 501 (Not Implemented) response in such cases. -
draft-ietf-httpbis/latest/p3-payload.html
r745 r746 401 401 <meta name="DC.Creator" content="Reschke, J. F."> 402 402 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 403 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-1 5">403 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-17"> 404 404 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 405 405 <meta name="DC.Description.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 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> … … 427 427 </tr> 428 428 <tr> 429 <td class="left">Expires: July 19, 2010</td>429 <td class="left">Expires: July 21, 2010</td> 430 430 <td class="right">J. Mogul</td> 431 431 </tr> … … 484 484 <tr> 485 485 <td class="left"></td> 486 <td class="right">January 1 5, 2010</td>486 <td class="right">January 17, 2010</td> 487 487 </tr> 488 488 </tbody> … … 514 514 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 515 515 </p> 516 <p>This Internet-Draft will expire in July 19, 2010.</p>516 <p>This Internet-Draft will expire in July 21, 2010.</p> 517 517 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 518 518 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 674 674 <ul class="empty"> 675 675 <li>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations 676 is termed a `variant'. Use of the term `variant'does not necessarily imply that the resource is subject to content negotiation.676 is termed a "variant". Use of the term "variant" does not necessarily imply that the resource is subject to content negotiation. 677 677 </li> 678 678 </ul> … … 1777 1777 </p> 1778 1778 <p id="rfc.section.B.1.p.6">If this header is used in a response with the application/octet-stream content-type, the implied suggestion is that the user 1779 agent should not display the response, but directly enter a `save response as...'dialog.1779 agent should not display the response, but directly enter a "save response as..." dialog. 1780 1780 </p> 1781 1781 <p id="rfc.section.B.1.p.7">See <a href="#content-disposition.issues" title="Content-Disposition Issues">Section 7.2</a> for Content-Disposition security issues. -
draft-ietf-httpbis/latest/p3-payload.xml
r745 r746 286 286 A resource may have one, or more than one, representation(s) 287 287 associated with it at any given instant. Each of these 288 representations is termed a `variant'. Use of the term `variant'288 representations is termed a "variant". Use of the term "variant" 289 289 does not necessarily imply that the resource is subject to content 290 290 negotiation. … … 2670 2670 If this header is used in a response with the application/octet-stream 2671 2671 content-type, the implied suggestion is that the user agent 2672 should not display the response, but directly enter a `save response2673 as... 'dialog.2672 should not display the response, but directly enter a "save response 2673 as..." dialog. 2674 2674 </t> 2675 2675 <t> -
draft-ietf-httpbis/latest/p4-conditional.html
r741 r746 400 400 <meta name="DC.Creator" content="Reschke, J. F."> 401 401 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 402 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01- 01">402 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-15"> 403 403 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 404 404 <meta name="DC.Description.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 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."> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: July 5, 2010</td>428 <td class="left">Expires: July 19, 2010</td> 429 429 <td class="right">J. Mogul</td> 430 430 </tr> … … 483 483 <tr> 484 484 <td class="left"></td> 485 <td class="right">January 1 , 2010</td>485 <td class="right">January 15, 2010</td> 486 486 </tr> 487 487 </tbody> … … 513 513 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 514 514 </p> 515 <p>This Internet-Draft will expire in July 5, 2010.</p>515 <p>This Internet-Draft will expire in July 19, 2010.</p> 516 516 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 517 517 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p5-range.html
r741 r746 400 400 <meta name="DC.Creator" content="Reschke, J. F."> 401 401 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 402 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01- 01">402 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-17"> 403 403 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 404 404 <meta name="DC.Description.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 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."> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: July 5, 2010</td>428 <td class="left">Expires: July 21, 2010</td> 429 429 <td class="right">J. Mogul</td> 430 430 </tr> … … 483 483 <tr> 484 484 <td class="left"></td> 485 <td class="right">January 1 , 2010</td>485 <td class="right">January 17, 2010</td> 486 486 </tr> 487 487 </tbody> … … 513 513 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 514 514 </p> 515 <p>This Internet-Draft will expire in July 5, 2010.</p>515 <p>This Internet-Draft will expire in July 21, 2010.</p> 516 516 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 517 517 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 800 800 to obtain the entire current entity-body. 801 801 </p> 802 <p id="rfc.section.5.3.p.2">The "If-Range" request-header field allows a client to "short-circuit" the second request. Informally, its meaning is `if803 the entity is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity '.802 <p id="rfc.section.5.3.p.2">The "If-Range" request-header field allows a client to "short-circuit" the second request. Informally, its meaning is "if 803 the entity is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity". 804 804 </p> 805 805 <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span> <a href="#header.if-range" class="smpl">If-Range</a> = "If-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.if-range" class="smpl">If-Range-v</a> -
draft-ietf-httpbis/latest/p5-range.xml
r741 r746 656 656 <t> 657 657 The "If-Range" request-header field allows a client to "short-circuit" the second 658 request. Informally, its meaning is `if the entity is unchanged, send658 request. Informally, its meaning is "if the entity is unchanged, send 659 659 me the part(s) that I am missing; otherwise, send me the entire new 660 entity '.660 entity". 661 661 </t> 662 662 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Range"/><iref primary="true" item="Grammar" subitem="If-Range-v"/> -
draft-ietf-httpbis/latest/p7-auth.html
r741 r746 394 394 <meta name="DC.Creator" content="Reschke, J. F."> 395 395 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 396 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01- 01">396 <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-17"> 397 397 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 398 398 <meta name="DC.Description.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 HTTP Authentication."> … … 425 425 </tr> 426 426 <tr> 427 <td class="left">Expires: July 5, 2010</td>427 <td class="left">Expires: July 21, 2010</td> 428 428 <td class="right">HP</td> 429 429 </tr> … … 478 478 <tr> 479 479 <td class="left"></td> 480 <td class="right">January 1 , 2010</td>480 <td class="right">January 17, 2010</td> 481 481 </tr> 482 482 </tbody> … … 508 508 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 509 509 </p> 510 <p>This Internet-Draft will expire in July 5, 2010.</p>510 <p>This Internet-Draft will expire in July 21, 2010.</p> 511 511 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 512 512 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 787 787 the user for credentials. 788 788 </li> 789 <li>Applications which include a session termination indication (such as a `logout' or `commit'button on a page) after which790 the server side of the application `knows'that there is no further reason for the client to retain the credentials.789 <li>Applications which include a session termination indication (such as a "logout" or "commit" button on a page) after which 790 the server side of the application "knows" that there is no further reason for the client to retain the credentials. 791 791 </li> 792 792 </ul> -
draft-ietf-httpbis/latest/p7-auth.xml
r741 r746 576 576 577 577 <t>Applications which include a session termination indication 578 (such as a `logout' or `commit'button on a page) after which579 the server side of the application `knows'that there is no578 (such as a "logout" or "commit" button on a page) after which 579 the server side of the application "knows" that there is no 580 580 further reason for the client to retain the credentials.</t> 581 581 </list>
Note: See TracChangeset
for help on using the changeset viewer.