|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
2 days
|
|
|
Remaining Estimate:
|
2 days
|
|
|
Time Spent:
|
Not Specified
|
|
|
|
| Support Plan Customer Issue: |
No
|
| Resolution Date: |
06/27/08 04:05 PM
|
| Acceptance Test - Add?: |
Yes
|
| Acceptance Test - Entry: |
1. Make two BOSH requests to Openfire, so that the first one has a request id of one more than the second one's request id.
2. Openfire should respond to the latter request first, and then to the former request, gracefully.
1. Make two BOSH requests to Openfire, so that the first one has a request id of one more than the second one's request id.
2. Openfire should respond to the latter request first, and then to the former request, gracefully.
|
As stated in XEP-0124, http://www.xmpp.org/extensions/xep-0124.html#rids-order :
"When a client makes simultaneous requests, the connection manager may receive them out of order. The connection manager MUST forward the stanzas to the server and respond to the client requests in the order specified by the 'rid' attributes. The client MUST process responses received from the connection manager in the order the requests were made."
When Openfire recevies two BOSH requests out of order, i.e. the one with the greader rid arrives first, it responds to the latter with:
<body xmlns="http://jabber.org/protocol/httpbind" type="terminal" condition="item-not-found"></body>
Subsequent requests from the client will be responded with 404-Not Found, since the session is dropped.
|
|
Description
|
As stated in XEP-0124, http://www.xmpp.org/extensions/xep-0124.html#rids-order :
"When a client makes simultaneous requests, the connection manager may receive them out of order. The connection manager MUST forward the stanzas to the server and respond to the client requests in the order specified by the 'rid' attributes. The client MUST process responses received from the connection manager in the order the requests were made."
When Openfire recevies two BOSH requests out of order, i.e. the one with the greader rid arrives first, it responds to the latter with:
<body xmlns="http://jabber.org/protocol/httpbind" type="terminal" condition="item-not-found"></body>
Subsequent requests from the client will be responded with 404-Not Found, since the session is dropped. |
Show » |
| There are no comments yet on this issue.
|
|
Bug
Closed
Major
BOSH session dropped when requests are received out of order