view libpurple/protocols/jabber/JEPS @ 27039:9a79f8a99259

Set charset=utf-8 when cyrus sasl doesn't include it. Both deryni and my reading of the digest md5 cyrus plugin is that the response will never actually include the charset (digestmd5.c:make_client_response, look for IsUTF8). I future-proofed this code by checking for it anyway. To be polite for older servers, we might want to only send this if the server sent charset=utf-8 in the challenge (and encode everything to ISO-8859-1). However, the RFC doesn't say always sending it is wrong (and that's what the in-tree implementation does).
author Paul Aurich <paul@darkrain42.org>
date Fri, 05 Jun 2009 07:02:16 +0000
parents 5fe8042783c1
children 1c542f86dbcf
line wrap: on
line source

0045: IN PROGRESS
	Multi-User Chat
0047: IN PROGRESS
	In-Band Bytestreams
0060: NEED
	Pub-Sub
0071: AWAITING FINAL SPEC
	XHTML-IM
0073: NEED
	Basic IM Protocol Suite
0080: NEED (Do we?)
	Geographic Location Information
0084: NEED
	User Avatars in Jabber
0085: NEED
	Chat State Notifications
0089: WATCH
	Generic Alerts
0093: NEED
	Roster Item Exchange
0100: NEED
	Gateway Interaction (Transports)
0115: WATCH
	Client Capabilities
0117: NEED
	Intermediate IM Protocol Suite