HTTP to HTTPS redirect in Nginx - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of redirecting HTTP to HTTPS in a web server?

Redirecting HTTP to HTTPS ensures that all web traffic is encrypted, protecting data from being intercepted or tampered with. It improves security and user trust.

beginner

Which Nginx directive is used to perform a permanent redirect from HTTP to HTTPS?

The return 301 https://$host$request_uri; directive is used inside the HTTP server block to permanently redirect requests to HTTPS.

beginner

Show a simple Nginx server block configuration that redirects all HTTP requests to HTTPS.

server {
    listen 80;
    server_name example.com www.example.com;
    return 301 https://$host$request_uri;
}

intermediate

Why is it important to use a 301 status code for HTTP to HTTPS redirects?

A 301 status code means 'Moved Permanently'. It tells browsers and search engines that the resource has permanently moved to HTTPS, helping SEO and caching the redirect.

beginner

What happens if you do not redirect HTTP to HTTPS on your website?

Users can access the site over an unencrypted connection, risking data interception. Browsers may show security warnings, reducing user trust and potentially harming SEO rankings.

Which Nginx directive is used to redirect HTTP traffic to HTTPS?

A listen 443 ssl;

B proxy_pass https://$host;

C return 301 https://$host$request_uri;

D rewrite ^ https://$host$request_uri? permanent;

The 'return 301 https://$host$request_uri;' directive sends a permanent redirect from HTTP to HTTPS.

What does the status code 301 mean in HTTP redirects?

A Moved Permanently

B Temporary Redirect

C Not Found

D Internal Server Error

301 means the resource has moved permanently to a new URL.

In Nginx, which port is typically used for HTTP traffic before redirecting to HTTPS?

A 443

B 8080

C 22

D 80

Port 80 is the default port for HTTP traffic.

What is the main benefit of redirecting HTTP to HTTPS?

A Improved security by encrypting data

B Lower server costs

C Faster page loading

D More ads displayed

Redirecting to HTTPS encrypts data, improving security.

Which variable in Nginx holds the original requested URI during redirect?

A $host

B $request_uri

C $server_name

D $remote_addr

$request_uri contains the original URI requested by the client.

Explain how to configure Nginx to redirect all HTTP requests to HTTPS.

Think about the server block that listens on HTTP and sends a permanent redirect.

Why is it important to use HTTPS and redirect HTTP traffic to HTTPS on websites?

Consider what happens if data is sent without encryption and how browsers react.

Practice

1. What is the main purpose of configuring an HTTP to HTTPS redirect in nginx?

easy

A. To allow both HTTP and HTTPS traffic without changes

B. To block all HTTP traffic permanently

C. To automatically send users from an insecure HTTP site to a secure HTTPS site

D. To disable HTTPS and use only HTTP

Solution

1. Step 1: Understand HTTP and HTTPS roles

   HTTP is not secure, HTTPS encrypts data for safety.

2. Step 2: Purpose of redirect

   Redirecting HTTP to HTTPS ensures users always use the secure version.

3. Final Answer:

   To automatically send users from an insecure HTTP site to a secure HTTPS site -> Option C

4. Quick Check:

   Redirect HTTP to HTTPS = Secure site [OK]

Hint: Redirect HTTP to HTTPS to secure user connections [OK]

Common Mistakes:

• Thinking redirect blocks HTTP instead of forwarding
• Believing HTTPS disables HTTP completely
• Confusing redirect with allowing both protocols

2. Which nginx configuration snippet correctly redirects all HTTP requests to HTTPS?

easy

A. server { listen 80; rewrite ^ https://$host$uri permanent; }

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

C. server { listen 80; proxy_pass https://$host$request_uri; }

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

Solution

1. Step 1: Identify correct listen port and redirect method

   HTTP listens on port 80; redirect uses 'return 301' for permanent redirect.

2. Step 2: Check syntax correctness

   server { listen 80; return 301 https://$host$request_uri; } uses 'listen 80' and 'return 301 https://$host$request_uri;' which is correct syntax.

3. Final Answer:

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

4. Quick Check:

   Port 80 + return 301 + https URL = Correct redirect [OK]

Hint: Use 'listen 80' and 'return 301 https://$host$request_uri;' [OK]

Common Mistakes:

• Using 'listen 443' for HTTP redirect
• Using 'proxy_pass' instead of 'return 301'
• Incorrect rewrite syntax causing errors

3. Given this nginx server block, what will happen when a user visits http://example.com/page?

server {
  listen 80;
  server_name example.com;
  return 301 https://$host$request_uri;
}

medium

A. The user will see the HTTP version of the page without redirection

B. The user will be redirected to https://example.com/page with a permanent redirect

C. The server will return a 404 error

D. The server will proxy the request to HTTPS without changing the URL

Solution

1. Step 1: Analyze the server block

   It listens on port 80 (HTTP) and returns a 301 redirect to HTTPS version of the requested URI.

2. Step 2: Understand the redirect effect

   User visiting http://example.com/page will be sent a permanent redirect to https://example.com/page.

3. Final Answer:

   The user will be redirected to https://example.com/page with a permanent redirect -> Option B

4. Quick Check:

   HTTP request + return 301 to HTTPS = Redirect [OK]

Hint: Return 301 sends permanent redirect to HTTPS URL [OK]

Common Mistakes:

• Assuming no redirect happens
• Confusing proxy_pass with redirect
• Expecting error instead of redirect

4. You wrote this nginx config to redirect HTTP to HTTPS but it does not work:

server {
  listen 80;
  server_name example.com;
  rewrite ^ https://$host$uri permanent;
}

What is the likely problem?

medium

A. The rewrite directive should be replaced with 'return 301 https://$host$request_uri;'

B. The rewrite directive is missing a semicolon

C. The listen port should be 443 for HTTPS

D. The server_name directive is incorrect

Solution

1. Step 1: Check rewrite vs return usage

   While rewrite can redirect, using 'return 301' is simpler and more reliable for HTTP to HTTPS redirects.

2. Step 2: Identify best practice

   Replacing rewrite with 'return 301 https://$host$request_uri;' fixes the redirect issue.

3. Final Answer:

   The rewrite directive should be replaced with 'return 301 https://$host$request_uri;' -> Option A

4. Quick Check:

   Use 'return 301' for clean HTTP to HTTPS redirect [OK]

Hint: Use 'return 301' instead of rewrite for HTTPS redirect [OK]

Common Mistakes:

• Thinking missing semicolon causes failure
• Changing listen port to 443 for HTTP redirect
• Assuming server_name is the problem

5. You want to redirect HTTP to HTTPS but only for the domain secure.example.com, leaving other domains on HTTP. Which nginx config snippet achieves this?

hard

A. server { listen 80; server_name secure.example.com; return 301 https://$host$request_uri; }

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

C. server { listen 443 ssl; server_name secure.example.com; return 301 http://$host$request_uri; }

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

Solution

1. Step 1: Match only the desired domain

   Using 'server_name secure.example.com;' limits redirect to that domain only.

2. Step 2: Redirect HTTP on port 80 to HTTPS

   Listening on port 80 and returning 301 redirect to HTTPS URL ensures only that domain redirects.

3. Final Answer:

   server { listen 80; server_name secure.example.com; return 301 https://$host$request_uri; } -> Option A

4. Quick Check:

   Specific server_name + return 301 = domain-only redirect [OK]

Hint: Use server_name to limit redirect to one domain [OK]

Common Mistakes:

• Using default_server redirects all domains
• Redirecting on port 443 instead of 80
• Using wildcard server_name '_' incorrectly