[Pidgin] #13891: Invalid characters in status messages causing disconnects
Pidgin
trac at pidgin.im
Fri Apr 29 06:03:30 EDT 2011
#13891: Invalid characters in status messages causing disconnects
---------------------+------------------------------------------------------
Reporter: Natanji | Owner: deryni
Type: defect | Status: new
Milestone: | Component: XMPP
Version: 2.7.11 | Resolution:
Keywords: |
---------------------+------------------------------------------------------
Description changed by Natanji:
Old description:
> I am using Jabber with an ICQ transport. I have many contacts on ICQ, and
> some of them seem to use digsby.com from time to time. This will sadly
> set their status message to something containing illegal characters for
> XMPP, as it seems - causing Pidgin to drop the whole XMPP connection.
>
> Here is the debug output (anonymized) after which I get the disconnect:
> (11:49:40) jabber: Recv (ssl)(374): <presence to="my at jabber.address.com"
> from="123456789 at icq.jabber.address.com"><status>Available - I use
> http://digsby.com/icqutf-8</status><x
> xmlns="vcard-
> temp:x:update"><photo><![CDATA[4e038ff8350832a865e7c58761ebf825a12080dd]]></photo><hash><![CDATA[4e038ff8350832a865e7c58761ebf825a12080dd]]></hash></x></presence>
> (11:49:40) jabber: XML parser error for JabberStream 0x8c8b548: Domain 1,
> code 9, level 3: xmlParseCharRef: invalid xmlChar value 0
> (11:49:40) jabber: xmlParseChunk returned fatal 9
> (11:49:40) connection: Connection error on 0x8f7e250 (reason: 0
> description: XML Parse error)
> (...)
> (11:49:40) jabber: xmlParseChunk returned fatal 9
> (11:49:40) account: Disconnecting account my at jabber.address.com/X60t
> (0x8a8b818)
> (11:49:40) connection: Disconnecting connection 0x8f7e250
> (11:49:40) connection: Deactivating keepalive.
> (11:49:40) jabber: Sending (ssl) (my at jabber.address.com/X60t):
> </stream:stream>
> (11:49:40) connection: Destroying connection 0x8f7e250
New description:
I am using Jabber with an ICQ transport. I have many contacts on ICQ, and
some of them seem to use digsby.com from time to time. This will sadly set
their status message to something containing illegal characters for XMPP,
as it seems - causing Pidgin to drop the whole XMPP connection.
Here is the debug output (anonymized) after which I get the disconnect:
(11:49:40) jabber: Recv (ssl)(374): <presence to="my at jabber.address.com"
from="123456789 at icq.jabber.address.com"><status>Available - I use
http://digsby.com/icqutf-8</status><x
xmlns="vcard-
temp:x:update"><photo><![CDATA[4e038ff8350832a865e7c58761ebf825a12080dd]]></photo><hash><![CDATA[4e038ff8350832a865e7c58761ebf825a12080dd]]></hash></x></presence>
(11:49:40) jabber: XML parser error for JabberStream 0x8c8b548: Domain 1,
code 9, level 3: xmlParseCharRef: invalid xmlChar value 0
(11:49:40) jabber: xmlParseChunk returned fatal 9
(11:49:40) connection: Connection error on 0x8f7e250 (reason: 0
description: XML Parse error)
(...)
(11:49:40) jabber: xmlParseChunk returned fatal 9
(11:49:40) account: Disconnecting account my at jabber.address.com/X60t
(0x8a8b818)
(11:49:40) connection: Disconnecting connection 0x8f7e250
(11:49:40) connection: Deactivating keepalive.
(11:49:40) jabber: Sending (ssl) (my at jabber.address.com/X60t):
</stream:stream>
(11:49:40) connection: Destroying connection 0x8f7e250
--
--
Ticket URL: <http://developer.pidgin.im/ticket/13891#comment:1>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list