Thank you for information. Namespace problems on the s2s connection leak through to the c2s connections. I will fix this.
On 3/12/06, Robert B Quattlebaum, Jr. <[EMAIL PROTECTED]> wrote: > For the sake of keeping this issue alive, here is an example packet > that google talk will send a client: > > <cli:message xmlns:cli="jabber:client" from="[EMAIL PROTECTED]/ > powerbook" type="chat" to="[EMAIL PROTECTED]" id="iChat_54A77CFC" > > <cli:body>testing</cli:body> > <html xmlns="http://jabber.org/protocol/xhtml-im";> > <body xmlns="http://www.w3.org/1999/xhtml"; style="background- > color:#ACB5BF;color:#000000" > > <span style="font-family:Gill Sans" >testing</span> > </body> > </html> > <x xmlns="jabber:x:event"> > <composing/> > </x> > </cli:message> > > So it is using the prefixing, in several places. It would seem like a > pretty easy thing to fix. > > On Mar 9, 2006, at 11:43 AM, Gary Burd wrote: > > > On 3/9/06, Robert B Quattlebaum, Jr. <[EMAIL PROTECTED]> wrote: > >> On Mar 9, 2006, at 5:02 AM, Ralph Meijer wrote: > >>> On Thu, Mar 09, 2006 at 07:29:51AM +0100, Remko Troncon wrote: > >>>>> My friend who is using trillian says that the trillian log is > >>>>> complaining that <cli:message ...> isn't a valid top level > >>>>> stanza and > >>>>> drops it. Looks like a namespace issue of some sorts? Pandion > >>>>> doesn't > >>>>> seem to work too well either... > >>>> > >>>> As far as i know, namespaced XML elements like the one google > >>>> sends are > >>>> allowed. I never seen a client send them, but Google does, and most > >>>> off the shelf XML parsers used in clients seem to be able to > >>>> handle it. > >>> > >>> The point is that using prefixes for elements in the jabber:client > >>> namespace is specifically not allowed. This is clearly defined in > >>> section 11.2.2 of RFC 3920 (XMPP Core). > >>> > >>> If Google's implementation sends <cli:message/> where cli is a > >>> prefix > >>> for the jabber:client namespace, this is simply not compliant. Other > >>> implementations cannot be blamed for rejecting it. > >>> > >> > >> Are the Google Talk engineers monitoring this forum? This seems like > >> a rather significant issue that requires attention ASAP. > > > > I've been looking at this, but I have not been able to reproduce it. > > Some more information will help me figure out what's going on: > > > > - Time that problem was first observed. > > - Is the Trillian user logged into a @gmail.com or @googlemail.com > > account? > > - Is the sender logged into a @gmail.com or @googlemail.com account? > > - What client is the sender using? > >
