Understanding Web Protocols: HTTP and HTTPS

Every time you open a browser and visit a website, something is happening behind the scenes that makes that page appear on your screen. That "something" is a web protocol, and for the CCST Networking exam, you need to understand the two most common ones: HTTP and HTTPS.

What Is a Protocol?

Before diving into HTTP and HTTPS specifically, let's make sure the word "protocol" makes sense. A protocol is simply a set of rules that defines how two devices communicate. Think of it like a language: if you and I both speak English, we can exchange information. If your browser and a web server both "speak" HTTP, they can exchange web pages.

HTTP: The Foundation of Web Communication

HTTP stands for HyperText Transfer Protocol. It is the foundation of internet communication on the web. When you type a URL into your browser and press Enter, your browser sends an HTTP request to a web server. The server processes that request and sends back an HTTP response, which is the web page you see.

Here is a simplified example of what that exchange looks like:

Client Request:
GET /index.html HTTP/1.1
Host: www.example.com

Server Response:
HTTP/1.1 200 OK
Content-Type: text/html
...page content follows...

HTTP operates on port 80 by default. It is a stateless protocol, meaning each request is independent. The server does not remember your previous request when you make a new one.

The problem with HTTP is straightforward: the data sent between your browser and the server is transmitted in plain text. That means anyone positioned between you and the server (on the same Wi-Fi network, for example) could potentially read everything you send and receive. Think of it like sending a postcard: anyone who handles it along the way can read what is written on it.

HTTPS: Adding Security to the Conversation

HTTPS stands for HyperText Transfer Protocol Secure. It is HTTP with an added layer of encryption provided by TLS (Transport Layer Security). This encryption scrambles the data before it leaves your device, so even if someone intercepts it, they cannot read it.

Using the postcard analogy: HTTPS puts your message inside a locked box before it leaves your hands. Only the intended recipient has the key to open it.

HTTPS operates on port 443 by default. You can recognize it in a browser by:

• The URL beginning with https:// instead of http://
• A padlock icon in the browser's address bar
• A valid SSL/TLS certificate from the web server

Key Differences at a Glance

• HTTP: Plain text, no encryption, uses port 80
• HTTPS: Encrypted via TLS, uses port 443
• HTTP: Suitable for non-sensitive public content
• HTTPS: Required for login pages, payment forms, and any sensitive data

Why Secure Browsing Matters

Secure browsing is not just a convenience feature. It is a fundamental part of protecting users on the internet. When you log into your bank, enter a password, or submit personal information, HTTPS ensures that data is encrypted end-to-end between your browser and the server.

From a networking perspective, HTTP and HTTPS traffic behaves differently on the wire. Network devices like firewalls and proxies must account for both protocols. Many organizations enforce HTTPS-only policies, redirecting any http:// requests automatically to https://.

As a rule of thumb: if you see a browser warning that a site is "Not Secure," that means the site is still using HTTP. You should avoid entering any personal information on that page.

What's Next

Now that you understand how HTTP and HTTPS handle web communication, the next logical step is understanding DNS (Domain Name System): the protocol that translates human-friendly names like www.example.com into the IP addresses that routers and switches actually use to deliver traffic. Stay tuned for our next post in the CCST Networking series.