Skip to content

browser context proxyServer #789

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

Merged
merged 1 commit into from
Jun 19, 2025
Merged

browser context proxyServer #789

merged 1 commit into from
Jun 19, 2025

Conversation

sjorsdonkers
Copy link
Contributor

@sjorsdonkers sjorsdonkers commented Jun 17, 2025

Currently we rely on there existing only 1 browser context. We just need to make sure that we set it back after the session ends

Additional:
Should we rename --http-proxy to --proxy-server to align with chromium?

@sjorsdonkers sjorsdonkers marked this pull request as draft June 17, 2025 16:18
@sjorsdonkers sjorsdonkers force-pushed the browsercontext-proxyServer branch from 3ad7936 to 6f5141d Compare June 17, 2025 16:43
Comment on lines +86 to +89
// For now the http client is not in the browser context so we assume there is just 1.
bc.http_proxy_before = cmd.cdp.browser.http_client.http_proxy;
const proxy_cp = try cmd.cdp.browser.http_client.allocator.dupe(u8, proxy);
cmd.cdp.browser.http_client.http_proxy = try std.Uri.parse(proxy_cp);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this too hacky? 🧐

@sjorsdonkers sjorsdonkers marked this pull request as ready for review June 17, 2025 16:47
@karlseguin karlseguin merged commit 0b846b1 into main Jun 19, 2025
21 checks passed
@karlseguin karlseguin deleted the browsercontext-proxyServer branch June 19, 2025 02:22
@github-actions github-actions bot locked and limited conversation to collaborators Jun 19, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants