28/02/10 15:22:53 (13 years ago)


1 edited


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

    r756 r763  
    401401      <meta name="dct.creator" content="Reschke, J. F.">
    402402      <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">
    404404      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    405405      <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 &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">
    427427            </tr>
    428428            <tr>
    429                <td class="left">Expires: August 6, 2010</td>
     429               <td class="left">Expires: September 1, 2010</td>
    430430               <td class="right">J. Mogul</td>
    431431            </tr>
    484484            <tr>
    485485               <td class="left"></td>
    486                <td class="right">February 2, 2010</td>
     486               <td class="right">February 28, 2010</td>
    487487            </tr>
    488488         </tbody>
    514514      <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>.
    515515      </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>
    517517      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    518518      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    942942      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="server-driven.negotiation" href="#server-driven.negotiation">Server-driven Negotiation</a></h2>
    943943      <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.,
    945945         language, content-coding, etc.) and the contents of particular header fields in the request message or on other information
    946946         pertaining to the request (such as the network address of the client).
Note: See TracChangeset for help on using the changeset viewer.