Fix: set accept_encoding to nil to use Typhoeus defaults. #11
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.
Problem
When using Faraday with the Typhoeus adapter, file download requests with specific content encoding types (particularly aws-chunked) were failing with Unrecognized or bad HTTP Content or Transfer-Encoding errors.
The root cause was that accept_encoding: '' explicitly disables encoding handling, which interferes with proper compression and content encoding processing by servers.
Solution
Changed accept_encoding: '' to accept_encoding: nil in the Typhoeus adapter. This allows Typhoeus to use default values and handle compression correctly while maintaining proper server communication.
Testing