Update documentation for proxy usage with cloakserve and CDP connection #478
jarallahassalami
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I would like to suggest an update to the documentation to clarify the correct way to use a proxy, especially when working with the CDP server (
cloakserve) and connecting viaconnect_over_cdp.The current documentation clearly explains how to pass a proxy to the
launch()function in the Python/JS wrapper (e.g.,launch(proxy="http://...")). However, it can be confusing for users trying to use the CDP server.I attempted to pass the proxy as a query parameter in the CDP URL like this:
browser = pw.chromium.connect_over_cdp("http://localhost:9222?proxy=http://proxy:8080&geoip=true")This approach does not work, and it is not documented as an invalid method.
From my testing and understanding, the correct way is to pass the proxy to the
cloakservecommand itself using the--proxy-serverargumen :cloakserve --proxy-server=http://user:pass@proxy:8080It would be very helpful to add explicit examples to the documentation (README.md or the relevant sections) covering:
How to run
cloakservewith a proxy: Include command-line examples for both HTTP and SOCKS5 proxies.How to connect a CDP client to the proxied
cloakserveserver: Show the correct connect_over_cdp call without the proxy parameter in the URL.A note on
geoipand other flags: Clarify if and how flags like geoip can be used with cloakserve (e.g., via command-line arguments or not at all), as the current documentation might imply they work in the CDP URL.This update would prevent confusion and save time for users who, like me, assume that the proxy configuration should be part of the client-side connection string rather than the server startup configuration.
Thank you for considering this documentation improvement.
All reactions