Changeset 1101 for draft-ietf-httpbis/latest/p7-auth.xml
- Timestamp:
- 08/01/11 14:27:21 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p7-auth.xml
r1099 r1101 15 15 <!ENTITY ID-MONTH "January"> 16 16 <!ENTITY ID-YEAR "2011"> 17 <!ENTITY mdash "—"> 17 18 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 18 19 <!ENTITY notation-abnf "<xref target='Part1' x:rel='#notation.abnf' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 352 353 <t> 353 354 A user agent that wishes to authenticate itself with an origin 354 server --usually, but not necessarily, after receiving a 401355 (Unauthorized) --&MAY; do so by including an Authorization header field355 server — usually, but not necessarily, after receiving a 401 356 (Unauthorized) — &MAY; do so by including an Authorization header field 356 357 with the request. A client that wishes to authenticate itself with a 357 proxy --usually, but not necessarily, after receiving a 407 (Proxy358 Authentication Required) --&MAY; do so by including a Proxy-Authorization358 proxy — usually, but not necessarily, after receiving a 407 (Proxy 359 Authentication Required) — &MAY; do so by including a Proxy-Authorization 359 360 header field with the request. Both the Authorization 360 361 field value and the Proxy-Authorization field value consist of … … 475 476 <t> 476 477 The "Authorization" request-header field allows a user agent to authenticate 477 itself with a server --usually, but not necessarily, after receiving a 401478 itself with a server — usually, but not necessarily, after receiving a 401 478 479 (Unauthorized) response. Its value consists of credentials containing 479 480 information of the user agent for the realm of the resource being
Note: See TracChangeset
for help on using the changeset viewer.