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
I'm not really having an issue per say with this provider, but I would like to inquire into why the response codes on this provider are hard coded to 200.
In fact, the semantics of the response's HTTP status code (which codes are considered "good" or "bad") should actually be none of this http data resource's concern at all.
As a user, you make a HTTP request, then you receive a HTTP response. What's contained in that response (e.g. status code) should be the user's concern.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
I'm not really having an issue per say with this provider, but I would like to inquire into why the response codes on this provider are hard coded to 200.
if resp.StatusCode != 200
Why not the range of 200? At a min
200 | OK | [RFC7231, Section 6.3.1]
201 | Created | [RFC7231, Section 6.3.2]
202 | Accepted | [RFC7231, Section 6.3.3]
Thanks
The text was updated successfully, but these errors were encountered: