Currently we require a 200 status code for events and a 202 for sessions but there's no need to be so specific as any 2xx status indicates success
Now we only warn on codes outside of the 2xx range, unless a specific code has been set in options['success']. If a specific code is given then it must match exactly, i.e. it has the same behaviour as before
This generally shouldn't affect users as the event & session endpoints always respond with 200 & 202 but can prevent spurious warnings if delivering to a custom service that doesn't use the same codes (e.g. a forwarding agent)
Goal
Currently we require a 200 status code for events and a 202 for sessions but there's no need to be so specific as any 2xx status indicates success
Now we only warn on codes outside of the 2xx range, unless a specific code has been set in
options['success']. If a specific code is given then it must match exactly, i.e. it has the same behaviour as beforeThis generally shouldn't affect users as the event & session endpoints always respond with 200 & 202 but can prevent spurious warnings if delivering to a custom service that doesn't use the same codes (e.g. a forwarding agent)