How do multiple clients connect simultaneously to one port, say 80, on a server? [duplicate]

by

First off, a “port” is just a number. All a “connection to a port” really represents is a packet which has that number specified in its “destination port” header field.

Now, there are two answers to your question, one for stateful protocols and one for stateless protocols.

For a stateless protocol (ie UDP), there is no problem because “connections” don’t exist – multiple people can send packets to the same port, and their packets will arrive in whatever sequence. Nobody is ever in the “connected” state.

For a stateful protocol (like TCP), a connection is identified by a 4-tuple consisting of source and destination ports and source and destination IP addresses. So, if two different machines connect to the same port on a third machine, there are two distinct connections because the source IPs differ. If the same machine (or two behind NAT or otherwise sharing the same IP address) connects twice to a single remote end, the connections are differentiated by source port (which is generally a random high-numbered port).

Simply, if I connect to the same web server twice from my client, the two connections will have different source ports from my perspective and destination ports from the web server’s. So there is no ambiguity, even though both connections have the same source and destination IP addresses.

Ports are a way to multiplex IP addresses so that different applications can listen on the same IP address/protocol pair. Unless an application defines its own higher-level protocol, there is no way to multiplex a port. If two connections using the same protocol simultaneously have identical source and destination IPs and identical source and destination ports, they must be the same connection.

More Related Contents:

  1. How many socket connections can a web server handle?
  2. HTTP Keep Alive and TCP keep alive
  3. Avoid caching of the http responses
  4. Uses of content-disposition in an HTTP response header
  5. What’s the difference between a POST and a PUT HTTP REQUEST?
  6. TCP Client to Server communication
  7. How can I use an http proxy with node.js http.Client?
  8. Spaces in URLs? [duplicate]
  9. CORS Access-Control-Allow-Headers wildcard being ignored?
  10. Dealing with HTTP content in HTTPS pages
  11. How to handle multiple cookies with the same name?
  12. What encoding should I use for HTTP Basic Authentication?
  13. Ideal HTTP cache control headers for different types of resources
  14. Correct way to delete cookies server-side
  15. Remove http referer
  16. Detect end of HTTP request body
  17. Java detect lost connection [duplicate]
  18. Proper REST response for empty table?
  19. How to correctly set Http Request Header in Angular 2
  20. Using “transfer-encoding: chunked”, how much data must be sent before browsers start rendering it?
  21. Do web browsers always send a trailing slash after a domain name?
  22. What exactly is an HTTP Entity?
  23. Payloads of HTTP Request Methods
  24. What HTTP response headers are required
  25. Chunked transfer encoding – browser behavior
  26. Domain set cookie for subdomain
  27. Chunked encoding and content-length header
  28. Console errors. Failed to load resource: net::ERR_INSECURE_RESPONSE
  29. What to do with errors when streaming the body of an Http request
  30. Standard method for HTTP partial upload, resume upload

Leave a Comment