Changeset 763 for draft-ietf-httpbis
- Timestamp:
- 28/02/10 15:22:53 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 10 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r761 r763 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2010-02- 17">406 <meta name="dct.issued" scheme="ISO8601" content="2010-02-28"> 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 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: August 21, 2010</td>437 <td class="left">Expires: September 1, 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">February 17, 2010</td>490 <td class="right">February 28, 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 August 21, 2010.</p>522 <p>This Internet-Draft will expire in September 1, 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> … … 1920 1920 <li>If the response status code is 100 (Continue) or 101 (Switching Protocols), the response <em class="bcp14">MAY</em> include a Date header field, at the server's option. 1921 1921 </li> 1922 <li>If the response status code conveys a server error, e.g. 500 (Internal Server Error) or 503 (Service Unavailable), and it1922 <li>If the response status code conveys a server error, e.g., 500 (Internal Server Error) or 503 (Service Unavailable), and it 1923 1923 is inconvenient or impossible to generate a valid Date. 1924 1924 </li> … … 2424 2424 </p> 2425 2425 <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a> <a id="personal.information" href="#personal.information">Personal Information</a></h2> 2426 <p id="rfc.section.11.1.p.1">HTTP clients are often privy to large amounts of personal information (e.g. the user's name, location, mail address, passwords,2426 <p id="rfc.section.11.1.p.1">HTTP clients are often privy to large amounts of personal information (e.g., the user's name, location, mail address, passwords, 2427 2427 encryption keys, etc.), and <em class="bcp14">SHOULD</em> be very careful to prevent unintentional leakage of this information. We very strongly recommend that a convenient interface 2428 2428 be provided for the user to control dissemination of such information, and that designers and implementors be particularly -
draft-ietf-httpbis/latest/p1-messaging.xml
r761 r763 2697 2697 the server's option.</t> 2698 2698 2699 <t>If the response status code conveys a server error, e.g. 5002699 <t>If the response status code conveys a server error, e.g., 500 2700 2700 (Internal Server Error) or 503 (Service Unavailable), and it is 2701 2701 inconvenient or impossible to generate a valid Date.</t> … … 3470 3470 <t> 3471 3471 HTTP clients are often privy to large amounts of personal information 3472 (e.g. the user's name, location, mail address, passwords, encryption3472 (e.g., the user's name, location, mail address, passwords, encryption 3473 3473 keys, etc.), and &SHOULD; be very careful to prevent unintentional 3474 3474 leakage of this information. -
draft-ietf-httpbis/latest/p2-semantics.html
r760 r763 403 403 <meta name="dct.creator" content="Reschke, J. F."> 404 404 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 405 <meta name="dct.issued" scheme="ISO8601" content="2010-02- 12">405 <meta name="dct.issued" scheme="ISO8601" content="2010-02-28"> 406 406 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 407 407 <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 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: August 16, 2010</td>436 <td class="left">Expires: September 1, 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">February 12, 2010</td>489 <td class="right">February 28, 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 August 16, 2010.</p>520 <p>This Internet-Draft will expire in September 1, 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> … … 1097 1097 <div id="rfc.iref.m.8"></div> 1098 1098 <h2 id="rfc.section.7.9"><a href="#rfc.section.7.9">7.9</a> <a id="CONNECT" href="#CONNECT">CONNECT</a></h2> 1099 <p id="rfc.section.7.9.p.1">This specification reserves the method name CONNECT for use with a proxy that can dynamically switch to being a tunnel (e.g. 1099 <p id="rfc.section.7.9.p.1">This specification reserves the method name CONNECT for use with a proxy that can dynamically switch to being a tunnel (e.g., 1100 1100 SSL tunneling <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). 1101 1101 </p> … … 1489 1489 <h3 id="rfc.section.8.5.5"><a href="#rfc.section.8.5.5">8.5.5</a> <a id="status.504" href="#status.504">504 Gateway Timeout</a></h3> 1490 1490 <p id="rfc.section.8.5.5.p.1">The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the 1491 URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g.DNS) it needed to access in attempting to complete the request.1491 URI (e.g., HTTP, FTP, LDAP) or some other auxiliary server (e.g., DNS) it needed to access in attempting to complete the request. 1492 1492 </p> 1493 1493 <div class="note" id="rfc.section.8.5.5.p.2"> … … 2222 2222 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> 2223 2223 <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2> 2224 <p id="rfc.section.A.1.p.1">Clarified which error code should be used for inbound server failures (e.g. DNS failures). (<a href="#status.504" id="rfc.xref.status.504.3" title="504 Gateway Timeout">Section 8.5.5</a>).2224 <p id="rfc.section.A.1.p.1">Clarified which error code should be used for inbound server failures (e.g., DNS failures). (<a href="#status.504" id="rfc.xref.status.504.3" title="504 Gateway Timeout">Section 8.5.5</a>). 2225 2225 </p> 2226 2226 <p id="rfc.section.A.1.p.2">201 (Created) had a race that required an Etag be sent when a resource is first created. (<a href="#status.201" id="rfc.xref.status.201.3" title="201 Created">Section 8.2.2</a>). -
draft-ietf-httpbis/latest/p2-semantics.xml
r760 r763 1061 1061 <t> 1062 1062 This specification reserves the method name CONNECT for use with a 1063 proxy that can dynamically switch to being a tunnel (e.g. SSL1063 proxy that can dynamically switch to being a tunnel (e.g., SSL 1064 1064 tunneling <xref target="RFC2817"/>). 1065 1065 </t> … … 1848 1848 <t> 1849 1849 The server, while acting as a gateway or proxy, did not receive a 1850 timely response from the upstream server specified by the URI (e.g. 1851 HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed1850 timely response from the upstream server specified by the URI (e.g., 1851 HTTP, FTP, LDAP) or some other auxiliary server (e.g., DNS) it needed 1852 1852 to access in attempting to complete the request. 1853 1853 </t> … … 3182 3182 <t> 3183 3183 Clarified which error code should be used for inbound server failures 3184 (e.g. DNS failures). (<xref target="status.504"/>).3184 (e.g., DNS failures). (<xref target="status.504"/>). 3185 3185 </t> 3186 3186 <t> -
draft-ietf-httpbis/latest/p3-payload.html
r756 r763 401 401 <meta name="dct.creator" content="Reschke, J. F."> 402 402 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 403 <meta name="dct.issued" scheme="ISO8601" content="2010-02- 02">403 <meta name="dct.issued" scheme="ISO8601" content="2010-02-28"> 404 404 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 405 405 <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 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: August 6, 2010</td>429 <td class="left">Expires: September 1, 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">February 2 , 2010</td>486 <td class="right">February 28, 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 August 6, 2010.</p>516 <p>This Internet-Draft will expire in September 1, 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> … … 942 942 <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a> <a id="server-driven.negotiation" href="#server-driven.negotiation">Server-driven Negotiation</a></h2> 943 943 <p id="rfc.section.4.1.p.1">If the selection of the best representation for a response is made by an algorithm located at the server, it is called server-driven 944 negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g. 944 negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g., 945 945 language, content-coding, etc.) and the contents of particular header fields in the request message or on other information 946 946 pertaining to the request (such as the network address of the client). -
draft-ietf-httpbis/latest/p3-payload.xml
r756 r763 854 854 an algorithm located at the server, it is called server-driven 855 855 negotiation. Selection is based on the available representations of 856 the response (the dimensions over which it can vary; e.g. language,856 the response (the dimensions over which it can vary; e.g., language, 857 857 content-coding, etc.) and the contents of particular header fields in 858 858 the request message or on other information pertaining to the request -
draft-ietf-httpbis/latest/p4-conditional.html
r756 r763 400 400 <meta name="dct.creator" content="Reschke, J. F."> 401 401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 402 <meta name="dct.issued" scheme="ISO8601" content="2010-02- 02">402 <meta name="dct.issued" scheme="ISO8601" content="2010-02-28"> 403 403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404 404 <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 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: August 6, 2010</td>428 <td class="left">Expires: September 1, 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">February 2 , 2010</td>485 <td class="right">February 28, 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 August 6, 2010.</p>515 <p>This Internet-Draft will expire in September 1, 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> … … 976 976 </p> 977 977 <p id="rfc.section.6.4.p.2">This allows efficient updates of cached information with a minimum amount of transaction overhead. It is also used to prevent 978 a method (e.g. PUT) from inadvertently modifying an existing resource when the client believes that the resource does not978 a method (e.g., PUT) from inadvertently modifying an existing resource when the client believes that the resource does not 979 979 exist. 980 980 </p> -
draft-ietf-httpbis/latest/p4-conditional.xml
r756 r763 892 892 <t> 893 893 This allows efficient updates of cached information with a minimum amount of 894 transaction overhead. It is also used to prevent a method (e.g. PUT)894 transaction overhead. It is also used to prevent a method (e.g., PUT) 895 895 from inadvertently modifying an existing resource when the client 896 896 believes that the resource does not exist. -
draft-ietf-httpbis/latest/p6-cache.html
r756 r763 402 402 <meta name="dct.creator" content="Reschke, J. F."> 403 403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2010-02- 02">404 <meta name="dct.issued" scheme="ISO8601" content="2010-02-28"> 405 405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406 406 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. 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."> … … 428 428 </tr> 429 429 <tr> 430 <td class="left">Expires: August 6, 2010</td>430 <td class="left">Expires: September 1, 2010</td> 431 431 <td class="right">J. Mogul</td> 432 432 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right">February 2 , 2010</td>491 <td class="right">February 28, 2010</td> 492 492 </tr> 493 493 </tbody> … … 519 519 <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>. 520 520 </p> 521 <p>This Internet-Draft will expire in August 6, 2010.</p>521 <p>This Internet-Draft will expire in September 1, 2010.</p> 522 522 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 523 523 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1389 1389 it important that users not be presented with error messages or warning messages when they use navigation controls (such as 1390 1390 BACK) to view previously fetched resources. Even though sometimes such resources ought not be cached, or ought to expire quickly, 1391 user interface considerations may force service authors to resort to other means of preventing caching (e.g. "once-only" URLs)1392 in order not to suffer the effects of improperly functioning history mechanisms.1391 user interface considerations may force service authors to resort to other means of preventing caching (e.g., "once-only" 1392 URLs) in order not to suffer the effects of improperly functioning history mechanisms. 1393 1393 </p> 1394 1394 </div> -
draft-ietf-httpbis/latest/p6-cache.xml
r756 r763 1568 1568 resources. Even though sometimes such resources ought not be cached, or ought to expire 1569 1569 quickly, user interface considerations may force service authors to resort to other 1570 means of preventing caching (e.g. "once-only" URLs) in order not to suffer the effects1570 means of preventing caching (e.g., "once-only" URLs) in order not to suffer the effects 1571 1571 of improperly functioning history mechanisms. 1572 1572 </t>
Note: See TracChangeset
for help on using the changeset viewer.