I would like to find an elegant way to make sure my self-service web services connect to Azure Service Bus (threads and queues) via HTTPS - I don't want them to return to HTTP.
// this ensures that HTTP is used instead of TCP sockets.
ServiceBusEnvironment.SystemConnectivity.Mode = ConnectivityMode.Http;
The above setup ensures that TCP sockets will not be attempted, but I cannot find a way to make sure that the HTTP reserve is not used if HTTPS (SSL) is not installed.
My proxy stops the violinist from working well with the service bus, so when I pick up the violinist, he just writes a bunch of (unencrypted) HTTP traffic coming from my servers - obviously this is the opposite of what I want.
Message objects assume that URIs will be passed in the form
Endpoint=sb:
What prevents me from indicating https: // ..... Does anyone have any ideas on how and where I can prevent Service Bus from using unencrypted messages?
Interestingly (inconsistently?), The namespace manager does not seem to mind using a URL with https in it ...
var ns = NamespaceManager.CreateFromConnectionString(
"Endpoint=https://somenamespace.servicebus.windows.net/;..."
);
Update # 1: downloading a proxy, it looks like the message goes through port 80. It uses http 1.1 streams, which explains why the violinist and proxies didn't play well. A handshake occurs when azure sends the webstream address in response 201, and then TCP packets begin to receive through port 80, including information in the following form:
*sb://somenamespace.servicebus.windows.net:80/....application/ssl-tls
...
(later on)
...
http://www.microsoft.com/pki/mscorp/MSIT%20Machine%20Auth%20CA%202(1).crt
This strongly makes me suspect that TLS traffic is sent through port 80, although I would like someone to be able to confirm this.