Jul 29, 2010, 11:11:34 PM (9 years ago)

Addresses #109: Clarify entity / representation / variant terminology

Removed entity-header adjective and ABNF and clarified distinction
between payload and representation.

Uncapitalize the phrase effective request URI so that it doesn't
dominate the prose, and define the term "target resource" to be
used instead of the "resource identified by the effective request URI".

1 edited


  • draft-ietf-httpbis/latest/p7-auth.xml

    r961 r965  
    303303   The request requires user authentication. The response &MUST; include a
    304304   WWW-Authenticate header field (<xref target="header.www-authenticate"/>) containing a challenge
    305    applicable to the requested resource. The client &MAY; repeat the
     305   applicable to the target resource. The client &MAY; repeat the
    306306   request with a suitable Authorization header field (<xref target="header.authorization"/>). If
    307307   the request already included Authorization credentials, then the 401
    323323   client must first authenticate itself with the proxy. The proxy &MUST;
    324324   return a Proxy-Authenticate header field (<xref target="header.proxy-authenticate"/>) containing a
    325    challenge applicable to the proxy for the requested resource. The
     325   challenge applicable to the proxy for the target resource. The
    326326   client &MAY; repeat the request with a suitable Proxy-Authorization
    327327   header field (<xref target="header.proxy-authorization"/>). HTTP access authentication is explained
    402402   The "Proxy-Authenticate" response-header field consists of a challenge that
    403403   indicates the authentication scheme and parameters applicable to the proxy
    404    for this Effective Request URI (&effective-request-uri;). It &MUST; be included as part
     404   for this effective request URI (&effective-request-uri;). It &MUST; be included as part
    405405   of a 407 (Proxy Authentication Required) response.
    461461   The "WWW-Authenticate" response-header field consists of at least one
    462462   challenge that indicates the authentication scheme(s) and parameters
    463    applicable to the Effective Request URI (&effective-request-uri;). It &MUST; be included in 401
     463   applicable to the effective request URI (&effective-request-uri;). It &MUST; be included in 401
    464464   (Unauthorized) response messages.
Note: See TracChangeset for help on using the changeset viewer.