Windows support about devtools-proxy HOT 5 OPEN

Yes, you're right. The Proxy itself (proxy.py) is fully compatible with Windows already. The thing that is incompatible with Windows is a Chrome wrapper (chrome-wrapper.sh). I see 2 possible solutions:

• write chrome-wrapper.bat (or .ps1) which will work the same as chrome-wrapper.sh does.
• write chrome-wrapper.py in Python and replace chrome-wrapper.sh with it. Then there is no need to support 2 different wrappers for different systems (I prefer this way, to be honest, but it will require more time).

from devtools-proxy.

Will try to run it on Linux and understand how it works, then will try to create bat first. If I am not mistaken, by using chrome-wrapper as binary in ChromeOptions, we still should set the path to chrome driver binary as well?

from devtools-proxy.

we still should set the path to chrome driver binary as well?

Did you mean Chrome (not chrome driver)? If so, then it's not required, In the wrapper, I've tried to mimic chromedriver's heuristic for finding Chrome's binary. But if you want to use custom binary (which is not in default locations), you can add an argument --chrome-binary to ChromeOptions' args.

from devtools-proxy.

I meant chrome driver

from devtools-proxy.

devtools-proxy doesn't require any changes of chromedriver usage (it requires only additional parameters in ChromeOptions). So if you set it without proxy, then you need to set it with the proxy.

from devtools-proxy.