With the rapid development of the Internet, the network protocols used with it are also constantly updated and iterated. There are currently three mainstream network protocols, namely HTTP, HTTPS and SOCKS5. Let's take a closer look at these three network protocols:

HTTP protocol

HTTP, or Hypertext Transfer Protocol, is the most widely used network protocol on the Internet. All WWW files must comply with this standard. HTTP is an application layer protocol based on the TCP/IP protocol. It does not involve data packet transmission, but mainly specifies the communication format between the client and the server. It is a protocol specifically used to transmit web content such as hypermedia documents injected with HTML.

The original purpose of designing HTTP was to provide a method for publishing and receiving HTML pages. In 1960, American Ted Nelson conceived a method for processing text information through computers and called it hypertext, which became the foundation for the development of the HTTP hypertext transfer protocol standard architecture.

HTTPS protocol

HTTPS, or Hypertext Transfer Security Protocol, is an HTTP channel with security as its goal. Simply put, it is a secure version of HTTP, that is, an SSL layer is added to HTTP. The security foundation of HTTPS is SSL, so the detailed content of encryption requires SSL. HTTPS is a URI scheme (abstract identifier system) with a syntax similar to the http: system, used for secure HTTP data transmission.

The https: URL indicates that it uses HTTP, but HTTPS has a different default port than HTTP and an encryption/authentication layer (between HTTP and TCP). The system was originally developed by Netscape and is now widely used for security-sensitive communications on the World Wide Web, such as transaction payments.

SOCKS5 protocol

SOCKS5 is a proxy protocol that plays an intermediary role between the front-end machine and the server machine that use the TCP/IP protocol to communicate, allowing the front-end machine in the intranet to access the server in the Internet or make the communication more secure.

The SOCKS5 server simulates the behavior of a front-end by forwarding the request sent by the front-end to the real target server. Here, the front-end and SOCKS5 also communicate through the TCP/IP protocol. The front-end sends the request originally sent to the real server to the SOCKS5 server, and then the SOCKS5 server forwards the request to the real server.