Conditional redirects with if in Nginx - Time & Space Complexity

Time Complexity: Conditional redirects with if

O(n)

Understanding Time Complexity

We want to understand how the time it takes for nginx to process conditional redirects changes as the number of conditions grows.

Specifically, how does checking multiple conditions affect performance?

Scenario Under Consideration

Analyze the time complexity of the following nginx configuration snippet.

server {
    listen 80;
    if ($host = 'example.com') {
        return 301 https://example.com$request_uri;
    }
    if ($host = 'test.com') {
        return 301 https://test.com$request_uri;
    }
    # more if conditions ...
}

This snippet checks the host header and redirects to HTTPS for specific domains using multiple if conditions.

Identify Repeating Operations

Each if condition is checked one after another until a match is found or all are checked.

• Primary operation: Sequential evaluation of if conditions.
• How many times: Number of if statements, depends on how many conditions are configured.

How Execution Grows With Input

As the number of if conditions increases, nginx checks each one in order until it finds a match.

Input Size (n)	Approx. Operations
10	Up to 10 condition checks
100	Up to 100 condition checks
1000	Up to 1000 condition checks

Pattern observation: The number of checks grows directly with the number of conditions, so more conditions mean more work.

Final Time Complexity

Time Complexity: O(n)

This means the time to process redirects grows linearly with the number of if conditions.

Common Mistake

[X] Wrong: "All if conditions run at the same time, so adding more doesn't slow nginx."

[OK] Correct: nginx checks conditions one by one, so more conditions mean more checks and more time.

Interview Connect

Understanding how nginx processes conditional redirects helps you explain real-world server behavior and performance in interviews.

Self-Check

What if we replaced multiple if conditions with a single map directive? How would the time complexity change?

Practice

1. What does the if directive do in an nginx configuration for conditional redirects?

easy

A. It logs all user requests to a file.

B. It checks a condition and performs an action like redirect if true.

C. It restarts nginx automatically.

D. It permanently disables the server.

Solution

1. Step 1: Understand the role of if in nginx

   The if directive evaluates a condition inside the server or location block.

2. Step 2: Recognize its use for redirects

   If the condition is true, nginx can perform actions like return to redirect users.

3. Final Answer:

   It checks a condition and performs an action like redirect if true. -> Option B

4. Quick Check:

   if checks condition for redirect [OK]

Hint: Remember: if tests, return redirects [OK]

Common Mistakes:

• Thinking if restarts nginx
• Confusing if with logging
• Assuming if disables server

2. Which of the following is the correct syntax to redirect all requests from /old to /new using if in nginx?

easy

A. if ($request_uri == "/old") return 301 /new;

B. if $request_uri == "/old" { return 301 /new; }

C. if ($request_uri = "/old") { return 301 /new; }

D. if $request_uri = "/old" return 301 /new;

Solution

1. Step 1: Check correct if syntax in nginx

   nginx requires parentheses around the condition and uses a single equals sign for string comparison.

2. Step 2: Confirm the block and return statement

   The condition must be inside parentheses, followed by braces with the return directive inside.

3. Final Answer:

   if ($request_uri = "/old") { return 301 /new; } -> Option C

4. Quick Check:

   Parentheses and braces with single = [OK]

Hint: Use parentheses and single = inside if [OK]

Common Mistakes:

• Using double == instead of single =
• Omitting parentheses around condition
• Missing braces around return

3. Given this nginx snippet:

server {
  listen 80;
  server_name example.com;
  location / {
    if ($http_user_agent ~* "Mobile") {
      return 302 /mobile;
    }
  }
}

What happens when a user with user agent "Mozilla Mobile" visits http://example.com/?

medium

A. They are redirected to /mobile with a 302 status.

B. They see the normal homepage without redirect.

C. They get a 404 error.

D. The server crashes due to syntax error.

Solution

1. Step 1: Understand the if condition with regex

   The condition checks if the user agent contains "Mobile" ignoring case.

2. Step 2: Apply the redirect action

   Since "Mozilla Mobile" matches, nginx returns a 302 redirect to /mobile.

3. Final Answer:

   They are redirected to /mobile with a 302 status. -> Option A

4. Quick Check:

   User agent matches regex, triggers redirect [OK]

Hint: Regex ~* means case-insensitive match [OK]

Common Mistakes:

• Ignoring case sensitivity in regex
• Assuming no redirect happens
• Thinking syntax error occurs

4. Identify the error in this nginx config snippet for redirecting /old to /new:

if $request_uri = "/old" {
  return 301 /new;
}

medium

A. Missing parentheses around the condition in if.

B. Using double equals instead of single equals.

C. Missing semicolon after if statement.

D. Incorrect return status code.

Solution

1. Step 1: Check if syntax requirements

   nginx requires the condition inside parentheses after if.

2. Step 2: Verify the given snippet

   The snippet lacks parentheses around $request_uri = "/old", causing syntax error.

3. Final Answer:

   Missing parentheses around the condition in if. -> Option A

4. Quick Check:

   if needs parentheses [OK]

Hint: Always wrap if conditions in parentheses [OK]

Common Mistakes:

• Forgetting parentheses in if
• Confusing single and double equals
• Thinking semicolon needed after if

5. You want to redirect users accessing /old only if they come from the domain example.com. Which nginx config snippet correctly does this using if?

hard

A. if ($request_uri = "/old" && $http_referer ~* "example.com") { return 301 /new; }

B. if ($request_uri = "/old") { return 301 /new if ($http_referer ~* "example.com"); }

C. if ($request_uri = "/old" || $http_referer ~* "example.com") { return 301 /new; }

D. if ($request_uri = "/old") { if ($http_referer ~* "example.com") { return 301 /new; } }

Solution

1. Step 1: Understand nginx if limitations

   nginx does not support combining conditions with && inside a single if.

2. Step 2: Use nested if for multiple conditions

   Nested if blocks allow checking one condition inside another.

3. Step 3: Analyze options

   if ($request_uri = "/old") { if ($http_referer ~* "example.com") { return 301 /new; } } uses nested if correctly; others use unsupported syntax or wrong logic.

4. Final Answer:

   if ($request_uri = "/old") { if ($http_referer ~* "example.com") { return 301 /new; } } -> Option D

5. Quick Check:

   Nested if for multiple conditions [OK]

Hint: Use nested if for multiple conditions in nginx [OK]

Common Mistakes:

• Trying to use && inside one if
• Using || instead of && for AND logic
• Placing return incorrectly