HTTPS for web server in Raspberry Pi - Time & Space Complexity

Time Complexity: HTTPS for web server

O(n)

Understanding Time Complexity

When setting up HTTPS on a Raspberry Pi web server, it's important to understand how the time to handle requests grows as more users connect.

We want to see how the server's work changes when it encrypts and decrypts data for each visitor.

Scenario Under Consideration

Analyze the time complexity of the HTTPS handshake and request handling code.

import ssl
import socket

context = ssl.create_default_context(ssl.Purpose.CLIENT_AUTH)
context.load_cert_chain(certfile='cert.pem', keyfile='key.pem')

with socket.socket() as sock:
    sock.bind(('0.0.0.0', 443))
    sock.listen(5)
    while True:
        client, addr = sock.accept()
        with context.wrap_socket(client, server_side=True) as ssock:
            data = ssock.recv(1024)
            ssock.sendall(b'HTTP/1.1 200 OK\r\n\r\nHello HTTPS')
    

This code sets up a simple HTTPS server that accepts connections, performs SSL handshake, receives data, and sends a response.

Identify Repeating Operations

Look at what repeats as more clients connect.

• Primary operation: The server accepts connections and performs SSL handshake for each client.
• How many times: Once per client connection, repeating indefinitely.

How Execution Grows With Input

Each new client causes the server to do a handshake and handle a request.

Input Size (n)	Approx. Operations
10 clients	10 handshakes + 10 request processes
100 clients	100 handshakes + 100 request processes
1000 clients	1000 handshakes + 1000 request processes

Pattern observation: The work grows directly with the number of clients; more clients mean more handshakes and processing.

Final Time Complexity

Time Complexity: O(n)

This means the server's work grows linearly with the number of client connections it handles.

Common Mistake

[X] Wrong: "The SSL handshake happens once and then all clients share it."

[OK] Correct: Each client must do its own handshake to securely connect, so the server repeats this work for every new client.

Interview Connect

Understanding how HTTPS affects server workload helps you explain real-world server behavior and scalability in interviews.

Self-Check

"What if the server used persistent connections to keep clients connected longer? How would the time complexity change?"

Practice

1. What is the main purpose of using HTTPS on a Raspberry Pi web server?

easy

A. To make the website load faster

B. To change the website's design automatically

C. To allow more users to connect simultaneously

D. To encrypt data and keep the website safe

Solution

1. Step 1: Understand HTTPS function

   HTTPS encrypts data between the user and the server to protect privacy and security.

2. Step 2: Compare options

   Only To encrypt data and keep the website safe correctly describes HTTPS purpose; others are unrelated to encryption.

3. Final Answer:

   To encrypt data and keep the website safe -> Option D

4. Quick Check:

   HTTPS = encrypt data [OK]

Hint: HTTPS means secure data transfer with encryption [OK]

Common Mistakes:

• Thinking HTTPS speeds up the website
• Confusing HTTPS with website design
• Believing HTTPS increases user capacity

2. Which command correctly stops the Apache web server on Raspberry Pi before obtaining an SSL certificate?

easy

A. sudo systemctl stop apache2

B. sudo start apache2

C. apache2 stop sudo

D. stop apache2 sudo

Solution

1. Step 1: Recall correct systemctl syntax

   The command to stop a service is 'sudo systemctl stop servicename'.

2. Step 2: Identify correct option

   sudo systemctl stop apache2 matches the correct syntax to stop Apache2; others are invalid commands.

3. Final Answer:

   sudo systemctl stop apache2 -> Option A

4. Quick Check:

   Stop service = sudo systemctl stop [OK]

Hint: Use 'sudo systemctl stop apache2' to stop Apache safely [OK]

Common Mistakes:

• Using incorrect command order
• Omitting 'sudo' for permissions
• Using 'start' instead of 'stop'

3. What will be the output of this command on Raspberry Pi after installing Certbot and running it to get a certificate?

sudo certbot --apache

medium

A. It automatically obtains and installs an SSL certificate for Apache

B. It deletes all Apache configuration files

C. It starts the Apache server without SSL

D. It shows an error because Certbot is not compatible

Solution

1. Step 1: Understand Certbot command

   The command 'sudo certbot --apache' requests and installs SSL certificates automatically for Apache.

2. Step 2: Evaluate options

   Only It automatically obtains and installs an SSL certificate for Apache correctly describes the expected behavior; others are incorrect or false.

3. Final Answer:

   It automatically obtains and installs an SSL certificate for Apache -> Option A

4. Quick Check:

   Certbot --apache = get SSL cert [OK]

Hint: Certbot with --apache auto installs SSL cert [OK]

Common Mistakes:

• Thinking Certbot deletes files
• Assuming Certbot starts server
• Believing Certbot is incompatible with Apache

4. You tried to get an SSL certificate but forgot to stop Apache first. What error will most likely occur?

medium

A. No internet connection error

B. Certificate installed successfully

C. Port 80 is already in use error

D. Apache configuration syntax error

Solution

1. Step 1: Understand port usage during certificate request

   Certbot needs to use port 80 to verify domain ownership, but Apache uses it if running.

2. Step 2: Identify error from port conflict

   If Apache is not stopped, Certbot cannot bind port 80, causing 'Port 80 is already in use' error.

3. Final Answer:

   Port 80 is already in use error -> Option C

4. Quick Check:

   Apache running blocks port 80 for Certbot [OK]

Hint: Stop Apache before Certbot to avoid port 80 conflict [OK]

Common Mistakes:

• Ignoring need to stop Apache
• Expecting success without stopping server
• Confusing error with internet issues

5. After successfully obtaining an SSL certificate on Raspberry Pi, what is the correct sequence to enable HTTPS on your Apache web server?

hard

A. Restart Apache, then configure firewall to allow port 443

B. Configure firewall to allow port 443, then restart Apache

C. Restart Apache only, no firewall changes needed

D. No action needed; HTTPS works automatically without restart

Solution

1. Step 1: Open firewall port 443 for HTTPS

   Before restarting Apache, ensure firewall allows HTTPS traffic on port 443.

2. Step 2: Restart Apache to apply SSL certificate

   Restarting Apache activates the new SSL certificate and enables HTTPS.

3. Final Answer:

   Configure firewall to allow port 443, then restart Apache -> Option B

4. Quick Check:

   Firewall open 443, then restart Apache [OK]

Hint: Open port 443 before restarting Apache for HTTPS [OK]

Common Mistakes:

• Restarting Apache before opening firewall port
• Assuming no firewall changes needed
• Believing HTTPS works without restart