Snowflake’s .NET driver documents proxy support from version 2.0.4. Add its proxy fields to the application’s existing connection configuration:

var settings =
    new Snowflake.Data.Client.SnowflakeDbConnectionStringBuilder();
settings.ConnectionString = existingConnectionString;

settings["useProxy"] = true;
settings["proxyHost"] = "proxy.example.net";
settings["proxyPort"] = 8080;

var connection = new Snowflake.Data.Client.SnowflakeDbConnection
{
    ConnectionString = settings.ConnectionString
};

existingConnectionString contains the application’s normal Snowflake account and authentication settings. Configure the connection before opening it.

proxyHost is a hostname. The port is supplied separately; do not insert http:// into the host field or repeat :8080 there. For a permitted public-proxy route to Snowflake, the HTTP proxy list provides candidate host and port values; it supplies no proxy account.

If the intermediary requires an account, add proxyUser and proxyPassword through the builder from the application’s credential source. A connection-string builder handles delimiters in values more reliably than concatenating raw passwords into a string.

Keep the driver’s NONPROXYHOSTS syntax separate from another client’s NO_PROXY grammar. Snowflake’s documented patterns are matched against URLs and support their own wildcard form.

Ũhoro ũhĩtĩte