Will Keeling

If you've imported Selenium Wire's `ca.crt` that should be enough. There may be some additional information that we're missing because it gets logged at debug level. Are you able to...

Thanks for sharing the logging. The debug message immediately after the warning indicates that the error is ``` SysCallError(10053, \'WSAECONNABORTED\') ``` That's a fairly general message indicating that the connection...

I've created a new release 4.0.5 that downgrades the warning to a debug message. I appreciate it's not a fix, but it should at least quieten the console output whilst...

Thanks for raising this. I'm not aware of a way for sites to detect the self-signed certificate, but I guess it's possible a mechanism may exist. But yes it's possible...

I'm not 100% sure exactly what in Selenium Wire is causing websites to trigger anti-bot measures, however there's a new [bot-detection feature](https://github.com/wkeeling/selenium-wire#bot-detection) in version 4.1.1 which might be worth a...

Some further info here. It seems that websites can in some cases detect that you are using Selenium Wire, even if you're using a browser implemented with measures to evade...

Yes good shout. Selenium Wire disables verification of upstream self-signed certificates by default. I'll have a look at reproducing with an upstream proxy that uses a self-signed certificate, but I'll...

@rnyPlanet thanks for linking to that issue. Yes that looks to be the cause of this problem. I'll keep an eye on the development of that issue and see how...

@jlplenio the behaviour of the `disable_capture` option has changed since my comment was added. It no longer fully disables HTTPS decryption because otherwise upstream proxy functionality won't work. With the...

@arisolt right now there is no way to do it unfortunately. Selenium Wire presents a different TLS fingerprint than a browser due to the way it uses HTTPS interception behind...