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

How to increment stream_id and change weight for Chrome persistent connections #183

Open
A-Posthuman opened this issue Sep 13, 2023 · 0 comments

Comments

@A-Posthuman
Copy link

When using this library with node-libcurl, I'd like my Chrome impersonation sessions to act as closely to the real Chrome as possible, particularly when making multiple requests using the same curl instance. The real Chrome seems to increment the stream_id in a multiplexed session as odd numbers, and the weight seems to often be 220 or 147 when requesting the sub-parts of a webpage.

My understanding (which might be wrong) of node-libcurl is that when using its asnyc "curly" object to make requests with, it is maintaining a cache of persistent connections. However when I try to test this by using a test program with single curly instance to make repeated requests to https://tls.peet.ws/api/all I don't see the stream_id incrementing.

It doesn't appear node-libcurl currently supports modifying these http2 parameters, when I try to pass it a "STREAM_WEIGHT" parameter it says it's unsupported. Anyway, wondering what might be the best approach to impersonating this aspect of Chrome, or if this project might add some features to assist with it.

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

No branches or pull requests

1 participant