Network Protocols

HTTP

HTTP (Hypertext Transfer Protocol) is an application-layer protocol for transmitting hypermedia documents, such as HTML, across the internet. It serves as the foundation for data communication on the World Wide Web, enabling clients (like web browsers) to request resources from servers and receive responses. HTTP operates as a request-response protocol in a client-server computing model, typically using TCP/IP connections.

Also known as: Hypertext Transfer Protocol, http, HTTP/1.1, HTTP/2, HTTP/3

🧊Why learn HTTP?

Developers should learn HTTP because it is essential for building and interacting with web applications, APIs, and services, as it defines how data is formatted and transmitted between clients and servers. It is used in scenarios such as fetching web pages, making API calls in mobile apps, and enabling communication in microservices architectures. Understanding HTTP is crucial for debugging network issues, optimizing performance, and implementing security measures like HTTPS.

See how it ranks →

Compare HTTP

HTTP vs Ftp→HTTP vs Websocket→HTTP vs Grpc→

Learning Resources

MDN Web Docs: HTTP

HTTP Fundamentals on freeCodeCamp

HTTP Crash Course on YouTube

HTTP: The Definitive Guide (Book)

Related Tools

Https Rest Api Web Sockets Tcp Ip Web Development

Alternatives to HTTP

Ftp Websocket Grpc

Other Network Protocols

6LoWPAN (IPv6 over Low-Power Wireless Personal Area Networks) is a networking protocol that enables IPv6 communication over low-power, low-data-rate wireless networks, such as those used in IoT devices. It compresses IPv6 packets to fit within the constraints of IEEE 802.15.4 networks, allowing seamless integration of resource-constrained devices into the internet. This protocol is essential for enabling IoT applications by providing efficient, standardized IP-based connectivity for sensors and actuators.

Acme Protocol is a standardized communication protocol used for automated certificate management, primarily for obtaining and renewing SSL/TLS certificates from certificate authorities (CAs). It enables servers and applications to automatically request, validate, and install certificates without manual intervention, streamlining the process of securing web services with HTTPS. The protocol is widely implemented by CAs and tools like Let's Encrypt to support the ACME (Automated Certificate Management Environment) standard.

ActivityPub is a decentralized social networking protocol that enables different social platforms to communicate with each other, allowing users to interact across independent servers. It provides a standardized way for servers to exchange social activities like posts, likes, and follows, forming a federated network where no single entity controls the entire system. This protocol underpins many modern federated social networks, promoting interoperability and user autonomy.

ActivityPub is a decentralized social networking protocol that enables different social media platforms to communicate with each other, allowing users to interact across servers. It defines a client-to-server API for creating, updating, and deleting content, and a server-to-server API for federated interactions, forming a federated social web. This protocol underpins federated social media networks like Mastodon, PeerTube, and Pixelfed, facilitating interoperability without central control.

ActivityPub is an open, decentralized social networking protocol that enables servers to communicate and share social activities, such as posts, likes, and follows, across different platforms. It is a W3C standard that defines a client-to-server API for creating, updating, and deleting content, as well as a server-to-server API for federated interactions between independent servers. This allows users on different social media platforms to interact seamlessly, fostering interoperability in the fediverse.

AFP (Apple Filing Protocol) is a proprietary network protocol developed by Apple for file sharing over a network, primarily used with Apple's macOS and classic Mac OS operating systems. It enables users to access files and services on remote servers as if they were local, supporting features like file locking, Unicode filenames, and resource forks. While historically central to AppleTalk networks, it has been largely superseded by SMB (Server Message Block) in modern Apple environments.