SNOW-1333163: Add support for default proxy configuration

[vc-74]

What is the current behavior?

The current HttpUtil implementation allows 2 scenarios:

• Explicitly set proxy by specifying useproxy, proxyhost... in the connection string
• Ignore proxy parameters in which case a proxy will never be used

This does not allow the default proxy scenarios, for instance:

• Getting proxy configuration from environment variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY...)
• On Windows, getting proxy configuration from WinInet, which is the only scenario supporting PAC scripts AFAIK

What is the desired behavior?

Since HttpClientHandler.UseProxy defaults to true and not specifying HttpClientHandler.Proxy will use the default proxy by default:

• If useproxy is true and proxy parameters are specified (proxyhost...) set HttpClientHandler.Proxy --> already available
• If useproxy is false, set HttpClientHandler.UseProxy to false --> already available
• If useproxy is true and no proxy parameters are specified (proxyhost...) leave HttpClientHandler.Proxy to its default value --> not available today

How would this improve snowflake-connector-net?

This would allow proxy settings from environment variables, PAC scripts... to be used to connect to Snowflake.

References, Other Background

[sfc-gh-dszmolka]

hi and again thank you for raising this as a separate Issue !

you're correct, currently the documented and supported way of setting proxies is configuring USEPROXY and the rest of the proxy settings like PROXYHOST and PROXYPORT (optionally, for authenticated proxies, the PROXYUSER and PROXYPASSWORD as well) in the connection settings.

we'll consider this improvement request for future plans. Of course if it's within your possibility to submit a PR too, that's greatly appreciated!

[vc-74]

we'll consider this improvement request for future plans. Of course if it's within your possibility to submit a PR too, that's greatly appreciated!

Done

[sfc-gh-dszmolka]

thank you ! the team will review and advise

[pgr-rick-schulte]

Can we get this issue escalated? prior to ver. 2.0.25 Proxy/No proxy setting we're working from environment variables. Perhaps you can reenable that code? We have a number of users that have not updated to the latest because of this and now Security is concerned about vulnerabilities. Proxy Settings in the connection is not our standard or manageable practice.

[sfc-gh-dszmolka]

I escalated this internally to the team but for future reference; for any important and production impacting issues or requests, the path for escalation is always your Snowflake account team as they have more context about your situation and also other tools at their disposal to help issues progress. Thank you for your understanding !

[vc-74]

@sfc-gh-dszmolka How long does it usually take for a PR to be reviewed?

[sfc-gh-dszmolka]

I cannot comment on that unfortunately, but usually should not take this much time, but again, escalated it on sunday (yesterday). If you're already a Snowflake customer, I recommend to do the same , to your account team. I regret this takes so much time, not sure about the reasons - apologies !

[pgr-rick-schulte]

It's interesting that the same behavior "removal of Proxy settings locations" happened in the SF ODBC driver around the same time . I had opened an issue with the ODBC team, and they added it back in the ODBC 3.1.4 ver. for us. It was Case#00620057.
I'm guessing there is some cross coordination between you, .Net Team and the ODBC driver would this help escalate?

[sfc-gh-dszmolka]

a quick update on this one

• someone is actively looking into this and hope i can share some progress next week
• identified the culprit to be a change between 2.0.25 and 2.1.0; so we can focus on that (the part where HTTPS_PROXY / HTTP_PROXY was picked up by the driver 2.0.25 and before, and is not picked up on or after 2.1.0)

[sfc-gh-dszmolka]

also I see PR was reviewed yesterday and some comments have been left

[pgr-rick-schulte]

Thank- you for the identifying where the change occurred