Timeline for How does any program identify the protocol header next from TCP?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2021 at 12:11 | comment | added | Zac67♦ | The source sends segments belonging to an SSH session to port 22 and those for HTTP to port 80 (or HTTPS to port 443). Those segments are then passed to the according process by the destination host stack. The actual web server never sees anything related to SSH. | |
| Jan 31, 2021 at 12:06 | comment | added | Maslin | that's where the confusion comes from - how does the web server know that incoming packets are in a SSH format and not HTTP? | |
| Jan 29, 2021 at 11:20 | comment | added | Zac67♦ | @Maslin SSH uses its own TCP port 22. A web server (Apache, nginx, ...) doesn't understand SSH, FTP or anything else but HTTP. | |
| Jan 29, 2021 at 11:10 | comment | added | Maslin | Thanks for your answer, but I am a bit confused, because what if I were to SSH into port 80 - how does the server identify that I am using the SSH protocol and not HTTP? Is there some way the web server can identify the protocol based on the data format itself? | |
| Jul 30, 2018 at 5:34 | history | answered | Zac67♦ | CC BY-SA 4.0 |