Ignore:
Timestamp:
Dec 31, 2012, 3:51:04 AM (7 years ago)
Author:
fielding@…
Message:

(editorial) that vs which

File:
1 edited

Legend:

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

    r2069 r2074  
    120120<t>
    121121   HTTP provides several &OPTIONAL; challenge-response authentication
    122    mechanisms which can be used by a server to challenge a client request and
     122   mechanisms that can be used by a server to challenge a client request and
    123123   by a client to provide authentication information. The "basic" and "digest"
    124124   authentication schemes continue to be specified in
     
    290290   partitioned into a set of protection spaces, each with its own
    291291   authentication scheme and/or authorization database. The realm value
    292    is a string, generally assigned by the origin server, which can have
     292   is a string, generally assigned by the origin server, that can have
    293293   additional semantics specific to the authentication scheme. Note that
    294294   there can be multiple challenges with the same auth-scheme but
     
    408408    </t>
    409409    <t>
    410       Therefore, new authentication schemes which choose not to carry
     410      Therefore, new authentication schemes that choose not to carry
    411411      credentials in the <x:ref>Authorization</x:ref> header field (e.g., using a newly defined
    412412      header field) will need to explicitly disallow caching, by mandating the use of
     
    524524<t>
    525525   The "Proxy-Authorization" header field allows the client to
    526    identify itself (or its user) to a proxy which requires
     526   identify itself (or its user) to a proxy that requires
    527527   authentication. Its value consists of
    528528   credentials containing the authentication information of the user
     
    694694   application's security model include but are not limited to:
    695695  <list style="symbols">
    696      <t>Clients which have been idle for an extended period following
    697         which the server might wish to cause the client to reprompt the
     696     <t>Clients that have been idle for an extended period, following
     697        which the server might wish to cause the client to re-prompt the
    698698        user for credentials.</t>
    699699
    700      <t>Applications which include a session termination indication
     700     <t>Applications that include a session termination indication
    701701        (such as a "logout" or "commit" button on a page) after which
    702702        the server side of the application "knows" that there is no
     
    708708   to parts of this problem, and we encourage the use of
    709709   password protection in screen savers, idle time-outs, and other
    710    methods which mitigate the security problems inherent in this
    711    problem. In particular, user agents which cache credentials are
     710   methods that mitigate the security problems inherent in this
     711   problem. In particular, user agents that cache credentials are
    712712   encouraged to provide a readily accessible mechanism for discarding
    713713   cached credentials under user control.
Note: See TracChangeset for help on using the changeset viewer.