[Pidgin] #9378: XML Parse error - disco after 3 seconds, XMPP/Jabber

[Pidgin]

#9378: XML Parse error - disco after 3 seconds, XMPP/Jabber
-----------------------------+----------------------------------------------
 Reporter:  av8or            |     Owner:  rekkanoryo
     Type:  defect           |    Status:  new       
Component:  unclassified     |   Version:  2.5.6     
 Keywords:  XML Parse error  |  
-----------------------------+----------------------------------------------
 Openfire 3.6.4 Server, XMPP/Jabber.
 Pidgin 2.5.5 and 2.5.6 client under WIN XP-Pro SP2.

 User starts up Pidgin and enters a chat room in OpenFire.  OpenFire
 replays some number of previous messages (it's a cfg option in OpenFire)
 and one contains invalid XML code.  This causes Pidgin to display 'XML
 Parse error' and disconnect from the Openfire Server.   Pidgin retries
 entry to the room (auto-login configured for one of more rooms) and the
 sequence repeats until the offending message with bad XML code is purged
 from the OpenFire 'history' replay feature.  History was set to 25
 messages on this server.

 I understand this is a known issue to some in the Pidgin community.
 I was told that the offending string in my example was:    


 One could blame the user for posting bad XML code as the trigger (believed
 to be a cut&paste from bad XML in an email that was created by some other
 evil/broken application)
 One can blame the OpenFire server for not checking XML messages that it
 passes to Pidgin.
 One could say that Pidgin is very strict in its' XML checking but that it
 should be a bit more forgiving with error recovery.

 It is this last point that I would like to explore.  Could the code be
 changed so that rather than disconnect from the XMPP/Jabber server, Pidgin
 tries to continue as best it can without a disconnect?  Maybe discard the
 offending message and post diagnostic error messages instead?

 Thanks

-- 
Ticket URL: <http://developer.pidgin.im/ticket/9378>
Pidgin <http://pidgin.im>
Pidgin