HTTP to HTTPS redirect in Nginx - Mini Project: Build & Apply

HTTP to HTTPS Redirect with Nginx

📖 Scenario: You manage a website that currently accepts both HTTP and HTTPS traffic. To improve security, you want to redirect all HTTP requests to HTTPS automatically.

🎯 Goal: Configure an Nginx server block to redirect all HTTP requests on port 80 to HTTPS on port 443.

📋 What You'll Learn

Create an Nginx server block listening on port 80

Add a server_name directive with the exact domain example.com

Configure a return 301 directive to redirect all HTTP requests to HTTPS

Print the final Nginx configuration for the HTTP redirect server block

💡 Why This Matters

🌍 Real World

Websites use HTTP to HTTPS redirects to ensure secure connections and protect user data.

💼 Career

DevOps engineers often configure web servers like Nginx to enforce HTTPS for security compliance.

1

Create the basic HTTP server block

Create an Nginx server block that listens on port 80 and has the server_name example.com.

Nginx

# Your code here

Hint

Use server {} block with listen 80; and server_name example.com;.

2

Add the HTTPS redirect configuration

Inside the existing server block, add a return 301 directive that redirects all requests to https://example.com$request_uri.

Nginx

server {
    listen 80;
    server_name example.com;
    # Add the redirect return directive here
}

Hint

Use return 301 https://example.com$request_uri; to redirect preserving the full request URI.

3

Add a comment explaining the redirect

Add a comment inside the server block above the return directive that says # Redirect all HTTP requests to HTTPS.

Nginx

server {
    listen 80;
    server_name example.com;
    # Add a comment explaining the redirect here
    return 301 https://example.com$request_uri;
}

Hint

Comments start with # in Nginx config files.

4

Print the final Nginx HTTP redirect configuration

Print the complete Nginx server block configuration you wrote for the HTTP to HTTPS redirect.

Nginx

# Print the final configuration below

Hint

Use a print statement to output the full server block as text.

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