You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Sometimes 404 or 301 response code is considered successful for an unusual endpoint.
It's possible that only 200 response is expected and 204 should be rejected.
Currently, _success transition is returned from HttpAction whenever response code is between 200 and 300.
Describe the solution you'd like
Configurable _success response codes, e.g.:
Is your feature request related to a problem? Please describe.
Sometimes
404
or301
response code is considered successful for an unusual endpoint.It's possible that only
200
response is expected and204
should be rejected.Currently,
_success
transition is returned from HttpAction whenever response code is between200
and300
.Describe the solution you'd like
Configurable
_success
response codes, e.g.:or provided in a different format. Interval support would be appreciated.
Describe alternatives you've considered
Currently no good alternative. Subsequent
_success
or_error
action has to handle the ambiguity.Additional context
Desired behaviour could be achieved if #128 was implemented.
The text was updated successfully, but these errors were encountered: