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

[Feature request] Option to custom HTTP header in client #52

Open
retred opened this issue Dec 17, 2017 · 4 comments
Open

[Feature request] Option to custom HTTP header in client #52

retred opened this issue Dec 17, 2017 · 4 comments

Comments

@retred
Copy link

retred commented Dec 17, 2017

Hi.
Add please option custom HTTP header in client.These settings help many bypass the firewall.
User-Agent:CustomAgent
Host:CustomHost
X-Forwarded-Host:CustomHost

The current settings for bypassing the firewall are very bad -
User-Agent:Go-http-client/1.1

Please add this option.
I think to you many will say thank you.
And your program will be the best.

@jpillora
Copy link
Owner

Interesting, are you finding that Go-http-client/1.1 is blocked?

@aus
Copy link
Collaborator

aus commented Feb 9, 2019

If you are using a HTTP proxy in chisel client, the User-Agent Go-http-client/1.1 will still be exposed during the initial CONNECT request to the proxy. Unfortunately, it seems that it is not possible to customize the CONNECT request header with gorilla/websockets. I've opened an issue here.

@eliezedeck
Copy link

Not only those, but possibly others, possibilities are endless. Please integrate this feature. Thanks.

@ingnelson
Copy link

Will you add Custom HTTP header , sir ? This is important to bypass firewall .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants