Ignore:
Timestamp:
16/12/12 03:46:23 (8 years ago)
Author:
fielding@…
Message:

editorial fixes in methods; use send instead of return, sent instead of returned; partly addresses #419

File:
1 edited

Legend:

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

    r2046 r2052  
    242242   invalid credentials (e.g., a bad password) or partial credentials (e.g.,
    243243   when the authentication scheme requires more than one round trip), an origin
    244    server &SHOULD; return a <x:ref>401 (Unauthorized)</x:ref> response. Such
     244   server &SHOULD; send a <x:ref>401 (Unauthorized)</x:ref> response. Such
    245245   responses &MUST; include a <x:ref>WWW-Authenticate</x:ref> header field
    246246   containing at least one (possibly new) challenge applicable to the
     
    250250   Likewise, upon a request that requires authentication by proxies that omit
    251251   credentials or contain invalid or partial credentials, a proxy &SHOULD;
    252    return a <x:ref>407 (Proxy Authentication Required)</x:ref> response. Such responses
     252   send a <x:ref>407 (Proxy Authentication Required)</x:ref> response. Such responses
    253253   &MUST; include a <x:ref>Proxy-Authenticate</x:ref> header field containing a (possibly
    254254   new) challenge applicable to the proxy.
     
    446446   This code is similar to <x:ref>401 (Unauthorized)</x:ref>, but indicates that the
    447447   client ought to first authenticate itself with the proxy. The proxy &MUST;
    448    return a <x:ref>Proxy-Authenticate</x:ref> header field (<xref target="header.proxy-authenticate"/>) containing a
     448   send a <x:ref>Proxy-Authenticate</x:ref> header field (<xref target="header.proxy-authenticate"/>) containing a
    449449   challenge applicable to the proxy for the target resource. The
    450450   client &MAY; repeat the request with a suitable <x:ref>Proxy-Authorization</x:ref>
Note: See TracChangeset for help on using the changeset viewer.