Skip to content
This repository has been archived by the owner on Mar 3, 2022. It is now read-only.

Accept-type headers #4

Open
bryanhirsch opened this issue Feb 1, 2013 · 1 comment
Open

Accept-type headers #4

bryanhirsch opened this issue Feb 1, 2013 · 1 comment

Comments

@bryanhirsch
Copy link
Contributor

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.

@mikestowe
Copy link

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants