Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider using Nancy's content negotiation #12

Open
gregoryjscott opened this issue Jul 10, 2014 · 1 comment
Open

Consider using Nancy's content negotiation #12

gregoryjscott opened this issue Jul 10, 2014 · 1 comment
Labels

Comments

@gregoryjscott
Copy link
Contributor

Currently the app is explicitly returning JSON, but might be worth considering using Nancy's content negotiation to allow other types. This will require that client's specify the type they want with a header but I think that's the correct way. I've seen an instance where someone changed the Nancy default to be JSON (if no header is present) which is something else to consider.

@junosuarez
Copy link
Member

👍 for having a default content type and also supporting other types via content negotiation. Whatever the resolution of this issue is, the supported types and response types should be documented in the readme and any other api documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants