[JDEV] Jabberd forgets </stream> after </stream:error>

Robert Norris rob at cataclysm.cx
Tue Feb 4 17:02:16 CST 2003

> Section 4.6 of the XMPP Core specification says:
> "If an error occurs at the level of the stream, the entity (initiating entity
> or receiving entity) that detects the error SHOULD send a stream error to the
> other entity specifying why the streams are being closed and then send a
> closing </stream> tag."
> Jabberd does not implement this behaviour properly; it sometimes closes the
> connection directly after the </stream:error> closing tag, without a final
> </stream:stream> tag.


> Is this indeed a bug that needs fixing?

Probably, but there are many places where 1.4.2 does not conform to the
XMPP spec. Since development has stopped on the 1.4 series, its unlikely
that this will be fixed (unless you want to develop a fix yourself,
which I can commit to CVS).

jabberd 2.0 aims to be fully compliant with the XMPP specs, and is under
active development.


Robert Norris                                       GPG: 1024D/FC18E6C2
Email+Jabber: rob at cataclysm.cx                Web: http://cataclysm.cx/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20030205/8379c64b/attachment-0002.pgp>

More information about the JDev mailing list