Linux Networking & TCP/IP for Developers · Lesson

HTTP/HTTPS Web Services

Understand how web servers like Apache or Nginx serve content, including basic configuration and HTTPS setup.

HTTP/HTTPS Web Services is a free Linux Networking & TCP/IP for Developers lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Linux Networking & TCP/IP for Developers learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Intro to Web Services

Welcome! In this lesson, we'll explore how websites and applications deliver content to your browser. This involves understanding web services, which are essentially how computers communicate over the internet to share information.

At the heart of this communication are protocols like HTTP and HTTPS, powered by web server software.

HTTP: The Web's Language

HTTP stands for Hypertext Transfer Protocol. It's the standard protocol for sending and receiving web pages and other web content.

When you type a website address, your browser sends an HTTP request to a server.
The server processes this request and sends an HTTP response back, usually containing the web page data.
HTTP typically uses port 80 for communication.

Web Servers in Action

A web server is software that stores web content (like HTML files, images, CSS, JavaScript) and delivers it to clients (like your browser) over HTTP or HTTPS.

Two of the most popular web server software packages are Apache HTTP Server and Nginx. Both are powerful and widely used in Linux environments.

Apache: Serving Content

Apache is known for its flexibility and module system. To serve content, Apache needs to know where your website files are located. This is defined by the DocumentRoot directive.

Here's a simplified example of an Apache configuration:

<VirtualHost *:80>
    ServerAdmin webmaster@example.com
    DocumentRoot /var/www/html/mysite
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

Nginx: Serving Content

Nginx (pronounced 'engine-x') is known for its high performance and efficiency, especially for serving static content and acting as a reverse proxy. It uses 'server blocks' to define how it handles requests.

The root directive specifies the directory containing your website files.

server {
    listen 80;
    server_name example.com www.example.com;
    root /var/www/html/mysite;
    index index.html index.htm;

    location / {
        try_files $uri $uri/ =404;
    }
}

Apache Virtual Hosts

To host multiple websites on a single server, Apache uses Virtual Hosts. Each Virtual Host configuration block defines settings for a specific domain name or IP address.

This allows Apache to serve example.com from one directory and anothersite.com from a completely different one, all on the same server.

Nginx Server Blocks

Nginx uses Server Blocks, which are conceptually similar to Apache's Virtual Hosts. Each server block listens on a specific port and responds to requests for particular domain names (specified by server_name).

This makes Nginx highly efficient for managing multiple web applications or websites.

Why HTTPS? Security First!

HTTPS (Hypertext Transfer Protocol Secure) is the secure version of HTTP. It's crucial for protecting sensitive data exchanged over the internet.

Encryption: HTTPS encrypts communication between your browser and the server, making it unreadable to eavesdroppers.
Data Integrity: It ensures that data hasn't been tampered with during transmission.
Authentication: It verifies that you are communicating with the intended server, preventing 'man-in-the-middle' attacks.

HTTPS typically uses port 443.

SSL/TLS Certificates

HTTPS relies on SSL/TLS certificates. These digital certificates are issued by trusted Certificate Authorities (CAs) and contain information about the website's identity.

When you visit an HTTPS site, your browser checks the certificate to ensure it's valid and trusted. This handshake process establishes a secure, encrypted connection.

Services like Let's Encrypt provide free SSL/TLS certificates, often automated with tools like Certbot.

Configuring HTTPS

To enable HTTPS, you need to configure your web server to use an SSL/TLS certificate. This involves specifying the certificate file and its corresponding private key in your server's configuration.

Both Apache and Nginx have directives to handle this. Here's a conceptual example:

server {
    listen 443 ssl;
    server_name secure.example.com;

    ssl_certificate /etc/letsencrypt/live/secure.example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/secure.example.com/privkey.pem;

    # Other HTTPS related settings...
}

Check Your Understanding

Web servers are essential for delivering content online. Let's test your knowledge about the protocols and their security aspects.

Web Services Recap

We've covered the fundamentals of web services! You now understand:

The roles of HTTP and HTTPS protocols.
How web servers like Apache and Nginx deliver content.
The importance of DocumentRoot/root and Virtual Hosts/Server Blocks.
Why HTTPS and SSL/TLS certificates are critical for secure communication.

These concepts are foundational for deploying and managing any web application on a Linux server!

Frequently asked questions

Is the “HTTP/HTTPS Web Services” lesson free?

Yes — the full text of “HTTP/HTTPS Web Services” is free to read here on the web, and the Linux Networking & TCP/IP for Developers course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Linux Networking & TCP/IP for Developers course, upgrade to CoddyKit PRO.

What will I learn in “HTTP/HTTPS Web Services”?

Understand how web servers like Apache or Nginx serve content, including basic configuration and HTTPS setup. You practise Linux Networking & TCP/IP for Developers with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Linux Networking & TCP/IP for Developers?

No prior experience is required. Linux Networking & TCP/IP for Developers on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “HTTP/HTTPS Web Services” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Linux Networking & TCP/IP for Developers lesson?

Yes. Every Linux Networking & TCP/IP for Developers lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Linux Networking & TCP/IP for Developers