You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Bernd Fondermann (JIRA)" <ji...@apache.org> on 2013/07/02 16:44:22 UTC

[jira] [Resolved] (VYSPER-329) Server To Server inbound messages in jabber:server namespace, delivery fails

     [ https://issues.apache.org/jira/browse/VYSPER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bernd Fondermann resolved VYSPER-329.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.8
    
> 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
>            Assignee: Bernd Fondermann
>            Priority: Critical
>             Fix For: 0.8
>
>         Attachments: vysper.diff
>
>   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