Handle POST without Content-Length#126
Merged
Merged
Conversation
A POST with no Content-Length header (or an empty value) made CGI.new
raise TypeError/ArgumentError from Integer(nil)/Integer(""). Treat a
missing or empty length as unspecified: read the body to EOF for
url-encoded forms, and raise a clear error for multipart where the
length is required.
#56
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A POST request with no Content-Length header, or with an empty value, made CGI.new raise TypeError or ArgumentError from Integer(nil) and Integer(""). This change treats a missing or empty length as unspecified.
For url-encoded forms the body is now read to EOF. For multipart the length is required, so it raises a clear error instead of crashing.
#56