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

POST with content should be 400 #129

Closed
ronag opened this issue May 18, 2018 · 4 comments
Closed

POST with content should be 400 #129

ronag opened this issue May 18, 2018 · 4 comments

Comments

@ronag
Copy link
Contributor

ronag commented May 18, 2018

If performing POST with content-length the server should reply 400?
@Acconut
Copy link
Member

Acconut commented May 20, 2018

Yes, 400 is a good status code in this case if the Content-Length is non-zero.

@ronag
Copy link
Contributor Author

ronag commented May 21, 2018

Related to #104.

@Acconut: If I make a PR with updates in regards to failure modes will you have time to review and merge? Also, would that be interesting at all?

@Acconut
Copy link
Member

Acconut commented May 23, 2018

Yes, that would be grad. Please incorporate those failure modes as non-mandatory suggestions so this is not a breaking change.

@Acconut
Copy link
Member

Acconut commented Oct 2, 2019

Closing this since #88 will allow POST requests with content.

@Acconut Acconut closed this as completed Oct 2, 2019
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
@Acconut @ronag