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 Content-Type in request produce BadRequest #36

Open
albertVel opened this issue May 31, 2017 · 1 comment
Open

Missing Content-Type in request produce BadRequest #36

albertVel opened this issue May 31, 2017 · 1 comment

Comments

@albertVel
Copy link

Hello,

we're experiencing issues when receiving requests from a device that doesn't indicate the Content-Type in its requests. The requests are type POST and its content is application/octet-stream

As described in https://stackoverflow.com/a/15860815 the Griffin.WebServer should not return a Bad Request. Instead should try to guess the Content Type of the content or consider it as application/octet-stream.
@jgauffin
Copy link
Owner

Why kind of error do you get? Can you reproduce it?

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
@jgauffin @albertVel