Prosody's BOSH terminate not compatible with JSJaC

baiwyc119 / lxmppd

Automatically exported from code.google.com/p/lxmppd

0 stars 0 forks source link

Prosody's BOSH terminate not compatible with JSJaC #211

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Closing an User Session while using CORS and JsJac based apps

What is the expected output? What do you see instead?
Prosody is expected to send out the following xml string:
<body xmlns="http://jabber.org/protocol/httpbind"/>
While instead it sends out an empty reply.

What version of the product are you using? On what operating system?
Prosody Nightly 0.8 build 7

Original issue reported on code.google.com by maranda3...@gmail.com on 8 Sep 2010 at 12:46

GoogleCodeExporter commented 9 years ago

Forgot to add the following detail: While using a cross domain request.

Original comment by maranda3...@gmail.com on 8 Sep 2010 at 12:50

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

or <body type='terminate' condition='item-not-found' 
xmlns='http://jabber.org/protocol/httpbind'/> for what regards the xml string 
expected.

Original comment by maranda3...@gmail.com on 8 Sep 2010 at 1:21

GoogleCodeExporter commented 9 years ago

The issue is with JSJaC, which was designed against ejabberd. It has the same 
issue with Tigase for example.

A recent BOSH ML thread on the issue: 
http://mail.jabber.org/pipermail/bosh/2010-September/thread.html#340

Basically Prosody sends the terminate on the second to last request, while 
ejabberd sends it on the last. This causes a javascript exception in JSJaC.

Possible Prosody side issue: Prosody may not be holding on to the last request, 
on which I think it should reply immediately on terminate.

Original comment by waqas20 on 8 Sep 2010 at 2:28

Changed title: Prosody's BOSH terminate not compatible with JSJaC
Changed state: Accepted

GoogleCodeExporter commented 9 years ago

Do you have an example page I can use for testing? item-not-found is not an 
error that can be given to the second-to-last request, since it relates to the 
sid, meaning the session has expired.

Original comment by MWild1 on 10 Sep 2010 at 5:04

GoogleCodeExporter commented 9 years ago

Fixed in http://prosody.im/changesets/9fb6e8ec15ed

Original comment by MWild1 on 4 Mar 2011 at 8:29

Changed state: Fixed