…Note: The name 'charset' has been chosen for consistency with Section 2.1.1 of [RFC2831] . A better name would have been 'accept-charset', as it is not about the message it appears in, but the server's expectation. In the example below, the server prompts for authentication in th…

…Note: The name 'charset' has been chosen for consistency with Section 2.1.1 of [RFC2831] . A better name would have been 'accept-charset', as it is not about the message it appears in, but the server's expectation. In the example below, the server prompts for authentication in th…

…Note: The name 'charset' has been chosen for consistency with Section 2.1.1 of [RFC2831] . A better name would have been 'accept-charset', as it is not about the message it appears in, but the server's expectation. In the example below, the server prompts for authentication in th…

…Specification toward Draft Standard. The group has determined that DIGEST-MD5 [ RFC2831 ] is not suitable for progression on the Standards Track due to interoperability, internationalization, and security concerns. The group will deliver a technical specification for a suitable p…