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

net/http fixes #36056

Closed
rocketdv opened this issue Dec 9, 2019 · 3 comments
Closed

net/http fixes #36056

rocketdv opened this issue Dec 9, 2019 · 3 comments

Comments

@rocketdv
Copy link

rocketdv commented Dec 9, 2019

What version of Go are you using (go version)?

$ go version
go version go1.13.4 windows/amd64

Suggestions for net/http

  • allow for header order to match the order in which they were added, currently it sorts them alphabetically, and this can be fingerprinted very easily when web scraping and causes me to get blocked sometimes
  • implement cronet or at least tls grease cipher, this will also stop me from getting blocked, some sites check what ciphers were sent
@rocketdv rocketdv changed the title net/http fixes net/http fixes Dec 9, 2019
@bradfitz
Copy link
Contributor

bradfitz commented Dec 9, 2019

Header order was #24375 (closed).

TLS ciphers are not part of the net/http package.

You could probably define your own Transport.DialTLS func that shells out to openssl s_client if you really needed to.

Closing, as there's nothing for me to do here.

@bradfitz bradfitz closed this as completed Dec 9, 2019
@rocketdv
Copy link
Author

rocketdv commented Dec 9, 2019

will header order ever be supported

@bradfitz
Copy link
Contributor

bradfitz commented Dec 9, 2019

If the right design emerges or we redo a bunch of the APIs and get to make new decisions.

@golang golang locked and limited conversation to collaborators Dec 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants