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.

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

Jump to bottom

Missing "Accept" header should not cause 406 response by default #317

Closed
aeronite opened this issue Feb 6, 2018 · 2 comments
Closed

Missing "Accept" header should not cause 406 response by default #317

aeronite opened this issue Feb 6, 2018 · 2 comments

Comments

@aeronite
Copy link

aeronite commented Feb 6, 2018

This is the same issue as #38
It seems the problem has since resurfaced
@orangy
Copy link
Contributor

orangy commented Feb 7, 2018

We are working on it in #312

@orangy orangy closed this as completed in 66ddfe5 Feb 7, 2018
@aeronite
Copy link
Author

aeronite commented Feb 7, 2018

Awesome thanks

@soywiz soywiz mentioned this issue Mar 28, 2018
Closed
schleinzer pushed a commit to schleinzer/ktor that referenced this issue Feb 26, 2019
@orangy
Change ContentNegotiation to allow missing Accept header and treat it…
7b4165f 
… as "*/*".

Fixes ktorio#317
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@orangy @aeronite