Skip to content
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

plugin.spawn does not apply proxy #47

Open
victornor opened this issue Sep 21, 2024 · 2 comments
Open

plugin.spawn does not apply proxy #47

victornor opened this issue Sep 21, 2024 · 2 comments

Comments

@victornor
Copy link

When using plugin.spawn instead of plugin.launch, the spawned instance does not use any proxy.

@dr3adx
Copy link

dr3adx commented Sep 21, 2024

When using plugin.spawn instead of plugin.launch, the spawned instance does not use any proxy.

why do you use spawn? can you explain to me the use case? im actually curious whats the purpose of this function

@victornor
Copy link
Author

When using plugin.spawn instead of plugin.launch, the spawned instance does not use any proxy.

why do you use spawn? can you explain to me the use case? im actually curious whats the purpose of this function

Js disgusts me.
So i'm running js from C# to avoid having to rewrite this lib. The js simply spawns and returns control of the cdp to C#.
I then just do my automation through playwright in C#. Might sound complicated, but it's flawless apart from this lib sometimes not applying proxy on spawn.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants