cycletls.NewTransport() to use forceHTTP1 by default #289
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… http.Client transport, for use with a custom http.client.
|
I'm not sure what you mean by http/2 being unsupported, we should be defaulting to http2. The purpose of this repo is to bypass tls/ja3 fingerprinting which runs primarily on http2 servers. The primary websites that we test against are http2 as well such as https://tls.peet.ws Happy to discuss it more on the discord https://discord.gg/gsmxMHrwhu |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR changes the default behavior of NewTransport to always use HTTP/1.x, seeing how HTTP/2 is currently unsupported.