37

Does HTTPS use TCP or UDP?

38

HTTPS can run over any reliable stream transport protocol. Normally that's TCP, but it could also be SCTP. It is NOT expected to run over UDP, which is an unreliable datagram protocol (in fact, while that's not its official name, that's a good way to remember what it is).

The IANA assignment for UDP is historical; at the time, nearly every protocol was assigned both the TCP and UDP port numbers, even if it was expected that it would only ever use one. There has been discussion of merging the port number registries, and only ever assigning one port to one protocol from here on. That is to make it easier to deploy future transport protocols that would otherwise need their own registries. I'm not aware of how that discussion concluded.

  • 1
    Most SSL implementations expose it as SSL socket, so it implies TCP. There are very rare occurrences of using any other transport. – Nasko May 14 '10 at 18:10
  • 3
    Warning: this answer is outdated (9 years ago). Take a look at the answer about QUIC protocol, which is an implementation that Google uses for Chrome. Just saying. – ivanleoncz Feb 26 '18 at 20:24
32

It uses TCP. It would be difficult to run it on UDP without the guarantee of packets arriving. If the packets don't arrive, the encrypted data will not be decipherable.

  • 4
    Or if the packets arrive out of order, as UDP contains no provisions for reordering packets like TCP. – janneb Jan 3 '10 at 9:42
  • 3
    Not going to -1 you because it'd be a little pedantic, but its worth noting that there's no reason it couldn't be run over UDP. It may be atypical, but it is possible. – ThatGraemeGuy Jan 3 '10 at 12:01
11

For the next time, if you wonder if a default port service run on tcp or udp, you can look at /etc/services on a linux machine.

  • 2
    Or a Windows machine, in a command prompt: find "https" %windir%\system32\drivers\etc\services – ThatGraemeGuy Jan 3 '10 at 11:57
  • 1
    My /etc/services also lists 80/udp. Actually, many services have allocated both ports, "just in case" I guess. – Peter Eisentraut Jan 9 '10 at 23:03
7

Nowadays HTTPS can run above either TCP or UDP.

The new "QUIC" protocol aims to replace multiple TCP connections with one multiplexed UDP connection, and hence can handle SSL and HTTPS:

HTTPS → SSL → QUIC flow → UDP → IP

QUIC was originally developped in 2012 by Google and is undergoing IETF review. For more details, see Wikipedia.

  • This should be the answer, considering the current scenario. For example, for experimental purposes, I could only block HTTPS traffic for an specific IP, using DROP targets on mangle table, using udp protocol for the rule. – ivanleoncz Feb 26 '18 at 20:22
  • +1, did not expect to learn something when clicking on this question. – T.Coutlakis Jun 25 '18 at 17:21
6

The OSI model allows higher layer protocols to run over any underlying protocol providing the correct services. HTTPS is HTTP using SSL/TLS security. SSL/TLS typically runs on top of TCP, but there is nothing to stop you from running it on UDP, SCTP or any other transport layer protocol.

As a matter of fact HTTPS over TCP and UDP are both defined as "well known" by IANA and have reserved port numbers.

See http://www.iana.org/assignments/port-numbers for the "official" ports/protocol combinations.

0
  • HTTPS is HTTP over TLS over TCP over IP.
  • TLS over UDP is a specific implementation called DTLS; where the D stands for "Datagram."

protected by Community 18 hours ago

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.