Closed tnt2k closed 1 year ago
One gets the impression that the wire itself uses the idea of proxying for the implementation of mitm.
One gets the impression that the wire itself uses the idea of proxying for the implementation of mitm.
Exactly, and Chrome doesn't allow proxychains (proxy-over-proxy)
For now, the workaround is to pass the proxies with the seleniumwire_options
as following:
wire_options = {
'proxy': {
'http': 'http://username:password@host:port',
'https': 'https://username:password@host:port',
'no_proxy': 'localhost,127.0.0.1' # excludes
}
}
mydriver = webdriver.Chrome(profile, uc_driver=True, seleniumwire_options=wire_options)
driver = mydriver.start()
See documentation
I plan to automatically pass proxies from profile["options"]["auth_proxy"]
if seleniumwire is enabled. ==> TODO
Note here, that seleniumwire
might get detected because of the different SSL-fingerprint. If you still need to intercept requests, maybe have a look at selenium-interceptor
Note here, that
seleniumwire
might get detected because of the different SSL-fingerprint. If you still need to intercept requests, maybe have a look at selenium-interceptor Exactly! I did not begin to describe the problem of pure wire, advanced proxy option in the wire we have a problem with the certificate. The wire was interested only in the possibility of modifying the response body.One gets the impression that the wire itself uses the idea of proxying for the implementation of mitm.
Exactly, and Chrome doesn't allow proxychains (proxy-over-proxy)
For now, the workaround is to pass the proxies with the
seleniumwire_options
as following:wire_options = { 'proxy': { 'http': 'http://username:password@host:port', 'https': 'https://username:password@host:port', 'no_proxy': 'localhost,127.0.0.1' # excludes } } mydriver = webdriver.Chrome(profile, uc_driver=True, seleniumwire_options=wire_options) driver = mydriver.start()
See documentation
I plan to automatically pass proxies from
profile["options"]["auth_proxy"]
if seleniumwire is enabled. ==> TODONote here, that
seleniumwire
might get detected because of the different SSL-fingerprint. If you still need to intercept requests, maybe have a look at selenium-interceptor
Exactly! I did not begin to describe the problem of pure wire, advanced proxy option in the wire we have a problem with the certificate. The wire was interested only in the possibility of modifying the response body.
Actually, let's reopen, just to not forget it:)
version == selenium-profiles 2.2.6 from pypi.org
The seleniumwire_options methods do not work when adding a proxy with authorization. In this case, the code does not end with any error, maybe I'm doing something wrong? If you comment out the
profile["options"]["auth_proxy"] = auth_proxy
line in the code below, everything works as expected.