[Pidgin] #3532: Jabber does not parse correctly incomming messages

Wed Nov 21 14:32:17 EST 2007

#3532: Jabber does not parse correctly incomming messages
---------------------+------------------------------------------------------
  Reporter:  emilal  |       Owner:  seanegan          
      Type:  defect  |      Status:  assigned          
  Priority:  minor   |   Milestone:                    
 Component:  XMPP    |     Version:  2.2.1             
Resolution:          |    Keywords:  Jabber not working
   Pending:  0       |  
---------------------+------------------------------------------------------
Comment (by seanegan):

 Replying to [comment:14 emilal]:
 > (10:01:09) jabber: Recv (ssl)(321): <message to="test at gmail.com"
 type="chat" id="37"
 from="gtalk_client at gmail.com/Talk.v10454F5546A"><body>Testing Gtalk
 client</body><active xmlns="http://jabber.org/protocol/chatstates"/><nos:x
 value="disabled" xmlns:nos="google:nosave"/><arc:record otr="false"
 xmlns:arc="http://jabber.org/protocol/archive"/></message>

 This message stanza looks correct, and you should have no problem
 receiving it. The first stanza is incorrect; there's either a bug in the
 Google Talk client that's sending invalid stanzas, or a bug in the Google
 Talk server which is re-writing them (or, potentially, some sort of IM
 firewall in between that's re-writing them. Is this in a corporate
 environment where these are common?)

 I work on the Google Talk team. If you send me the account names of those
 involved (by e-mail to seanegan at google.com if you're uncomfortable giving
 them here), I can look into what's up.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/3532#comment:16>
Pidgin <http://pidgin.im>
Pidgin