-
Notifications
You must be signed in to change notification settings - Fork 564
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
Add option to disable anonymizeProxy #420
Comments
Can you just try to change |
Yea I tried that. It does not work. |
I see. So you're trying to connect to an HTTP proxy over SSL, is that it? Apify SDK (internally through https://github.com/apifytech/proxy-chain package) only supports HTTPS tunneling via HTTP CONNECT method over a standard HTTP proxy. See this discussion for more details - https://stackoverflow.com/questions/45874515/what-is-https-proxy |
Right I've seen that. If the call to |
|
@jancurn I'm not sure that's true. Here, And the Edit: I think if the username/password check was moved above the scheme check it would work as I am wanting. |
Oh yeah, you're right, we'll fix this ASAP |
It's fixed in #425 |
👍 thanks! |
I'm using an https protocol proxy url and because apify forces all proxyUrls to use
anonymizeProxy()
this means I can't do it because the scheme is nothttp
.Could an option be added that disabled the
anonymizeProxy()
call? That would be awesome.I've tested with a custom
launchPuppeteerFunction
and it works, but it's not ideal because I lose all the other stuff apify does for handling puppeteer.The text was updated successfully, but these errors were encountered: