-
Notifications
You must be signed in to change notification settings - Fork 9k
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
[Bug]: Chromium download over http proxy fails #7597
Comments
puppeteer/src/node/BrowserFetcher.ts Lines 608 to 611 in f2e1927
In our setup, the download url is https, and the proxy url is http. This line chooses whether to use the http or https module based on the protocol of the download url, not the proxy url, so it is choosing https but passing a http url. |
Actually it looks like this is a bug in https-proxy-agent |
@fairbanksg Thanks for reporting this problem. We are in the process of improving our proxy support ( |
Same problem. |
1 similar comment
Same problem. |
Same problem. |
Same problem. Using npm 8.11.0. |
Same problem. Using node 16.5.0. npm 7.19.1. |
Same |
+1 for node 16 and 18 |
Same problem. Using node 16.14.2 and npm 8.5.0 |
I worked around this by adding this to my package.json:
|
We're marking this issue as unconfirmed because it has not had recent activity and we weren't able to confirm it yet. It will be closed if no further activity occurs within the next 30 days. |
Confirming that this is still a problem. |
This line need to be fixed:
A See more here: https://stackoverflow.com/a/71482233 |
+1 would be neat if this could be fixed. |
We're marking this issue as unconfirmed because it has not had recent activity and we weren't able to confirm it yet. It will be closed if no further activity occurs within the next 30 days. |
I am unable to reproduce, it seems to be downloading fine with a proxy server I tried. The https-proxy-agent has been fixed. |
@OrKoN and this would reproduce this problem |
if you have direct connection to Chinese npm mirrors, turn off vpn and do: |
Bug description
Steps to reproduce the problem:
It appears that this is happening because we are proxying HTTPS over an HTTP proxy.
Puppeteer version
5.5.0
Node.js version
16.9.1
npm version
7.21.1 (but we use yarn, version 1.22.5)
What operating system are you seeing the problem on?
Linux
Relevant log output
The text was updated successfully, but these errors were encountered: