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

typos/grammar

File:
1 edited

Legend:

Unmodified
Added
Removed
  • 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>
Note: See TracChangeset for help on using the changeset viewer.