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.

Sign up for GitHub

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

return a `406 Not Acceptable` response if a renderer matching the content negotiation headers is not available, and there is no default renderer #57

Open

DanielSchaffer opened this issue Jan 21, 2020 · 0 comments

Labels

@dandi/http-pipeline feature

Projects

Milestone

Contributor

DanielSchaffer commented Jan 21, 2020

No description provided.

DanielSchaffer created this issue from a note in v1.0.0 (To do)

DanielSchaffer added this to the v1.0.0 milestone

DanielSchaffer added @dandi/http-pipeline feature labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment