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

Investigate adding gzip content-encoding to node getUrl #1085

Closed
ricmoo opened this issue Oct 5, 2020 · 1 comment
Closed

Investigate adding gzip content-encoding to node getUrl #1085

ricmoo opened this issue Oct 5, 2020 · 1 comment
Labels
enhancement New feature or improvement. fixed/complete This Bug is fixed or Enhancement is complete and published.

Comments

@ricmoo
Copy link
Member

ricmoo commented Oct 5, 2020

The amount of data being returned from INFURA requires a lot of bandwidth which would benefit from gzip content-encoding. Investigate adding this.

It would likely help the other backends too.

@ricmoo ricmoo added enhancement New feature or improvement. on-deck This Enhancement or Bug is currently being worked on. labels Oct 5, 2020
@ricmoo
Copy link
Member Author

ricmoo commented Oct 8, 2020

This has been added in 5.0.17, and the AlchemyProvider and InfuraProvider have gzip enabled. Currently INFURA does not use the Accept-Encoding header, but it is on their near-term road map, and once enabled will just start working. :)

@ricmoo ricmoo closed this as completed Oct 8, 2020
@ricmoo ricmoo added fixed/complete This Bug is fixed or Enhancement is complete and published. and removed on-deck This Enhancement or Bug is currently being worked on. labels Oct 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or improvement. fixed/complete This Bug is fixed or Enhancement is complete and published.
Projects
None yet
Development

No branches or pull requests

1 participant