Opened 7 years ago
Last modified 6 years ago
#4812 reopened defect
XpartaMuPP doesn't use original id for responses
| Reported by: | Dunedan | Owned by: | |
|---|---|---|---|
| Priority: | Should Have | Milestone: | Backlog |
| Component: | Multiplayer lobby | Keywords: | |
| Cc: | Patch: |
Description
According to section 8.1.4 of RFC6120 response and error stanzas have to use the id of the originating query to indicate to which query they belong to:
If the generated stanza includes an 'id' attribute then it is REQUIRED for the response or error stanza to also include an 'id' attribute, where the value of the 'id' attribute MUST match that of the generated stanza.
That's not the case for XpartaMuPP, which always generates new ids for its responses (thanks Imarok for pointing that out in https://code.wildfiregames.com/D899).
Currently that behavior doesn't break anything, but a future update of ejabberd could in theory enforce the use of matching ids for requests and responses.
Change History (5)
comment:1 by , 7 years ago
| Milestone: | Backlog → Work In Progress |
|---|---|
| Patch: | → Phab:D899 |
comment:2 by , 7 years ago
| Milestone: | Work In Progress → Backlog |
|---|---|
| Patch: | Phab:D899 |
comment:4 by , 6 years ago
| Milestone: | Backlog → Alpha 23 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:5 by , 6 years ago
| Milestone: | Alpha 23 → Backlog |
|---|---|
| Resolution: | fixed |
| Status: | closed → reopened |
Argh, wrong ticket. sorry.
Sorry for the noise. Didn't notice it's a different issue from what the patch tries to solve.