I'm not sure about the implementation(i.e. public API probably shouldn't expose a google-specific type), but this solved the issue for my workflow.
Maybe, the new overload should take built in System.Net.IWebProxy or System.Net.Http.HttpClientHandler parameter instead, and wrap it with a factory internally, but I'm not sure if it's future-proof and covers all edge cases.
Thank you @kasthack for the contribution! I'm going to merge this into main and then update the release number to get this pushed into the next nuget release.
I'm not sure about the implementation(i.e. public API probably shouldn't expose a google-specific type), but this solved the issue for my workflow.
Maybe, the new overload should take built in
System.Net.IWebProxy
orSystem.Net.Http.HttpClientHandler
parameter instead, and wrap it with a factory internally, but I'm not sure if it's future-proof and covers all edge cases.