Thread: [Jwchat-devel] A couple problems with jwchat.
Status: Beta
Brought to you by:
zeank
Menu
▾
▴
jwchat-devel
|
From: Sean D. <se...@du...> - 2008-07-16 13:56:57
|
I'm currently working on setting up jwchat for our environment, but I"m running into a few problems. I'm using apache 2.2 and ejabberd 2.0.1. These are problems I first saw with jwchat 1.0beta3, so I upgraded to CVS on July 14 and I'm still seeing the same problems. The first problem is that when I open a chat window and type into it, the recipient never receives the IM. This seems to work in some cases, but not others. The place I can consistently get it to fail is using Firefox 3 as my browser on Linux (CentOS 5 specifically). Does anyone know how to resolve this issue? The other problem is I keep getting 404 errors in my logs for the file 'xmlextras.js'. Is this a bug in that jwchat is asking for the file? Or am I missing a file that needs to be installed? Thanks, Sean |
|
From: Stefan S. <st...@ze...> - 2008-07-16 14:57:08
|
Sean, Am Mittwoch, den 16.07.2008, 09:56 -0400 schrieb Sean Dilda: > The first problem is that when I open a chat window and type into it, > the recipient never receives the IM. This seems to work in some cases, > but not others. The place I can consistently get it to fail is using > Firefox 3 as my browser on Linux (CentOS 5 specifically). Does anyone > know how to resolve this issue? Sorry, don't know what could be the problem here. Did you try turning on debugging or checking the actual network traffic? Firebug is a good extension for Firefox to track down such problems btw. > The other problem is I keep getting 404 errors in my logs for the file > 'xmlextras.js'. Is this a bug in that jwchat is asking for the file? > Or am I missing a file that needs to be installed? The file doesn't exist anymore as of latestest versions of jsjac. But obviously it's still referenced somewhere within jwchat. But actually that's nothing to worry about. Cheers, Steve |
|
From: Sean D. <se...@du...> - 2008-07-16 18:10:55
|
Stefan Strigler wrote: > Sean, > > Am Mittwoch, den 16.07.2008, 09:56 -0400 schrieb Sean Dilda: > >> The first problem is that when I open a chat window and type into it, >> the recipient never receives the IM. This seems to work in some cases, >> but not others. The place I can consistently get it to fail is using >> Firefox 3 as my browser on Linux (CentOS 5 specifically). Does anyone >> know how to resolve this issue? > > Sorry, don't know what could be the problem here. Did you try turning on > debugging or checking the actual network traffic? Firebug is a good > extension for Firefox to track down such problems btw. I did a tcpdump between apache and ejabberd. This is what I found: From FF3: <body rid='622713' sid='cb299709563672ae8bc7029ecd56f7f803fb065c' xmlns='http://jabber.org/protocol/httpbind' key='436543e9f153c5c93c30001162640c0dff7e9944' ><message xmlns="jabber:client" type="chat" to="XX...@gm..."><body xmlns="">test</body></message></body> From FF2: <body rid='662313' sid='bbc2d1ec433ef298f546bc9ecd37a471bad0125e' xmlns='http://jabber.org/protocol/httpbind' key='5494dff971ceb080dd8cf28b132ba4089b342fff' ><message xmlns="jabber:client" type="chat" to="XX...@gm..."><body>test</body></message></body> The key difference seems to be that with FF3, the body tag (inside the message tag) is setting 'xmlns=""'. In FF2 it isn't doing that. I mimiced this difference using the XMPP console in pidgin and found that ejabberd quietly passes the message on, but pidgin ignores the incoming message that has the xmlns set in the body tag. > >> The other problem is I keep getting 404 errors in my logs for the file >> 'xmlextras.js'. Is this a bug in that jwchat is asking for the file? >> Or am I missing a file that needs to be installed? > > The file doesn't exist anymore as of latestest versions of jsjac. But > obviously it's still referenced somewhere within jwchat. But actually > that's nothing to worry about. > Thanks. I'll just patch my copy to remove those lines then. I can send you a copy of the patch if you like, although its a pretty basic change. |
|
From: Sean D. <se...@du...> - 2008-07-17 17:06:17
Attachments:
jwchat-noxmlextras.patch
|
Stefan Strigler wrote: >> Thanks. I'll just patch my copy to remove those lines then. I can >> send you a copy of the patch if you like, although its a pretty basic >> change. > > Sure, if you could send me a patch (against latest from CVS) that'd be > great. Saves me some work. > The patch is attached. |
|
From: Stefan S. <st...@ze...> - 2008-07-23 13:22:18
|
Thanks a lot. I've commited your patch to jwchat's CVS repository. Cheers, Steve Am Donnerstag, den 17.07.2008, 13:06 -0400 schrieb Sean Dilda: > Stefan Strigler wrote: > > >> Thanks. I'll just patch my copy to remove those lines then. I can > >> send you a copy of the patch if you like, although its a pretty basic > >> change. > > > > Sure, if you could send me a patch (against latest from CVS) that'd be > > great. Saves me some work. > > > > > The patch is attached. > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ JWChat-devel mailing list JWC...@li... https://lists.sourceforge.net/lists/listinfo/jwchat-devel |
|
From: Sean D. <se...@du...> - 2008-11-21 16:41:50
|
Stefan Strigler wrote: > Hi, > > Am Mittwoch, den 16.07.2008, 14:10 -0400 schrieb Sean Dilda: > > [...] > >> The key difference seems to be that with FF3, the body tag (inside the >> message tag) is setting 'xmlns=""'. In FF2 it isn't doing that. >> >> I mimiced this difference using the XMPP console in pidgin and found >> that ejabberd quietly passes the message on, but pidgin ignores the >> incoming message that has the xmlns set in the body tag. > > Oh I see. Thanks for tracing this down. This is a major problem then. > > I've filed a bug report at > https://trac.stefan-strigler.de/jsjac/ticket/46 and I'll try to fix it > ASAP. > This link doesn't seem to work anymore. Does anyone know what the status of this bug is? |
|
From: Stefan S. <st...@ze...> - 2008-11-24 09:51:56
|
Hi, Am Freitag, den 21.11.2008, 11:41 -0500 schrieb Sean Dilda: > > I've filed a bug report at > > https://trac.stefan-strigler.de/jsjac/ticket/46 and I'll try to fix it > > ASAP. > > > > This link doesn't seem to work anymore. Does anyone know what the > status of this bug is? The URL has changed, it's https://trac.jwchat.org/jsjac/ticket/46 now. But I'll try to make redirects work again. Btw the Bug is fixed at rev474 but there's no new release yet. Cheers, Steve |
|
From: Stefan S. <st...@ze...> - 2008-07-17 06:15:06
|
Hi, Am Mittwoch, den 16.07.2008, 14:10 -0400 schrieb Sean Dilda: [...] > The key difference seems to be that with FF3, the body tag (inside the > message tag) is setting 'xmlns=""'. In FF2 it isn't doing that. > > I mimiced this difference using the XMPP console in pidgin and found > that ejabberd quietly passes the message on, but pidgin ignores the > incoming message that has the xmlns set in the body tag. Oh I see. Thanks for tracing this down. This is a major problem then. I've filed a bug report at https://trac.stefan-strigler.de/jsjac/ticket/46 and I'll try to fix it ASAP. > Thanks. I'll just patch my copy to remove those lines then. I can > send you a copy of the patch if you like, although its a pretty basic > change. Sure, if you could send me a patch (against latest from CVS) that'd be great. Saves me some work. Cheers, Steve |
Thanks for helping keep SourceForge clean.
X