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
{{ message }}
This repository was archived by the owner on Dec 13, 2018. It is now read-only.
Let's say I do a GET to /login when produces: application/json is set. By default, I get a 404... This makes no sense.
If I add an Accept: application/json header, then I'll get back a 200 with the JSON schema as expected.
IMO, content type and headers should NOT have any effect on whether or not a route is found.
The same goes for doing a POST request. If I don't set BOTH Accept AND Content-Type headers when POST'ing to /login, I get back a 404.
This behavior is unexpected, and I would argue that it should be changed.