On 8/29/11 4:00 PM, Kim Alvefur wrote: > On Mon, 2011-08-29 at 15:43 -0600, Peter Saint-Andre wrote: >> On 8/29/11 11:50 AM, Kim Alvefur wrote: >>> Or act as if the client sent <foobar/>. Ie error and (maybe?) close the >>> stream. >> >> Well, <foobar/> would result in the <unsupported-stanza-type/> >> condition. Here the <auth/> element is acceptable in general, but not at >> this point in the stream. > > Is it really acceptable if it's not in <stream-features/> ? > > Also, a quick test[1] indicate the <stream:error/> behavior exists in > the wild. > > 1: M-Link on jabber.org says not-authorized, and my Prosody instance > says unsupported-stanza-type.
I see your point. Given that the initiating entity is attempting to send a first-level child element that is not appropriate for this stream context, I think <unsupported-stanza-type/> is the right error. Peter -- Peter Saint-Andre https://stpeter.im/ _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
