Ignore:
Timestamp:
14/09/13 23:59:24 (7 years ago)
Author:
fielding@…
Message:

rephrase misused SHOULDs; addresses #472

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p7-auth.html

    r2393 r2398  
    726726      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="header.authorization" href="#header.authorization">Authorization</a></h2>
    727727      <p id="rfc.section.4.1.p.1">The "Authorization" header field allows a user agent to authenticate itself with an origin server — usually, but not necessarily,
    728          after receiving a <a href="#status.401" class="smpl">401
    729             (Unauthorized)</a> response. Its value consists of credentials containing information of the user agent for the realm of the resource being requested.
     728         after receiving a <a href="#status.401" class="smpl">401 (Unauthorized)</a> response. Its value consists of credentials containing the authentication information of the user agent for the realm of the
     729         resource being requested.
    730730      </p>
    731731      <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.6"></span>  <a href="#header.authorization" class="smpl">Authorization</a> = <a href="#challenge.and.response" class="smpl">credentials</a>
    732 </pre><p id="rfc.section.4.1.p.3">If a request is authenticated and a realm specified, the same credentials <em class="bcp14">SHOULD</em> be valid for all other requests within this realm (assuming that the authentication scheme itself does not require otherwise,
    733          such as credentials that vary according to a challenge value or using synchronized clocks).
     732</pre><p id="rfc.section.4.1.p.3">If a request is authenticated and a realm specified, the same credentials are presumed to be valid for all other requests
     733         within this realm (assuming that the authentication scheme itself does not require otherwise, such as credentials that vary
     734         according to a challenge value or using synchronized clocks).
    734735      </p>
    735736      <p id="rfc.section.4.1.p.4">See <a href="p6-cache.html#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section 3.2</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> for details of and requirements pertaining to handling of the Authorization field by HTTP caches.
Note: See TracChangeset for help on using the changeset viewer.