Opened 12 years ago
Closed 10 years ago
#71 closed defect (fixed)
Roster sets always fail in RosterClientProtocol
Reported by: | ff | Owned by: | ralphm |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | generic | Keywords: | |
Cc: |
Description
As discussed in this thread https://mailman.ik.nu/pipermail/twisted-jabber/2010-October/000341.html roster sets are always ignored since the test of the sender is wrong and it always fails
Change History (1)
comment:1 Changed 10 years ago by ralphm
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
(In [ea2774e1c71c]:) Clean up of RosterItem and RosterClientProtocol.
RosterItem:
RosterRequest is a new class to represent roster request stanzas.
RosterClientProtocol:
RosterPushIgnored can be raised to return a service-unavailable stanza error for unwanted pushes.
This also fixes a problem with checking the sender address for roster pushes.
Author: ralphm. Fixes: #71.