sqlcmd behind http_proxy about go-sqlcmd HOT 4 CLOSED

Do you have any example applications that talk to Azure SQL DB through this same proxy?
The TDS protocol uses tcp but not http so I'm not sure what the expectation is here.
I am not a networking expert at all, though.

from go-sqlcmd.

Do you have any example applications that talk to Azure SQL DB through this same proxy? The TDS protocol uses tcp but not http so I'm not sure what the expectation is here. I am not a networking expert at all, though.

No I did not found any application talking to Azure SQL DB through this proxy.
If for example I would like to connect to an SSH Server from this same environment (behind proxy) I need to configure this:
"ProxyCommand nc -X connect -x $PROXY_IP:$PROXY_PORT %h %p" >> ~/.ssh/config

You're probably pointing me into right direction. How to check if our proxy is also handling tcp traffic?

from go-sqlcmd.

afaik you have to get your proxy owner to let port 1433 requests through instead of being redirected by the proxy.
The server requires the name in the connection string match the DNS name of the server too.

from go-sqlcmd.

Hi @shueybubbles,

thanks for your help. I finally got it working with help of this comment: dbeaver/dbeaver#4741 (comment)

It looks like if you're going through a tunnel you need to specify the username like this: export SQLCMDUSER=user@serverFQDN

If someone else finds this issue because of tunneling go-sqlcmd through a proxy this is the ncat command I used:
ncat --sh-exec "ncat --ssl $SQLCMDSERVER 1433 --proxy-type http --proxy $PROXY_IP:$PROXY_PORT" -l 14333 --keep-open &

Afterwards you should be able to connect like this:
./sqlcmd -S tcp:localhost:14333 -d $SQLCMDDATABASE -i query.sql

Envrionments Variables which need to be set:

• SQLCMDSERVER
• SQLCMDDATABASE
• SQLCMDUSER
• SQLCMDPASSWORD

from go-sqlcmd.