Hello,
When dealing with the problem you reported I found that it might be that a body is required in Notifies following an unsubscribe message. I have made the changes to include this and also fixed the problem with the bad status. Please test and provide feedback.
Thanks and regards, Anca Vamanu
Pascal Maugeri wrote:
Hi
I'm doing stability testing against presence module and after "several" requests an un-subscribe request (SUBSCRIBE with Expires=0) triggers a NOTIFY with a payload and the following Subscription-State header value:
Subscription-State: active;expires=0
In my humble opinion this is incorrect as the RFC 3265 section says in section 3.3.6:
Note that the NOTIFY messages triggered by SUBSCRIBE messages with "Expires" headers of 0 will contain a "Subscription-State" value of "terminated", and a "reason" parameter of "timeout".
Ref.: http://tools.ietf.org/html/rfc3265#section-3.3.6
Best regards, Pascal
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users