websockets
Comment on China cut itself off from the global internet on Wednesday
nul9o9@lemmy.dbzer0.com 4 days ago
Anyone know why someone would use port 443 for anything other than https?
Euphoma@lemmy.ml 4 days ago
BaroqueInMind@piefed.social 4 days ago
VPNs, DNS over https (DoH), load balancers via DHCP, encrypted remote procedure calls, TCP pipes via gsocket.
I could go on.
setsubyou@lemmy.world 3 days ago
Sometimes mandatory web proxies still allow direct connections to port 443 so as to not break https, which in return means as long as your connection is to port 443, that proxy will pass it through without interfering.
I used to run sshd on port 443 for this reason back when I regularly had to work from client networks.
Evotech@lemmy.world 3 days ago
To not get blocked by the great firewall
Zykino@programming.dev 4 days ago
Pass thoses firewalls and other corporates proxy/VPN/… that block most ports. If what you build is at least partly used where user have internet access, you know this port is open. Even if 22, 8080 and all the others are closed.
ksigley@lemmy.world 3 days ago
Happy cake day!
sugar_in_your_tea@sh.itjust.works 3 days ago
Some ISPs block other ports, so if you want to host something, that might be your best option.
JasonDJ@lemmy.zip 3 days ago
HTTPS may be the official designation for the port, but it is the de facto standard port for TLS. Whatever you want to send over TLS, doesn’t really matter.
HTTPS is just HTTP served over TLS (originally SSL).
Step by step, if you were to analyze a web connection over port 443, you would see that the client first negotiates the TCP connection (via three-way handshake), then TLS, and it’s not till after TLS is established that HTTPS is negotiated.
In that way, it’s kinda wrong to say it’s the HTTPS port. It’s really, nowadays, the TLS port. HTTP is just one of many protocols that can ride on top of it, and when we do that, we call it HTTPS.