Share via

2.2 Message Syntax

  • Article

The message syntax is as specified in [RFC2617] and [RFC2831].

When processing the username field, the server SHOULD<4> process "\" characters as improperly escaped "\\" characters.

The extension to this protocol consists of the use of the capability specified in [RFC2617] to add a new directive via the auth-param in the digest-challenge message ([RFC2831] section 2.1.1). The server sends: charset=utf-8 in the digest-challenge message. This indicates that the server can process UTF-8 encoded strings and that the client might use [UNICODE] encoding for the username field and in the password if it can also process UTF-8. Clients SHOULD<5> use [UNICODE] encoding when it is offered by the server to allow authentication with a region's supported character sets.