That may be exactly what is happening (the key tag is malformed), because a
key was not sent from the server - so the client is sending a malformed one
back. I should of figured that one out! :-) Apparently on earlier versions
of jabberd the key was always sent and the client expected it. Now
apparently it is optional.

Thank you!


On Mon, Mar 18, 2002 at 12:02:07PM -0500, Stephen Pendleton wrote:
> It seems that there has been a slight protocol change on the jabber.org
> development server. In particular, when registering on a gateway it used
to
> be required that a "key" was exchanged between the client and the server.
> Now it seems that the requirement has been dropped and clients that send
the
> key in the XML stream get disconnected. Unfortunately this requires that
all

Gosh, I'd say that a disconnection is a rather heavy handed approach
from the server, if that's what is really happening. Could it be
perhaps a malformed key tag (rather than just the presence of the tag)
that's causing an XML error?

Can you post some of the debug XML here at all?
cheers
dj
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev

_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev

Reply via email to