Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Add support for custom http.agent. #2709

Closed
ghost opened this issue Feb 17, 2022 · 2 comments
Closed

Add support for custom http.agent. #2709

ghost opened this issue Feb 17, 2022 · 2 comments

Comments

@ghost
Copy link

ghost commented Feb 17, 2022

Using custom http.agent has been supported by web3.js and it has some many use cases.

Using proxy-agent for connecting remote nodes via SOCKS5 or HTTP proxy

web3/web3.js#887
web3/web3.js#2827

Using client ssl certiciates for http provider

web3/web3.js#2395

Many npm libraries like axios also supports using custom http.agent as well

https://github.com/axios/axios#request-config

Also, this will help with developers connecting remote nodes with some networking restrictions ( censorship, firewalls, etc ).

Also suggesting to give an ability to use custom user-agent headers to hide information about users.

@ghost
Copy link
Author

ghost commented Feb 26, 2022

Hello, what do you think for my proposal? @ricmoo

@ghost ghost changed the title Add support for custom http.agent & custom user-agent headers. Add support for custom http.agent. Feb 27, 2022
@ricmoo
Copy link
Member

ricmoo commented Mar 8, 2022

I don't know this will make it into v5, but is certainly a candidate for v6.

I'll move it to the Ideas discussion.

@ethers-io ethers-io locked and limited conversation to collaborators Mar 8, 2022
@ricmoo ricmoo converted this issue into discussion #2775 Mar 8, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant