HTTPS for web server in Raspberry Pi - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Python HTTPS server code snippet?

Consider this Python code snippet running on a Raspberry Pi to start a simple HTTPS server using http.server and ssl modules. What will it print when started successfully?

Raspberry Pi

import http.server
import ssl

server_address = ('', 4443)
httpd = http.server.HTTPServer(server_address, http.server.SimpleHTTPRequestHandler)
httpd.socket = ssl.wrap_socket(httpd.socket, certfile='server.pem', server_side=True)
print('Serving on https://localhost:4443')
httpd.serve_forever()

A Serving on https://localhost:4443

B Serving on https://0.0.0.0:4443

C Error: certfile not found

D Serving on http://localhost:4443

💡 Hint

Look at the print statement and the port used.

The code explicitly prints 'Serving on https://localhost:4443' before starting the server. The server uses SSL on port 4443, so the URL is HTTPS and localhost.

🧠 Conceptual

intermediate

Which file is essential to enable HTTPS on a Raspberry Pi web server?

To enable HTTPS on a Raspberry Pi web server, which file must you have to provide the server's identity securely?

A index.html (homepage file)

B config.txt (system configuration file)

C server.pem (certificate and private key file)

D hosts (local DNS file)

💡 Hint

Think about what HTTPS needs to prove the server's identity.

HTTPS requires a certificate file (often combined with a private key) like server.pem to encrypt communication and prove the server's identity.

🔧 Debug

advanced

Why does this HTTPS server code raise an error?

Look at this Python code snippet for an HTTPS server on Raspberry Pi. It raises an error when run. What is the cause?

Raspberry Pi

import http.server
import ssl

server_address = ('', 4443)
httpd = http.server.HTTPServer(server_address, http.server.SimpleHTTPRequestHandler)
httpd.socket = ssl.wrap_socket(httpd.socket, keyfile='server.key', certfile='server.crt', server_side=True)
httpd.serve_forever()

A ssl.wrap_socket requires certfile only, not keyfile

B Port 4443 is reserved and cannot be used

C http.server.HTTPServer does not support SSL wrapping

D Missing combined PEM file; keyfile and certfile must be combined

💡 Hint

Check the SSL wrapping parameters and file requirements.

The ssl.wrap_socket function requires the private key and certificate to be correctly provided. Often, the key and cert must be combined into one PEM file or correctly referenced. If separate files are used, they must exist and be valid. Missing or mismatched files cause errors.

📝 Syntax

advanced

Which option correctly creates an SSL context for HTTPS on Raspberry Pi?

Choose the correct Python code snippet that creates an SSL context for an HTTPS server on Raspberry Pi.

A

import ssl
context = ssl.SSLContext(ssl.PROTOCOL_SSLv3)
context.load_cert_chain('server.pem')

B

import ssl
context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER)
context.load_cert_chain('server.pem')

C

import ssl
context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT)
context.load_cert_chain('server.pem')

D

import ssl
context = ssl.SSLContext(ssl.PROTOCOL_TLS)
context.load_cert_chain('server.pem')

💡 Hint

Look for the protocol designed for servers.

ssl.PROTOCOL_TLS_SERVER is the correct protocol for creating an SSL context for a server. Other protocols like SSLv3 are outdated or for clients.

🚀 Application

expert

How many simultaneous HTTPS connections can this Raspberry Pi server handle?

Given this Python HTTPS server code running on Raspberry Pi, how many simultaneous HTTPS client connections can it handle by default?

Raspberry Pi

import http.server
import ssl

server_address = ('', 4443)
httpd = http.server.HTTPServer(server_address, http.server.SimpleHTTPRequestHandler)
httpd.socket = ssl.wrap_socket(httpd.socket, certfile='server.pem', server_side=True)
httpd.serve_forever()

A 1

B 5

C 10

D Unlimited

💡 Hint

Consider the default behavior of http.server.HTTPServer.

The http.server.HTTPServer class is single-threaded and handles one request at a time by default. To handle multiple simultaneous connections, you need to use ThreadingHTTPServer or similar.