Ignore:
Timestamp:
Jul 3, 2012, 11:26:11 AM (7 years ago)
Author:
julian.reschke@…
Message:

Work-in-progress: hyperlink status codes definitions (for those defined in parts 4, 5, and 7)

File:
1 edited

Legend:

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

    r1697 r1708  
    258258</t>
    259259<t>
    260    The 401 (Unauthorized) response message is used by an origin server
     260   The <x:ref>401 (Unauthorized)</x:ref> response message is used by an origin server
    261261   to challenge the authorization of a user agent. This response &MUST;
    262262   include a WWW-Authenticate header field containing at least one
     
    264264</t>
    265265<t>   
    266    The 407 (Proxy Authentication Required) response message is used by a proxy to
     266   The <x:ref>407 (Proxy Authentication Required)</x:ref> response message is used by a proxy to
    267267   challenge the authorization of a client and &MUST; include a Proxy-Authenticate
    268268   header field containing at least one challenge
     
    290290<t>
    291291   A user agent that wishes to authenticate itself with an origin server
    292    &mdash; usually, but not necessarily, after receiving a 401 (Unauthorized)
     292   &mdash; usually, but not necessarily, after receiving a <x:ref>401 (Unauthorized)</x:ref>
    293293   &mdash; can do so by including an Authorization header field with the
    294294   request.
     
    296296<t>   
    297297   A client that wishes to authenticate itself with a proxy &mdash; usually,
    298    but not necessarily, after receiving a 407 (Proxy Authentication Required)
     298   but not necessarily, after receiving a <x:ref>407 (Proxy Authentication Required)</x:ref>
    299299   &mdash; can do so by including a Proxy-Authorization header field with the
    300300   request.
     
    316316   invalid credentials (e.g., a bad password) or partial credentials (e.g.,
    317317   when the authentication scheme requires more than one round trip), an origin
    318    server &SHOULD; return a 401 (Unauthorized) response. Such responses &MUST;
     318   server &SHOULD; return a <x:ref>401 (Unauthorized)</x:ref> response. Such responses &MUST;
    319319   include a WWW-Authenticate header field containing at least one (possibly
    320320   new) challenge applicable to the requested resource.
     
    323323   Likewise, upon a request that requires authentication by proxies that omit
    324324   credentials or contain invalid or partial credentials, a proxy &SHOULD;
    325    return a 407 (Proxy Authentication Required) response. Such responses
     325   return a <x:ref>407 (Proxy Authentication Required)</x:ref> response. Such responses
    326326   &MUST; include a Proxy-Authenticate header field containing a (possibly
    327327   new) challenge applicable to the proxy.
     
    498498  <iref primary="true" item="401 Unauthorized (status code)" x:for-anchor=""/>
    499499  <iref primary="true" item="Status Codes" subitem="401 Unauthorized" x:for-anchor=""/>
     500  <x:anchor-alias value="401 (Unauthorized)"/>
    500501<t>
    501502   The request requires user authentication. The response &MUST; include a
     
    515516  <iref primary="true" item="407 Proxy Authentication Required (status code)" x:for-anchor=""/>
    516517  <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required" x:for-anchor=""/>
    517 <t>
    518    This code is similar to 401 (Unauthorized), but indicates that the
     518  <x:anchor-alias value="407 (Proxy Authentication Required)"/>
     519<t>
     520   This code is similar to <x:ref>401 (Unauthorized)</x:ref>, but indicates that the
    519521   client ought to first authenticate itself with the proxy. The proxy &MUST;
    520522   return a Proxy-Authenticate header field (<xref target="header.proxy-authenticate"/>) containing a
     
    538540<t>
    539541   The "Authorization" header field allows a user agent to authenticate
    540    itself with a server &mdash; usually, but not necessarily, after receiving a 401
    541    (Unauthorized) response. Its value consists of credentials containing
     542   itself with a server &mdash; usually, but not necessarily, after receiving a <x:ref>401
     543   (Unauthorized)</x:ref> response. Its value consists of credentials containing
    542544   information of the user agent for the realm of the resource being
    543545   requested.
     
    593595   challenge that indicates the authentication scheme(s) and parameters
    594596   applicable to the proxy for this effective request URI (&effective-request-uri;).
    595    It &MUST; be included as part of a 407 (Proxy Authentication Required) response.
     597   It &MUST; be included as part of a <x:ref>407 (Proxy Authentication Required)</x:ref> response.
    596598</t>
    597599<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authenticate"/>
     
    649651</t>
    650652<t>   
    651    It &MUST; be included in 401 (Unauthorized) response messages and &MAY; be
     653   It &MUST; be included in <x:ref>401 (Unauthorized)</x:ref> response messages and &MAY; be
    652654   included in other response messages to indicate that supplying credentials
    653655   (or different credentials) might affect the response.
Note: See TracChangeset for help on using the changeset viewer.