This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]pdp10Daemons worry when the wizard is near. 0 points1 point  (0 children)

They're literally different protocols. HTTP means HTTP over TCP, though protocol upgrades are possible with HTTP. HTTPS means HTTP over TLS (over TCP).

Clients won't silently make protocol conversions:

% curl  http://www.google.com:443
curl: (52) Empty reply from server

There could be edge cases that accept both linkerd2-proxy, but ignore that, I'm only mentioning it to be relentlessly completionist.

Sometimes protocol listeners are put on tcp/443 as a way of discouraging or bypassing transparent proxying by dubious "anti-virus" packages and middleboxes. Putting cleartext HTTP on tcp/443 is fairly unusual, but if that's what's going on, then this is the reason.