Why HTTPS secures communication in Nginx - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does HTTPS protect data during transmission?

Which of the following best explains why HTTPS secures communication between a client and a server?

A HTTPS encrypts data so that only the intended recipient can read it, preventing eavesdropping.

B HTTPS compresses data to make transmission faster and more efficient.

C HTTPS changes the IP address of the server to hide its location.

D HTTPS stores data locally on the client to avoid sending it over the network.

💡 Hint

Think about what encryption does to data sent over the internet.

HTTPS uses encryption to protect data so that only the client and server can understand it. This prevents others from reading or tampering with the data during transmission.

💻 Command Output

intermediate

Check HTTPS status in nginx configuration

What will be the output of the following command on a server running nginx with HTTPS enabled?

sudo nginx -T | grep listen

Nginx

sudo nginx -T | grep listen

A listen 80;

B listen 443 ssl;

C listen 22;

D listen 8080;

💡 Hint

HTTPS usually uses a specific port number with SSL enabled.

Port 443 with 'ssl' indicates HTTPS is enabled in nginx configuration.

❓ Configuration

advanced

Identify the correct nginx HTTPS server block snippet

Which nginx server block snippet correctly enables HTTPS with SSL certificate and key?

A

}
;yek.elpmaxe/etavirp/lss/cte/ yek_etacifitrec_lss    
;trc.elpmaxe/strec/lss/cte/ etacifitrec_lss    
;lss 344 netsil    
{ revres

B

server {
    listen 80 ssl;
    ssl_certificate /etc/ssl/certs/example.crt;
    ssl_certificate_key /etc/ssl/private/example.key;
}

C

server {
    listen 443;
    ssl_certificate /etc/ssl/certs/example.crt;
    ssl_certificate_key /etc/ssl/private/example.key;
}

D

server {
    listen 443 ssl;
    ssl_certificate /etc/ssl/certs/example.crt;
    ssl_certificate_key /etc/ssl/private/example.key;
}

💡 Hint

Check the port number and correct SSL directives.

Option D correctly listens on port 443 with SSL enabled and uses the proper ssl_certificate and ssl_certificate_key directives.

❓ Troubleshoot

advanced

Why does nginx fail to start after enabling HTTPS?

After adding SSL configuration to nginx, the server fails to start. Which of the following is the most likely cause?

A The SSL certificate or key file paths are incorrect or files are missing.

B The server block is listening on port 80 instead of 443.

C The nginx user does not have permission to write to /var/log/nginx.

D The firewall is blocking port 22.

💡 Hint

Check file paths and permissions related to SSL files.

If nginx cannot find or access the SSL certificate or key files, it will fail to start when HTTPS is enabled.

✅ Best Practice

expert

Recommended security headers for HTTPS in nginx

Which set of HTTP headers should be added in nginx configuration to improve security for HTTPS websites?

A

add_header Content-Length 0;
add_header Connection close;
add_header Accept-Encoding gzip;

B

add_header Cache-Control no-cache;
add_header Content-Type text/html;
add_header Server nginx;

C

add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options DENY;

D

add_header Access-Control-Allow-Origin *;
add_header Content-Security-Policy "default-src *";
add_header X-Powered-By PHP/7.4;

💡 Hint

Think about headers that protect against common web attacks and enforce HTTPS.

Option C includes headers that enforce HTTPS usage, prevent MIME sniffing, and block clickjacking, which are best practices for HTTPS security.