Add impersonation support for Chrome 100 and 101, drop support for Chrome 98 #64
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
.. and for Edge 101 as well. The TLS fingerprint is identical to previous versions. The HTTP headers have the usual differences in the user agents. One important change though is in the way the HTTP2 SETTINGS frame is formed. Up until Chrome 98, there was an additional randomly-generated setting in the frame. This seems to have been removed since. Therefore it was removed from curl-impersonate as well, and support for Chrome/Edge 98 was deprecated, since supporting both signatures requires a lot of work.
|
Something got messed up here in the handling of the patch file. Will repoen in a new PR. |
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.
.. and add support for Edge 101 as well. The TLS fingerprint is identical to
previous versions. The HTTP headers have the usual differences in the
user agents. One important change though is in the way the HTTP2
SETTINGS frame is formed. Up until Chrome 98, there was an additional
randomly-generated setting in the frame. This seems to have been removed
since. Therefore it was removed from curl-impersonate as well, and
support for Chrome/Edge 98 was deprecated, since supporting both
signatures requires a lot of work.
Please note: Support for Chrome/Edge 98 is removed in this PR. Supporting them in addition to the latest versions requires a lot of work, which I'm not sure is necessary. I'll leave this PR open for a day or two to see if there's any objection for them to be removed.