Changeset 763 for draft-ietf-httpbis


Ignore:
Timestamp:
Feb 28, 2010, 7:22:53 AM (10 years ago)
Author:
julian.reschke@…
Message:

punctuation

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p1-messaging.html

    r761 r763  
    404404      <meta name="dct.creator" content="Reschke, J. F.">
    405405      <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">
    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 1 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.">
    … …  
    435435            </tr>
    436436            <tr>
    437                <td class="left">Expires: August 21, 2010</td>
     437               <td class="left">Expires: September 1, 2010</td>
    438438               <td class="right">HP</td>
    439439            </tr>
    … …  
    488488            <tr>
    489489               <td class="left"></td>
    490                <td class="right">February 17, 2010</td>
     490               <td class="right">February 28, 2010</td>
    491491            </tr>
    492492         </tbody>
    … …  
    520520      <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>.
    521521      </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>
    523523      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    524524      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    19201920         <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.
    19211921         </li>
    1922          <li>If the response status code conveys a server error, e.g. 500 (Internal Server Error) or 503 (Service Unavailable), and it
     1922         <li>If the response status code conveys a server error, e.g., 500 (Internal Server Error) or 503 (Service Unavailable), and it
    19231923            is inconvenient or impossible to generate a valid Date.
    19241924         </li>
    … …  
    24242424      </p>
    24252425      <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<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,
    24272427         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
    24282428         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  
    26972697         the server's option.</t>
    26982698
    2699       <t>If the response status code conveys a server error, e.g. 500
     2699      <t>If the response status code conveys a server error, e.g., 500
    27002700         (Internal Server Error) or 503 (Service Unavailable), and it is
    27012701         inconvenient or impossible to generate a valid Date.</t>
    … …  
    34703470<t>
    34713471   HTTP clients are often privy to large amounts of personal information
    3472    (e.g. the user's name, location, mail address, passwords, encryption
     3472   (e.g., the user's name, location, mail address, passwords, encryption
    34733473   keys, etc.), and &SHOULD; be very careful to prevent unintentional
    34743474   leakage of this information.

  • draft-ietf-httpbis/latest/p2-semantics.html

    r760 r763  
    403403      <meta name="dct.creator" content="Reschke, J. F.">
    404404      <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">
    406406      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    407407      <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 &#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.">
    … …  
    434434            </tr>
    435435            <tr>
    436                <td class="left">Expires: August 16, 2010</td>
     436               <td class="left">Expires: September 1, 2010</td>
    437437               <td class="right">HP</td>
    438438            </tr>
    … …  
    487487            <tr>
    488488               <td class="left"></td>
    489                <td class="right">February 12, 2010</td>
     489               <td class="right">February 28, 2010</td>
    490490            </tr>
    491491         </tbody>
    … …  
    518518      <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>.
    519519      </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>
    521521      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    522522      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    10971097      <div id="rfc.iref.m.8"></div>
    10981098      <h2 id="rfc.section.7.9"><a href="#rfc.section.7.9">7.9</a>&nbsp;<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.,
    11001100         SSL tunneling <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>).
    11011101      </p>
    … …  
    14891489      <h3 id="rfc.section.8.5.5"><a href="#rfc.section.8.5.5">8.5.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
    14901490      <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.
    14921492      </p>
    14931493      <div class="note" id="rfc.section.8.5.5.p.2">
    … …  
    22222222      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    22232223      <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<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&nbsp;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&nbsp;8.5.5</a>).
    22252225      </p>
    22262226      <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&nbsp;8.2.2</a>).

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r760 r763  
    10611061<t>
    10621062   This specification reserves the method name CONNECT for use with a
    1063    proxy that can dynamically switch to being a tunnel (e.g. SSL
     1063   proxy that can dynamically switch to being a tunnel (e.g., SSL
    10641064   tunneling <xref target="RFC2817"/>).
    10651065</t>
    … …  
    18481848<t>
    18491849   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 needed
     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 needed
    18521852   to access in attempting to complete the request.
    18531853</t>
    … …  
    31823182<t>
    31833183   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"/>).
    31853185</t>
    31863186<t>

  • 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).

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

    r756 r763  
    854854   an algorithm located at the server, it is called server-driven
    855855   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,
    857857   content-coding, etc.) and the contents of particular header fields in
    858858   the request message or on other information pertaining to the request

  • draft-ietf-httpbis/latest/p4-conditional.html

    r756 r763  
    400400      <meta name="dct.creator" content="Reschke, J. F.">
    401401      <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">
    403403      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    404404      <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 &#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.">
    … …  
    426426            </tr>
    427427            <tr>
    428                <td class="left">Expires: August 6, 2010</td>
     428               <td class="left">Expires: September 1, 2010</td>
    429429               <td class="right">J. Mogul</td>
    430430            </tr>
    … …  
    483483            <tr>
    484484               <td class="left"></td>
    485                <td class="right">February 2, 2010</td>
     485               <td class="right">February 28, 2010</td>
    486486            </tr>
    487487         </tbody>
    … …  
    513513      <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>.
    514514      </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>
    516516      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    517517      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    976976      </p>
    977977      <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 not
     978         a method (e.g., PUT) from inadvertently modifying an existing resource when the client believes that the resource does not
    979979         exist.
    980980      </p>

  • draft-ietf-httpbis/latest/p4-conditional.xml

    r756 r763  
    892892<t>
    893893   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)
    895895   from inadvertently modifying an existing resource when the client
    896896   believes that the resource does not exist.

  • draft-ietf-httpbis/latest/p6-cache.html

    r756 r763  
    402402      <meta name="dct.creator" content="Reschke, J. F.">
    403403      <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">
    405405      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    406406      <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 &#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.">
    … …  
    428428            </tr>
    429429            <tr>
    430                <td class="left">Expires: August 6, 2010</td>
     430               <td class="left">Expires: September 1, 2010</td>
    431431               <td class="right">J. Mogul</td>
    432432            </tr>
    … …  
    489489            <tr>
    490490               <td class="left"></td>
    491                <td class="right">February 2, 2010</td>
     491               <td class="right">February 28, 2010</td>
    492492            </tr>
    493493         </tbody>
    … …  
    519519      <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>.
    520520      </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>
    522522      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    523523      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    13891389            it important that users not be presented with error messages or warning messages when they use navigation controls (such as
    13901390            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.
    13931393         </p>
    13941394      </div>

  • draft-ietf-httpbis/latest/p6-cache.xml

    r756 r763  
    15681568    resources. Even though sometimes such resources ought not be cached, or ought to expire
    15691569    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 effects
     1570    means of preventing caching (e.g., "once-only" URLs) in order not to suffer the effects
    15711571    of improperly functioning history mechanisms.
    15721572  </t>
Note: See TracChangeset for help on using the changeset viewer.