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 has been archived by the owner on Mar 3, 2022. It is now read-only.
Accept-type headers - In addition to appending .json, I should also be able to send accept-type "application/json". Makes working with Backbone and other client-side libraries a lot easier.
The text was updated successfully, but these errors were encountered:
Personally I absolutely agree. I think the content-type/ accepts should be the primary, however, that creates a conflict with the .json extension (in that case, which do you choose to enforce).
For that reason I would be all for the removal of the .ext and instead rely on the accepts and content-type headers as the source of truth as intended by the HTTP specification.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Accept-type headers - In addition to appending .json, I should also be able to send accept-type "application/json". Makes working with Backbone and other client-side libraries a lot easier.
The text was updated successfully, but these errors were encountered: