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 think some error requests are returning wrong HTTP codes... Not sure though, but according to the HTTP RFC:
When a resource is non-existent it should return a 404 Not Found response. Trying to GET /santa-claus I receive a 500 instead.
When a method is not accepted for a given resource the server should return a 405 Method Not Allowed instead of the 404 I'm currently getting. Example: PATCH /posts
The text was updated successfully, but these errors were encountered:
Actually, PATCH does work (except for #9). I said that based on conflicting doc (#5). I'm not really sure if there's any verb that's not supported by the service... Maybe it could reply 405 for, say, OPTIONS? This way we can write tests that handle correctly unsupported verbs.
I think some error requests are returning wrong HTTP codes... Not sure though, but according to the HTTP RFC:
404 Not Found
response. Trying toGET /santa-claus
I receive a 500 instead.405 Method Not Allowed
instead of the404
I'm currently getting. Example:PATCH /posts
The text was updated successfully, but these errors were encountered: