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
Have the headers changed a bit with Chrome 103? #89
Comments
I just tested Chrome 103 with Wireshark and the
Yes it changes every release.
You are correct, this is a bug with my implementation. The user-supplied headers are always added after the built-in list of headers that curl-impersonate uses. I'll open a separate issue for that.
I just tried that and the order looks fine, same as supplied in the script. Can you verify again? |
Opened #90 |
Here is what I get when manually editing the curl_chrome101 script:
|
I just tried exactly the same and I get the correct order. Is it possible that you have the |
Ahh, yes you're right I had forgotten I added that env var into my .bashrc a while back. Ok that explains it. |
Alright, I'll close this issue. We have #90 open for the libcurl-impersonate bug with the headers order. |
I checked my laptop's Windows Chrome 103 headers using your socat procedure, compared to the chrome101 curl-impersonate script's results I see extra headers for Connection:, Cache-Control:, and also DNT:. That last one might be due to my personal Chrome settings, not sure. Also the sec-ch-ua: string seems to be a bit different.
Chrome 103:
curl-impersonate chrome101:
Related question: I tried setting custom headers via node-libcurl in my program, by passing an array to my .get() method's 'HTTPHEADER' option, like below, but in the resulting request socat is showing the Connection: and Cache-Control: headers end up at the end, despite my array passing them first. Is this a curl bug? Anyway to override it to get the right order like Chrome 103?
socat result:
I tried editing the curl_chrome101 script to add these 2 headers in there, and same behavior: they end up at the bottom of the headers instead of top.
The text was updated successfully, but these errors were encountered: