[ejabberd] problem with external components

Pedro Melo melo at simplicidade.org
Fri Jun 13 13:08:09 MSD 2008


On Jun 13, 2008, at 9:57 AM, Fabio Forno wrote:

> Hi,
> I'm using ejabberd 2.0.1 and I have a little problem with the initial
> handshake of  external components.
> Accordingly to xep 114 the component should open the stream with:
> <stream:stream
>     xmlns='jabber:component:accept'
>     xmlns:stream='http://etherx.jabber.org/streams'
>     to='plays.shakespeare.lit'> <--------
> and the server should respond with:
> <stream:stream
>     xmlns:stream='http://etherx.jabber.org/streams'
>     xmlns='jabber:component:accept'
>     from='plays.shakespeare.lit' <-----
>     id='3BF96D32'>
> to and from must be the same subdomain, instead ejabberd answers with
> just from = "shakespeare.lit". After this, the routing of messages is
> correct and I can send a receive messages from the component, however
> this makes some troubles with component libraries which check the from
> attribute.

hmms... Our components just work with ejabberd, and on previous  
servers I've used the answer <stream> was always from server domain.

I think this might by a typo in the spec. It does not make much sense  
to have a from='component.domain'...

Best regards,
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: melo at simplicidade.org

More information about the ejabberd mailing list