comparison ChangeLog @ 27020:a0e3e4f37702

disapproval of revision '84a23ef59e6a3bc88834f0948c67516f0a39234b' Conversation in devel@c.p.i leads to deryni saying: Ok, if we send charset=utf-8 then we need to have sent a utf8 username and realm in digest-response but need to have used iso8859-1 versions of them when calculating response-value (if they are valid iso8859-1). I think. which is what the code was doing before.
author Paul Aurich <paul@darkrain42.org>
date Wed, 03 Jun 2009 19:34:26 +0000
parents e696a0740a85
children 2f297ab00e9d
comparison
equal deleted inserted replaced
27015:e696a0740a85 27020:a0e3e4f37702
48 * Support custom smileys in MUCs (only when all participants support the 48 * Support custom smileys in MUCs (only when all participants support the
49 "Bits of Binary" extension, and a maximum of 10 participants are in the 49 "Bits of Binary" extension, and a maximum of 10 participants are in the
50 chat to avoid getting too many fetch requests). 50 chat to avoid getting too many fetch requests).
51 * Fix an issue with Jabber (pre-XMPP) servers and the user's preference 51 * Fix an issue with Jabber (pre-XMPP) servers and the user's preference
52 to require SSL not being respected. 52 to require SSL not being respected.
53 * When using non-Cyrus SASL DIGEST-MD5 authentication, only specify the
54 charset as UTF-8 if the username/password weren't converted to ISO-8859-1.
55 53
56 Yahoo: 54 Yahoo:
57 * P2P file transfers. (Sulabh Mahajan) 55 * P2P file transfers. (Sulabh Mahajan)
58 * Sending text messages (address to +<countrycode><phone number>). 56 * Sending text messages (address to +<countrycode><phone number>).
59 (Sulabh Mahajan) 57 (Sulabh Mahajan)