CORS configuration in Nginx - Time & Space Complexity

Time Complexity: CORS configuration

O(n)

Understanding Time Complexity

We want to understand how the time it takes to handle CORS settings in nginx changes as more requests come in.

Specifically, how does nginx process CORS headers for each request?

Scenario Under Consideration

Analyze the time complexity of the following nginx CORS configuration snippet.

    location /api/ {
      if ($http_origin) {
        add_header Access-Control-Allow-Origin "$http_origin";
        add_header Access-Control-Allow-Credentials "true";
        add_header Access-Control-Allow-Methods "GET, POST, OPTIONS";
        add_header Access-Control-Allow-Headers "Authorization,Content-Type";
      }
      if ($request_method = 'OPTIONS') {
        return 204;
      }
      proxy_pass http://backend;
    }
    

This code sets CORS headers for requests to /api/ and handles preflight OPTIONS requests.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: nginx processes each incoming HTTP request and applies the CORS header rules.
• How many times: Once per request; no loops or recursion inside the configuration.

How Execution Grows With Input

Each request triggers the same fixed set of header additions and checks.

Input Size (n)	Approx. Operations
10	10 sets of header checks and additions
100	100 sets of header checks and additions
1000	1000 sets of header checks and additions

Pattern observation: The work grows linearly with the number of requests, but each request's processing time stays constant.

Final Time Complexity

Time Complexity: O(n)

This means the total work grows directly with the number of requests, but each request is handled in constant time.

Common Mistake

[X] Wrong: "Adding more CORS headers makes each request take longer in a way that grows with the number of headers."

[OK] Correct: The number of headers is fixed and small, so each request still takes about the same time regardless of header count.

Interview Connect

Understanding how nginx handles CORS per request helps you explain server behavior clearly and shows you can reason about request handling efficiency.

Self-Check

"What if we added a loop inside nginx config to check multiple origins dynamically? How would the time complexity change?"