Why HTTPS secures communication in Nginx - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable HTTPS by specifying the SSL certificate file.

Nginx

ssl_certificate [1];

Drag options to blanks, or click blank then click option'

A/etc/nginx/ssl/server.crt

B/etc/nginx/conf.d/default.conf

C/var/www/html/index.html

D/etc/nginx/nginx.conf

Attempts:

3 left

💡 Hint

Common Mistakes

Using configuration files or HTML files instead of certificate files.

The ssl_certificate directive points to the SSL certificate file needed for HTTPS.

2fill in blank

medium

Complete the code to specify the SSL key file for HTTPS in nginx configuration.

Nginx

ssl_certificate_key [1];

Drag options to blanks, or click blank then click option'

A/usr/share/nginx/html/index.html

B/etc/nginx/conf.d/ssl.conf

C/etc/nginx/ssl/server.key

D/var/log/nginx/access.log

Attempts:

3 left

💡 Hint

Common Mistakes

Using log files or HTML files instead of key files.

The ssl_certificate_key directive specifies the private key file for HTTPS encryption.

3fill in blank

hard

Fix the error in the nginx server block to listen on HTTPS port.

Nginx

listen [1] ssl;

Drag options to blanks, or click blank then click option'

A8080

B443

C80

D22

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 80 or other ports which are not standard for HTTPS.

HTTPS uses port 443, so the server must listen on port 443 with SSL enabled.

4fill in blank

hard

Fill both blanks to complete the nginx server block for HTTPS with strong security.

Nginx

ssl_protocols [1];
ssl_ciphers [2];

Drag options to blanks, or click blank then click option'

ATLSv1.2 TLSv1.3

BSSLv3 TLSv1

CHIGH:!aNULL:!MD5

DLOW:!SSLv3

Attempts:

3 left

💡 Hint

Common Mistakes

Using outdated protocols or weak cipher suites.

Use modern TLS versions and strong ciphers to secure HTTPS connections.

5fill in blank

hard

Fill all three blanks to configure nginx to redirect HTTP to HTTPS and enable SSL.

Nginx

server {
    listen [1];
    return [2] https://$host$request_uri;
}

server {
    listen [3] ssl;
    ssl_certificate /etc/nginx/ssl/server.crt;
    ssl_certificate_key /etc/nginx/ssl/server.key;
}

Drag options to blanks, or click blank then click option'

A80

B301

C443

D302

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong ports or temporary redirect codes.

Port 80 listens for HTTP and redirects permanently (301) to HTTPS on port 443 with SSL enabled.

Practice

1. Why does HTTPS secure communication between a browser and a website?

easy

A. It changes the website's design automatically.

B. It makes the website load faster.

C. It encrypts data so others cannot read it during transfer.

D. It blocks all internet traffic except from trusted sites.

Solution

1. Step 1: Understand HTTPS function

   HTTPS encrypts data sent between browser and website to protect privacy.

2. Step 2: Identify the security benefit

   Encryption prevents attackers from reading or changing the data during transfer.

3. Final Answer:

   It encrypts data so others cannot read it during transfer. -> Option C

4. Quick Check:

   Encryption = Secure communication [OK]

Hint: HTTPS means encrypted data transfer [OK]

Common Mistakes:

• Thinking HTTPS speeds up the website
• Believing HTTPS changes website design
• Assuming HTTPS blocks all traffic except trusted

2. Which nginx configuration line enables HTTPS on port 443?

easy

A. listen 443 ssl;

B. listen 80 ssl;

C. listen 443 http;

D. listen 80 http;

Solution

1. Step 1: Identify HTTPS port and protocol

   HTTPS uses port 443 and requires SSL enabled in nginx.

2. Step 2: Match correct listen directive

   Only "listen 443 ssl;" correctly enables SSL on port 443.

3. Final Answer:

   listen 443 ssl; -> Option A

4. Quick Check:

   Port 443 + ssl = HTTPS enabled [OK]

Hint: HTTPS always uses port 443 with ssl flag [OK]

Common Mistakes:

• Using port 80 for HTTPS
• Missing ssl keyword
• Confusing http and https protocols

3. Given this nginx snippet, what happens when a user visits https://example.com?

server {
  listen 443 ssl;
  ssl_certificate /etc/ssl/certs/example.crt;
  ssl_certificate_key /etc/ssl/private/example.key;
  location / {
    root /var/www/html;
  }
}

medium

A. The site loads but without encryption.

B. The site loads securely with encrypted data transfer.

C. The server returns an error due to missing port 80.

D. The site redirects to HTTP automatically.

Solution

1. Step 1: Analyze nginx SSL setup

   Configuration listens on port 443 with SSL certificates set, enabling HTTPS.

2. Step 2: Determine user experience

   User visiting https://example.com gets encrypted connection and site content served.

3. Final Answer:

   The site loads securely with encrypted data transfer. -> Option B

4. Quick Check:

   SSL config + port 443 = secure site load [OK]

Hint: SSL certs + listen 443 = secure HTTPS site [OK]

Common Mistakes:

• Assuming missing port 80 causes error
• Thinking HTTPS works without SSL certs
• Believing site redirects to HTTP automatically

4. You configured nginx with SSL but users report insecure warnings. Which fix is correct?

server {
  listen 443 ssl;
  ssl_certificate /etc/ssl/certs/example.crt;
  # ssl_certificate_key missing here
  location / {
    root /var/www/html;
  }
}

medium

A. Add the missing ssl_certificate_key directive with the private key path.

B. Change listen 443 ssl; to listen 80 ssl;.

C. Remove the ssl_certificate line to disable SSL.

D. Add ssl_protocols TLSv1; to force older TLS.

Solution

1. Step 1: Identify missing SSL key

   SSL requires both certificate and private key to work properly.

2. Step 2: Fix configuration by adding key

   Adding ssl_certificate_key with correct path fixes SSL warnings.

3. Final Answer:

   Add the missing ssl_certificate_key directive with the private key path. -> Option A

4. Quick Check:

   SSL key missing = warnings; add key [OK]

Hint: SSL needs both cert and key files [OK]

Common Mistakes:

• Changing port 443 to 80 for SSL
• Removing SSL cert disables HTTPS but not fix warnings
• Forcing old TLS versions causes security risks

5. You want nginx to redirect all HTTP traffic to HTTPS to secure communication. Which configuration snippet achieves this?

hard

A. server {
listen 443;
ssl_certificate /etc/ssl/certs/example.crt;
}

B. server {
listen 443 ssl;
return 301 http://$host$request_uri;
}

C. server {
listen 80 ssl;
root /var/www/html;
}

D. server {
listen 80;
return 301 https://$host$request_uri;
}

Solution

1. Step 1: Understand HTTP to HTTPS redirect

   Redirect must listen on port 80 (HTTP) and send 301 redirect to HTTPS URL.

2. Step 2: Check configuration correctness

   server { listen 80; return 301 https://$host$request_uri; } listens on port 80 and returns 301 redirect to https:// with original host and URI.

3. Final Answer:

   server { listen 80; return 301 https://$host$request_uri; } -> Option D

4. Quick Check:

   Port 80 redirect to HTTPS = secure redirect [OK]

Hint: Redirect HTTP (80) to HTTPS with 301 return [OK]

Common Mistakes:

• Redirecting HTTPS to HTTP instead
• Using ssl on port 80 incorrectly
• Missing redirect causes insecure access