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

Jump to bottom

net/http: make "http: ContentLength=N with Body length 0" error message more intelligible #43650

Open
leventov opened this issue Jan 12, 2021 · 1 comment
Open

net/http: make "http: ContentLength=N with Body length 0" error message more intelligible #43650

leventov opened this issue Jan 12, 2021 · 1 comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Backlog

Comments

@leventov
Copy link

leventov commented Jan 12, 2021 •
edited

I think it would be nice to make error message more intelligible, e. g. "Request.Body's length (0) doesn't match Content-Length header (N)"

It may seem very obvious when you already know what the present error message means, but actually I couldn't understand. This SO question has 11k views and I suspect the majority of them are other confused developers.
@leventov leventov changed the title Make "http: ContentLength=N with Body length 0" error message more intelligible net/http: make "http: ContentLength=N with Body length 0" error message more intelligible Jan 12, 2021
@cagedmantis cagedmantis added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jan 15, 2021
@cagedmantis cagedmantis added this to the Backlog milestone Jan 15, 2021
@cagedmantis
Copy link
Contributor

/cc @bradfitz @empijei @neild

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
2 participants
@cagedmantis @leventov