[Pidgin] #9015: INCORRECT IMPLEMENTATION OF XMPP PING

[Pidgin]

#9015: INCORRECT IMPLEMENTATION OF XMPP PING
-------------------------+--------------------------------------------------
 Reporter:  niraj19july  |     Owner:  deryni
     Type:  defect       |    Status:  new   
Component:  XMPP         |   Version:  2.5.5 
 Keywords:               |  
-------------------------+--------------------------------------------------
 Pidgin 2.4.x and 2.5.x have started supporting XEP-0199 : XMPP Ping.
 As per xep, if a pinged entity doesn't support the ping namespace it MUST
 return a service-unavailable error as follows:

 <iq from='juliet at capulet.lit/chamber'
     to='chat.shakespeare.lit'
     id='comp1'
     type='error'>
   <ping xmlns='urn:xmpp:ping'/>
   <error type='cancel'>
     <service-unavailable xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
   </error>
 </iq>

 However, even if server sends the error, pidgin considers it to be the
 response of the ping and keeps the connection alive. Ideally, when xmpp
 ping support is not discovered by Service Discovery or when server sends
 error response to ping request then client must disable the pings, which
 it uses as a keep alive mechanism, to detect that server is no longer
 responding. Once the ping is disable, client can instead use TCP pings.

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