Ignore:
Timestamp:
Jan 8, 2011, 6:27:21 AM (9 years ago)
Author:
julian.reschke@…
Message:

use mdash for long dashes, make use of dashes consistent

File:
1 edited

Legend:

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

    r1099 r1101  
    397397      <meta name="dct.creator" content="Reschke, J. F.">
    398398      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    399       <meta name="dct.issued" scheme="ISO8601" content="2011-01-01">
     399      <meta name="dct.issued" scheme="ISO8601" content="2011-01-08">
    400400      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    401401      <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 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication.">
     
    428428            </tr>
    429429            <tr>
    430                <td class="left">Expires: July 5, 2011</td>
     430               <td class="left">Expires: July 12, 2011</td>
    431431               <td class="right">HP</td>
    432432            </tr>
     
    481481            <tr>
    482482               <td class="left"></td>
    483                <td class="right">January 1, 2011</td>
     483               <td class="right">January 8, 2011</td>
    484484            </tr>
    485485         </tbody>
     
    507507         in progress”.
    508508      </p>
    509       <p>This Internet-Draft will expire on July 5, 2011.</p>
     509      <p>This Internet-Draft will expire on July 12, 2011.</p>
    510510      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    511511      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    648648         scheme. Note that there can be multiple challenges with the same auth-scheme but different realms.
    649649      </p>
    650       <p id="rfc.section.2.p.10">A user agent that wishes to authenticate itself with an origin server -- usually, but not necessarily, after receiving a 401
    651          (Unauthorized) -- <em class="bcp14">MAY</em> do so by including an Authorization header field with the request. A client that wishes to authenticate itself with a proxy
    652          -- usually, but not necessarily, after receiving a 407 (Proxy Authentication Required) -- <em class="bcp14">MAY</em> do so by including a Proxy-Authorization header field with the request. Both the Authorization field value and the Proxy-Authorization
     650      <p id="rfc.section.2.p.10">A user agent that wishes to authenticate itself with an origin server usually, but not necessarily, after receiving a 401
     651         (Unauthorized) <em class="bcp14">MAY</em> do so by including an Authorization header field with the request. A client that wishes to authenticate itself with a proxy
     652         — usually, but not necessarily, after receiving a 407 (Proxy Authentication Required) — <em class="bcp14">MAY</em> do so by including a Proxy-Authorization header field with the request. Both the Authorization field value and the Proxy-Authorization
    653653         field value consist of credentials containing the authentication information of the client for the realm of the resource being
    654654         requested. The user agent <em class="bcp14">MUST</em> choose to use one of the challenges with the strongest auth-scheme it understands and request credentials from the user based
     
    705705      <div id="rfc.iref.h.1"></div>
    706706      <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>
    707       <p id="rfc.section.4.1.p.1">The "Authorization" request-header field allows a user agent to authenticate itself with a server -- usually, but not necessarily,
     707      <p id="rfc.section.4.1.p.1">The "Authorization" request-header field allows a user agent to authenticate itself with a server usually, but not necessarily,
    708708         after receiving a 401 (Unauthorized) response. Its value consists of credentials containing information of the user agent
    709709         for the realm of the resource being requested.
Note: See TracChangeset for help on using the changeset viewer.