| commit | 66c385611737fe9e606f80b7949985fd4962a302 | |
| author | Stefan Becker <chemobejk@gmail.com> | |
| Mon, 3 Jun 2013 20:11:22 +0000 (3 23:11 +0300) | ||
| committer | Stefan Becker <chemobejk@gmail.com> | |
| Mon, 3 Jun 2013 20:17:42 +0000 (3 23:17 +0300) | ||
| tree | fbf096d44fb45e0ff594a54a4314941cea9b7a53 | treesnapshot (tar.gz zip) |
| parent | 0ab7cf957d05cf909318de252ac1b5b68f5d68e6 | commitdiff |
subscriptions: fix handling of "resubscribe" notify
I noticed that one of my buddy list entries triggered a "resubscribe"
notification. The single subscription to that buddy triggered another
"resubscribe" notificiation, causing an endless ping-pong.
After comparing the messages from the debug log with the examples from
[MS-PRES] it turned out that the re-subscription message should not have
these headers:
Require: adhoclist, categoryList
Supported: eventlist
I noticed that one of my buddy list entries triggered a "resubscribe"
notification. The single subscription to that buddy triggered another
"resubscribe" notificiation, causing an endless ping-pong.
After comparing the messages from the debug log with the examples from
[MS-PRES] it turned out that the re-subscription message should not have
these headers:
Require: adhoclist, categoryList
Supported: eventlist
| src/core/sipe-subscriptions.c | diffblobblamehistory |