Why Do Ports Matter? Understanding TCP/UDP Ports and Their Role in Web Services

Common Ports

In everyday development, especially for backend developers, you encounter many well‑known ports: MySQL uses 3306, Redis uses 6379, Tomcat defaults to 8080, SSH uses 22, and so on.

The most important ports for web services are 80 (HTTP) and 443 (HTTPS), which we will discuss in detail.

Are Ports Mandatory?

During local web development you might access a service via localhost:8080. When the same service is deployed to a production site, the port often disappears from the URL because a default value is applied.

For example, accessing https://xiaogd.net actually uses the default port 443, so the full form is https://xiaogd.net:443. You can see the port in Chrome's developer tools.

If you specify an incorrect port, such as https://xiaogd.net:80, the request fails; however, http://xiaogd.net:80 works because the server redirects HTTP to HTTPS.

Default Ports for Protocols

When a URL does not explicitly contain a port, the browser assigns a default based on the protocol:

If the protocol is HTTP, the default port is 80.

If the protocol is HTTPS, the default port is 443.

If you manually enter a port, the request uses that port; an incorrect port results in a failed connection.

Why Do We Need Ports?

Ports are needed for inter‑process communication (IPC). A request contains an IP address, but the operating system also needs a port to know which process should handle the request.

Think of a port as a lightweight identifier similar to a process ID, allowing the server to route traffic to the correct service without exposing internal IDs.

Ports as an Indirection Layer

Directly using process IDs would require the client to know the server's internal IDs, which is impractical. Ports provide an indirection layer that decouples clients from server implementation details.

This indirection enables the principle of Inversion of Control: clients always send requests to well‑known ports (80 or 443), and servers listen on those ports, reversing the dependency.

Port Analogy

Imagine a citizen center where each service window corresponds to a port. To obtain a passport you go to window 80; you don't need to know which staff member is behind the desk.

Ports as a Naming Service

Ports act as a naming service similar to DNS or Spring Cloud Eureka: the numeric name (e.g., 80) maps to a specific service implementation.

Ports and IoC (Inversion of Control)

The port mechanism embodies IoC: clients request services via ports, and servers bind to those ports, allowing the server to control which process handles the request.

Revisiting Default Ports

Users generally do not need to know port numbers; defaults keep URLs simple. However, developers can choose any port for local testing or for obscure services.

Ports and TCP/UDP Protocols

Ports exist for both TCP and UDP, though most common services (HTTP, HTTPS) use TCP. UDP ports 80 and 443 are reserved but not typically used for web traffic.

When a TCP connection is established, the client selects a random source port (e.g., 38672) and the server responds to that port, completing the bidirectional communication.

Thus, IP + port together enable processes on different hosts to communicate via TCP/UDP.