Skip to main content

Azure Service Bus Topics - How communication works over HTTP (80,443)

By
In this topic we will talk about different protocols and ports that can be used to communicate between our machines and Azure Service Bus Topics.
The communication between Azure Service Bus Topic and our machines we can use:
  • AMQP (new and hot)
  • TCP/IP
  • HTTP
For TCP/IP connection is pretty clear what ports are used (9351 and 9552). It seems that 9351 is used for inbound traffic and 9552 is used for outbound traffic (this ports may change)

The interesting discussion is when we are taking about HTTP. The communication over HTTP protocol is done over two ports - 443 and 80.
Each port is used for specific use case:
  • 80:   is used for outbound traffic
  • 443: is used for inbound traffic
This means that when we are listening to a subscription we will use port 80 to check if a message is available. The same port will be used to receive the message from subscription. 
The port 443 is used when we need to send messages to topic. Each time when we send a message to a topic, the message is send over 443 without exception. 

For both ports (80 and 443), the communication is done done using a TLS/SSL. Even if port 80 is used, the communication is secure - inside a tunnel. No data in clear are send between our application and Azure Service Bus.
It is important to know that Azure Service Bus doesn't supports unsecure connection. All the communication will be done over a secure tunnel.


If the connectivity mode is not change (AutoDetect), the Azure Service Bus library will try to use TCP/IP connection. If the connection cannot be established using the 9XXX ports, it will fall back automatically to HTTP ports.
We have the possibility to specify directly what kind of connectivity mode we want to use (AutoDetect/TCP/HTTP). This is useful when we already know the connectivity type. 
The below sample shows how we can configure it.
HTTP: ServiceBusEnvironment.SystemConnectivity.Mode = ConnectivityMode.Http;
TCP:  ServiceBusEnvironment.SystemConnectivity.Mode = ConnectivityMode.Tcp;
Auto: ServiceBusEnvironment.SystemConnectivity.Mode = ConnectivityMode.AutoDetect;

In conclusion we should keep in mind that all the communication between Azure Service Bus endpoint and our system is done over a secure channel. For HTTP connection, a tunnel is establish over 80 and 443 ports.
Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...
Post a Comment
Read more