Proxy dating info

Additional information could be exposed by the contents of the authentication-scheme specific parameters; this will have to be considered in the definitions of these schemes. This document updates the definitions of the "Authentication-Info" and "Proxy-Authentication-Info" header fields, so the "Permanent Message Header Field Names" registry has been updated accordingly: --------------------------- ---------- ---------- ----------------- | Header Field Name | Protocol | Status | Reference | --------------------------- ---------- ---------- ----------------- | Authentication-Info | http | standard | Section 3 of | | | | | this document | | Proxy-Authentication-Info | http | standard | Section 4 of | | | | | this document | --------------------------- ---------- ---------- ----------------- [RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L.

The presence of the header fields alone indicates that HTTP authentication is in use.

Acknowledgements This document is based on the header field definitions in RFCs 20, whose authors are: John Franks, Phillip M.

Stewart, "HTTP Authentication: Basic and Digest Access Authentication", RFC 2617, DOI 10.17487/RFC2617, June 1999, .

The Proxy-Authentication-Info response header field is equivalent to Authentication-Info, except that it applies to proxy authentication ([RFC7235], Section 2) and its semantics are defined by the authentication scheme indicated by the Proxy-Authorization header field ([RFC7235], Section 4.4) of the corresponding request: Proxy-Authentication-Info = #auth-param However, unlike Authentication-Info, the Proxy-Authentication-Info header field applies only to the next outbound client on the response chain.

The Proxy-Authentication-Info Response Header Field . This information can include a finalization message from the server (e.g., it can contain the server authentication). HTTP authentication schemes can use the Authentication-Info response header field to communicate information after the client's authentication credentials have been accepted. For backwards compatibility, authentication scheme definitions can restrict the format for senders to one of the two variants. This allows recipients to use generic parsing components, independent of the authentication scheme in use.Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents ( in effect on the date of publication of this document. This document is a product of the Internet Engineering Task Force (IETF). It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.

835 comments

Leave a Reply

Your email address will not be published. Required fields are marked *

*