[🚀 Feature]: Any WebDriver may accept user-provided HttpMessageHandler

[nvborisenko]

Description

Explaining shortly: each webdriver creates own HttpMessageHandler (represents OS network connection). It's OK for local chromedriver which starts always on new port (different story). But it is not OK when I execute hundreds of tests (webdrivers) for remote service provider (grid, browserstack..)

Revisit how to manage lifecycle of HttpMessageHandler and how configure them to be potentially reused.

Have you considered any alternatives or workarounds?

There is workaround, but it not so easy to use. Probably it is right "workaround", anyway, let explore how to improve.

[selenium-ci]

@nvborisenko, thank you for creating this issue. We will troubleshoot it as soon as we can.

Selenium Triage Team: remember to follow the Triage Guide

[nvborisenko]

Good solution for users would be cache/pool, but the tricky question when to invalidate cache... I guess we can reuse/reimplement AspNet approach.