Don't use #eof? when parsing multipart #1201
Merged
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.
On chunked requests (
Transfer-Encoding: chunked
) content length won't be present, so#eof?
will be called on the Rack input directly. However, the Rack input doesn't have to respond to#eof?
, it's not part of the Rack specification. For example,Rack::Lint::InputWrapper
andUnicorn::StreamInput
don't respond to#eof?
. This means that in development and on Unicorn, multipart parsing will fail for chunked requests.This change refactors the multipart parser so that it doesn't call
#eof?
.