Hi

I'm having lots of fun hacking on Vysper :-)

In investigating to troubles with my integration tests for XMPP Ping,
I generated the following traffic between the client and the server:
Client:
<iq id="BuvmS-2" to="vysper.org" from="[email protected]"
type="get"><ping xmlns="urn:xmpp:ping"></ping></iq>

Server:
<iq to="[email protected]" from="vysper.org" type="error" id="BuvmS-2">
  <iq id="BuvmS-2" to="vysper.org" from="[email protected]" type="get">
    <ping xmlns="urn:xmpp:ping"></ping>
  </iq>
  <error type="cancel">
    <service-unavailable
xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"></service-unavailable>
  </error>
</iq>

Looking at the examples from XEP-0199, we should not include the
original <iq> element in the error response, but merely the <ping>
element, so something like:
<iq to="[email protected]" from="vysper.org" type="error" id="BuvmS-2">
  <ping xmlns="urn:xmpp:ping"></ping>
  <error type="cancel">
    <service-unavailable
xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"></service-unavailable>
  </error>
</iq>

This also seems to agree with some examples from RFC 3920, for example here:
http://xmpp.org/rfcs/rfc3920.html#bind

Should we change this?

/niklas

Reply via email to