Bugzilla

Steps to reproduce:

To detect if the Thundebird XMPP client is still connected, a server or service can send it a 'ping' request, as specified in [XEP-0199: XMPP Ping] (https://xmpp.org/extensions/xep-0199.html)

Thunderbird supports this protocol. However, when generating a response, it incorrectly addresses the response. Instead of addressing the response to the originator of the request, it addresses it to the server that Thunderbird is connected to.

When it was the server that issued the request, then this will work as expected. However, if it is any entity (including other clients, and other services), then the requester will never receive a response.

This appears to be a simple oversight in the code. The handling of the request is very similar to handling "Version" requests, that correctly addresses the response.

This issue is related to, but not a duplicate of #1806630

Steps to reproduce:

To detect if the Thundebird XMPP client is still connected, a server or service can send it a 'ping' request, as specified in [XEP-0199: XMPP Ping] (https://xmpp.org/extensions/xep-0199.html)

Thunderbird supports this protocol. However, when generating a response, it incorrectly addresses the response. Instead of addressing the response to the originator of the request, it addresses it to the server that Thunderbird is connected to.

When it was the server that issued the request, then this will work as expected. However, if it is any entity (including other clients, and other services), then the requester will never receive a response.

This appears to be a simple oversight in the code. The handling of the request is very similar to handling "Version" requests, that correctly addresses the response.

This issue is related to, but not a duplicate of bug 1806630