Hi, thanks for the quick responses. I'm replying here though Guus has a very good argumentation about the reasoning behind this behavior.
Am Dienstag, den 13.09.2005, 15:01 +0200 schrieb Alexander Gnauck: > Stefan Strigler schrieb: > > Or let me rephrase to make it more clearly: A client may use > > authentication based on jabber:iq:auth only if it didn't supply a > > version attribute within the opening stream tag? > > yes you are right. Then there is a problem with HTTP Binding, as it is up to the connection manager to send a stream tag if it's implemented as a proxying connection manager. Thus a client is not able to decide which direction to take. :( I guess it's better to switch to standards-jig now ... Cheers, Steve
