Layer 7 — Application

What This Layer Does

The Application layer is where networking meets the things people actually do: loading a page, sending mail, opening a shared file, connecting to a distant machine.

Start with a correction, because this layer's name misleads almost everyone. The Application layer is not the application. Your browser is a program with menus, tabs, bookmarks, and a rendering engine, and none of that is Layer 7. Layer 7 is the set of networking services and protocols the browser uses when it needs something from the network. The distinction matters: a text editor with no network feature has no Layer 7 involvement at all, and a browser has plenty.

What these services have in common is a request-and-response pattern. A program asks for something in an agreed format. A program somewhere else understands the request, does the work, and sends back an answer, or an explanation of why it could not. The rules for what a valid request looks like, what the answers mean, and what to do about errors are the protocol.

A handful of protocols cover most of everyday use:

• HTTP and HTTPS carry web pages. HTTPS is HTTP with the contents encrypted.
• DNS translates a name such as example.com into an IP address. Nearly everything you do begins with a DNS lookup, which is why DNS trouble feels like the whole internet has failed.
• SMTP sends email between mail servers.
• IMAP lets a mail program read messages that stay stored on a server.
• FTP transfers files. It is old and sends credentials unprotected, so secure alternatives have largely replaced it.
• SSH provides an encrypted connection to a remote machine's command line.

That list is deliberately short. There are hundreds more, and memorizing them teaches you nothing about how networks work.

Common Examples

• HTTP and HTTPS, for web browsing
• DNS, for turning names into IP addresses
• SMTP and IMAP, for sending and reading email
• FTP, for file transfer
• SSH, for secure remote access

Simple Real-World Example

You type example.com into a browser and press Enter.

The browser first needs an IP address, so it makes a DNS request asking what address belongs to that name, and gets one back. It then sends an HTTPS request to that address asking for the page. The web server receives the request, finds the page, and returns it along with a status code saying whether the request succeeded. The browser then asks for the images, stylesheets, and scripts the page refers to, each one its own request and response.

Two protocols, several exchanges, and all of it finished before you have finished lifting your finger off the key.

What Can Go Wrong?

• DNS lookup fails. The name cannot be turned into an address, so nothing connects, even though the network itself is healthy.
• The service is down. The request arrives correctly and the program on the other side is not running or is overloaded.
• The request is refused. The server understood the request perfectly and declined it, which is what a "not found" or "forbidden" message means.
• The two sides support different versions. Both speak the protocol, neither agrees on which variety, and the connection fails for reasons that look mysterious from the outside.

Remember This

Layer 7 provides the network services used by applications.