[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bug: RFC2831 noncompliance - "charset=utf-8" in challenge REQUIRES "char
From: |
marty |
Subject: |
Bug: RFC2831 noncompliance - "charset=utf-8" in challenge REQUIRES "charset=utf-8" in response |
Date: |
Mon, 24 Mar 2008 10:06:13 -0400 |
User-agent: |
Thunderbird 2.0.0.12 (Windows/20080213) |
This bug was encountered using
jabberd2 2.1.23 w/ GSASL 0.2.25
Pidgin 2.4.0 (Cyrus-based SASL)
In summary, the issue is that jabberd2 (as a consequence of gsasl)
indicates support for "charset=utf-8" in the challenge, and then
consequently _requires_ that the response contain a "charset=utf-8"
directive. This expectation is contrary to the RFC, which only states
that the "charset=utf-8" directive in the challenge indicates server
support for _optional_ utf-8 encoding of the response.
For details, please refer to the following:
(bug against jabberd2)
http://jabberd2.xiaoka.com/ticket/200
(original bug against Pidgin)
http://developer.pidgin.im/ticket/5213
- Bug: RFC2831 noncompliance - "charset=utf-8" in challenge REQUIRES "charset=utf-8" in response,
marty <=