Changeset 2393 for draft-ietf-httpbis


Ignore:
Timestamp:
14/09/13 14:26:34 (7 years ago)
Author:
julian.reschke@…
Message:

typos/grammar

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2392 r2393  
    446446  }
    447447  @bottom-center {
    448        content: "Expires March 17, 2014";
     448       content: "Expires March 18, 2014";
    449449  }
    450450  @bottom-right {
     
    488488      <meta name="dct.creator" content="Reschke, J. F.">
    489489      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    490       <meta name="dct.issued" scheme="ISO8601" content="2013-09-13">
     490      <meta name="dct.issued" scheme="ISO8601" content="2013-09-14">
    491491      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    492492      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    517517            <tr>
    518518               <td class="left">Intended status: Standards Track</td>
    519                <td class="right">September 13, 2013</td>
     519               <td class="right">September 14, 2013</td>
    520520            </tr>
    521521            <tr>
    522                <td class="left">Expires: March 17, 2014</td>
     522               <td class="left">Expires: March 18, 2014</td>
    523523               <td class="right"></td>
    524524            </tr>
     
    548548         in progress”.
    549549      </p>
    550       <p>This Internet-Draft will expire on March 17, 2014.</p>
     550      <p>This Internet-Draft will expire on March 18, 2014.</p>
    551551      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    552552      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    822822      <p id="rfc.section.2.1.p.9">The following example illustrates a typical message exchange for a GET request on the URI "http://www.example.com/hello.txt":</p>
    823823      <div id="rfc.figure.u.2"></div>
    824       <p>client request:</p><pre class="text2">GET /hello.txt HTTP/1.1
     824      <p>Client request:</p><pre class="text2">GET /hello.txt HTTP/1.1
    825825User-Agent: curl/7.16.3 libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3
    826826Host: www.example.com
     
    828828
    829829</pre><div id="rfc.figure.u.3"></div>
    830       <p>server response:</p><pre class="text">HTTP/1.1 200 OK
     830      <p>Server response:</p><pre class="text">HTTP/1.1 200 OK
    831831Date: Mon, 27 Jul 2009 12:28:53 GMT
    832832Server: Apache
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2392 r2393  
    365365</t>
    366366<figure><preamble>
    367 client request:
     367Client request:
    368368</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
    369369GET /hello.txt HTTP/1.1
     
    374374</artwork></figure>
    375375<figure><preamble>
    376 server response:
     376Server response:
    377377</preamble><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
    378378HTTP/1.1 200 OK
  • draft-ietf-httpbis/latest/p2-semantics.html

    r2391 r2393  
    446446  }
    447447  @bottom-center {
    448        content: "Expires March 17, 2014";
     448       content: "Expires March 18, 2014";
    449449  }
    450450  @bottom-right {
     
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-09-13">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-09-14">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    495495      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     
    519519            <tr>
    520520               <td class="left">Intended status: Standards Track</td>
    521                <td class="right">September 13, 2013</td>
     521               <td class="right">September 14, 2013</td>
    522522            </tr>
    523523            <tr>
    524                <td class="left">Expires: March 17, 2014</td>
     524               <td class="left">Expires: March 18, 2014</td>
    525525               <td class="right"></td>
    526526            </tr>
     
    550550         in progress”.
    551551      </p>
    552       <p>This Internet-Draft will expire on March 17, 2014.</p>
     552      <p>This Internet-Draft will expire on March 18, 2014.</p>
    553553      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    554554      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    12451245         (e.g., a <a href="#status.300" class="smpl">300 (Multiple Choices)</a> response to a GET request).
    12461246      </p>
    1247       <p id="rfc.section.3.4.2.p.3">A server might choose not to send an initial representation, other than than the list of alternatives, and thereby indicate
    1248          that reactive negotiation by the user agent is preferred. For example, the alternatives listed in responses with the <a href="#status.300" class="smpl">300 (Multiple Choices)</a> and <a href="#status.406" class="smpl">406 (Not Acceptable)</a> status codes include information about the available representations so that the user or user agent can react by making a
     1247      <p id="rfc.section.3.4.2.p.3">A server might choose not to send an initial representation, other than the list of alternatives, and thereby indicate that
     1248         reactive negotiation by the user agent is preferred. For example, the alternatives listed in responses with the <a href="#status.300" class="smpl">300 (Multiple Choices)</a> and <a href="#status.406" class="smpl">406 (Not Acceptable)</a> status codes include information about the available representations so that the user or user agent can react by making a
    12491249         selection.
    12501250      </p>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2391 r2393  
    10541054<t>
    10551055   A server might choose not to send an initial representation, other than
    1056    than the list of alternatives, and thereby indicate that reactive
     1056   the list of alternatives, and thereby indicate that reactive
    10571057   negotiation by the user agent is preferred. For example, the alternatives
    10581058   listed in responses with the <x:ref>300 (Multiple Choices)</x:ref> and
  • draft-ietf-httpbis/latest/p6-cache.html

    r2385 r2393  
    449449  }
    450450  @bottom-center {
    451        content: "Expires March 17, 2014";
     451       content: "Expires March 18, 2014";
    452452  }
    453453  @bottom-right {
     
    493493      <meta name="dct.creator" content="Reschke, J. F.">
    494494      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    495       <meta name="dct.issued" scheme="ISO8601" content="2013-09-13">
     495      <meta name="dct.issued" scheme="ISO8601" content="2013-09-14">
    496496      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    497497      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     
    519519            </tr>
    520520            <tr>
    521                <td class="left">Expires: March 17, 2014</td>
     521               <td class="left">Expires: March 18, 2014</td>
    522522               <td class="right">J. Reschke, Editor</td>
    523523            </tr>
     
    528528            <tr>
    529529               <td class="left"></td>
    530                <td class="right">September 13, 2013</td>
     530               <td class="right">September 14, 2013</td>
    531531            </tr>
    532532         </tbody>
     
    554554         in progress”.
    555555      </p>
    556       <p>This Internet-Draft will expire on March 17, 2014.</p>
     556      <p>This Internet-Draft will expire on March 18, 2014.</p>
    557557      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    558558      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    10771077         stored responses, the cache <em class="bcp14">SHOULD</em> forward the conditional request toward the origin server; if the received condition contains a list of entity-tags and the
    10781078         cache has its own set of stored responses for that primary cache key, the cache <em class="bcp14">SHOULD</em> take the union of the received set with the set of entity-tags for its own stored set of responses (fresh or stale) and generate
    1079          an <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a> header field containing that union when it forwards the request toward the origin server. However, if a stored responses contains
     1079         an <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a> header field containing that union when it forwards the request toward the origin server. However, if a stored response contains
    10801080         only partial content, the cache <em class="bcp14">MUST NOT</em> include its entity-tag in the union unless the request is for a range that would be fully satisfied by that stored response.
    10811081      </p>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r2385 r2393  
    945945   <x:ref>If-None-Match</x:ref> header field containing that union when it
    946946   forwards the request toward the origin server.
    947    However, if a stored responses contains only partial content, the cache
     947   However, if a stored response contains only partial content, the cache
    948948   &MUST-NOT; include its entity-tag in the union unless the request is for
    949949   a range that would be fully satisfied by that stored response.
  • draft-ietf-httpbis/latest/p7-auth.html

    r2365 r2393  
    446446  }
    447447  @bottom-center {
    448        content: "Expires March 5, 2014";
     448       content: "Expires March 18, 2014";
    449449  }
    450450  @bottom-right {
     
    486486      <meta name="dct.creator" content="Reschke, J. F.">
    487487      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    488       <meta name="dct.issued" scheme="ISO8601" content="2013-09-01">
     488      <meta name="dct.issued" scheme="ISO8601" content="2013-09-14">
    489489      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    490490      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework.">
     
    514514            <tr>
    515515               <td class="left">Intended status: Standards Track</td>
    516                <td class="right">September 1, 2013</td>
     516               <td class="right">September 14, 2013</td>
    517517            </tr>
    518518            <tr>
    519                <td class="left">Expires: March 5, 2014</td>
     519               <td class="left">Expires: March 18, 2014</td>
    520520               <td class="right"></td>
    521521            </tr>
     
    543543         in progress”.
    544544      </p>
    545       <p>This Internet-Draft will expire on March 5, 2014.</p>
     545      <p>This Internet-Draft will expire on March 18, 2014.</p>
    546546      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    547547      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    698698      <p id="rfc.section.2.2.p.2">A <dfn>protection space</dfn> is defined by the canonical root URI (the scheme and authority components of the effective request URI; see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) of the server being accessed, in combination with the realm value if present. These realms allow the protected resources
    699699         on a server to be partitioned into a set of protection spaces, each with its own authentication scheme and/or authorization
    700          database. The realm value is a string, generally assigned by the origin server, that can have additional semantics specific
     700         database. The realm value is a string, generally assigned by the origin server, which can have additional semantics specific
    701701         to the authentication scheme. Note that a response can have multiple challenges with the same auth-scheme but different realms.
    702702      </p>
     
    845845         <li>
    846846            <p>The credentials carried in an <a href="#header.authorization" class="smpl">Authorization</a> header field are specific to the User Agent, and therefore have the same effect on HTTP caches as the "private" Cache-Control
    847                response directive (<a href="p6-cache.html#cache-response-directive.private" title="private">Section 7.2.2.6</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>), within the scope of the request they appear in.
     847               response directive (<a href="p6-cache.html#cache-response-directive.private" title="private">Section 5.2.2.6</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>), within the scope of the request they appear in.
    848848            </p>
    849849            <p>Therefore, new authentication schemes that choose not to carry credentials in the <a href="#header.authorization" class="smpl">Authorization</a> header field (e.g., using a newly defined header field) will need to explicitly disallow caching, by mandating the use of
    850                either Cache-Control request directives (e.g., "no-store", <a href="p6-cache.html#cache-request-directive.no-store" title="no-store">Section 7.2.1.5</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) or response directives (e.g., "private").
     850               either Cache-Control request directives (e.g., "no-store", <a href="p6-cache.html#cache-request-directive.no-store" title="no-store">Section 5.2.1.5</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) or response directives (e.g., "private").
    851851            </p>
    852852         </li>
     
    12031203                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a>, <a href="#rfc.xref.Part6.2">5.1.2</a>, <a href="#rfc.xref.Part6.3">5.1.2</a>, <a href="#Part6"><b>8.1</b></a><ul>
    12041204                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a></li>
    1205                         <li><em>Section 7.2.1.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.3">5.1.2</a></li>
    1206                         <li><em>Section 7.2.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.2">5.1.2</a></li>
     1205                        <li><em>Section 5.2.1.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.3">5.1.2</a></li>
     1206                        <li><em>Section 5.2.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.2">5.1.2</a></li>
    12071207                     </ul>
    12081208                  </li>
  • draft-ietf-httpbis/latest/p7-auth.xml

    r2365 r2393  
    292292   partitioned into a set of protection spaces, each with its own
    293293   authentication scheme and/or authorization database. The realm value
    294    is a string, generally assigned by the origin server, that can have
     294   is a string, generally assigned by the origin server, which can have
    295295   additional semantics specific to the authentication scheme. Note that a
    296296   response can have multiple challenges with the same auth-scheme but
Note: See TracChangeset for help on using the changeset viewer.