…on of RFC5234 ]. Additionally, the following rules are included from HTTP/1.1 [ RFC2617 ]: auth-param and auth-scheme; and from "Uniform Resource Identifier (URI): Generic Syntax" [ RFC3986 ]: URI-reference. Unless otherwise noted, all the protocol parameter names and values are …

…ion of [RFC5234]. Additionally, the following rules are included from HTTP/1.1 [RFC2617]: auth-param and auth-scheme; and from "Uniform Resource Identifier (URI): Generic Syntax" [RFC3986]: URI-reference. Unless otherwise noted, all the protocol parameter names and values are cas…

…on of RFC5234 ]. Additionally, the following rules are included from HTTP/1.1 [ RFC2617 ]: auth-param and auth-scheme; and from "Uniform Resource Identifier (URI): Generic Syntax" [ RFC3986 ]: URI-reference. Unless otherwise noted, all the protocol parameter names and values are …

…on of RFC5234 ]. Additionally, the following rules are included from HTTP/1.1 [ RFC2617 ]: auth-param and auth-scheme; and from "Uniform Resource Identifier (URI): Generic Syntax" [ RFC3986 ]: URI-reference. Unless otherwise noted, all the protocol parameter names and values are …

…tion mechanism. This document extends but is generally backward compatible with RFC2617 ]. See Appendix A for the new capabilities introduced by this specification. The details of the challenge-response authentication mechanism are specified in the "Hypertext Transfer Protocol (H…

…tion mechanism. This document extends but is generally backward compatible with RFC2617 ]. See Appendix A for the new capabilities introduced by this specification. The details of the challenge-response authentication mechanism are specified in the "Hypertext Transfer Protocol (H…

…se exchange inspired by (but differing in details) to the one defined for HTTP [RFC2617]. In the short-term credential mechanism, the client and the server exchange a username and password through some out-of-band method prior to the STUN exchange. For example, in the ICE usage […

…e exchange inspired by (but differing in details) to the one defined for HTTP [ RFC2617 ]. In the short-term credential mechanism, the client and the server exchange a username and password through some out-of-band method prior to the STUN exchange. For example, in the ICE usage …

…sic, Digest, NTLM and Negotiate (SPNEGO). The first two options were defined in RFC2617 [ RFC2617 ], and are stateless. The second two options were developed by Microsoft and specified in RFC4559 [ RFC4559 ], and are stateful; otherwise known as multi-round authentication, or con…

…e exchange inspired by (but differing in details) to the one defined for HTTP [ RFC2617 ]. In the short-term credential mechanism, the client and the server exchange a username and password through some out-of-band method prior to the STUN exchange. For example, in the ICE usage …

… a client password MAY use the HTTP Basic authentication scheme as defined in [ RFC2617 ] to authenticate with the authorization server. The client identifier is encoded using the "application/x-www-form-urlencoded" encoding algorithm per Appendix B , and the encoded value is use…

…e exchange inspired by (but differing in details) to the one defined for HTTP [ RFC2617 ]. In the short-term credential mechanism, the client and the server exchange a username and password through some out-of-band method prior to the STUN exchange. For example, in the ICE usage …

… a client password MAY use the HTTP Basic authentication scheme as defined in [ RFC2617 ] to authenticate with the authorization server. The client identifier is encoded using the "application/x-www-form-urlencoded" encoding algorithm per Appendix B , and the encoded value is use…

…for this scheme follows the usage of the Basic scheme defined in Section 2 of [ RFC2617 Note that, as with Basic, it does not conform to the generic syntax defined in Section 1.2 of [ RFC2617 but is compatible with the general authentication framework in HTTP 1.1 Authentication R…

… a client password MAY use the HTTP Basic authentication scheme as defined in [ RFC2617 ] to authenticate with the authorization server. The client identifier is encoded using the "application/x-www-form-urlencoded" encoding algorithm per Appendix B , and the encoded value is use…