17 Nov
2021
17 Nov
'21
7:21 p.m.
Henning Westerholt writes:
Thanks for the changes. There will be a new release
for 5.5.x next
week. Regarding back-porting, technically its a new feature that
should not be backported. On the other hand it fixes compliance with
RFC 6665 for the module. @miconda what are your thoughts on this?
RFC 6665 tells
Implementations conformant with the current specification MUST treat
an incoming 202 response as identical to a 200 response and MUST NOT
generate 202 response codes to SUBSCRIBE or NOTIFY requests.
So should default behavior be 200 response. At least new users of the
module would expect is it works according to standard out of the box.