[
https://issues.apache.org/jira/browse/VYSPER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471606#comment-13471606
]
Justin Spears commented on VYSPER-329:
--------------------------------------
<message type="chat" id="purpleab223b79"
to="user@justins-imac/58df469512514b81a8f0aaabcf2e15d8"
from="justin@jive/Justins-iMac"><active
xmlns="http://jabber.org/protocol/chatstates"/><body>s2s</body></message>
Sorry about the previous capture it was taken from the openfire logs it wraps
each xmpp packet in a packet tag...
This was obtained by packet capture using adium as the client. Again no
namespace in the incoming message xml.
> Server To Server inbound messages in jabber:server namespace, delivery fails
> ----------------------------------------------------------------------------
>
> Key: VYSPER-329
> URL: https://issues.apache.org/jira/browse/VYSPER-329
> Project: VYSPER
> Issue Type: Bug
> Components: server-to-server
> Affects Versions: 0.8
> Reporter: Justin Spears
> Priority: Critical
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> When recieving messages from external servers, if the message is in the
> jabber:server namespace the message is not recognized and is sent to the
> ServiceUnavailableHandler. This includes all IQ/Presence/... messages.
> This was discovered testing against Openfire 3.2. According to a quick look
> of the rfc these should be accepted.
> Easy fix it is to change XMPPCoreStanzaHandler to check for either namespace
> protected boolean verifyNamespace(Stanza stanza) {
> String namespaceUri = stanza.getNamespaceURI();
> return NamespaceURIs.JABBER_SERVER.equals(namespaceUri) ||
> NamespaceURIs.JABBER_CLIENT.equals(namespaceUri);
> }
> I am not entirely sure this the correct way to handle it... but it works.
> It should also log at least debug level when StanzaHandlerLookup returns
> SERVICE_UNAVAILABLE_STANZA_ERROR_HANDLER it would have saved days of
> debugging.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
