Proxy headers forwarding in Nginx - Time & Space Complexity

Time Complexity: Proxy headers forwarding

O(n)

Understanding Time Complexity

When nginx forwards headers to a backend server, it processes each header line by line.

We want to understand how the time to forward headers grows as the number of headers increases.

Scenario Under Consideration

Analyze the time complexity of the following nginx proxy header forwarding snippet.

location / {
    proxy_pass http://backend;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}
    

This snippet forwards four headers from the client to the backend server for each request.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Processing each header line to add or modify before forwarding.
• How many times: Once per header line configured to forward (here, 4 times per request).

How Execution Grows With Input

As the number of headers to forward increases, nginx processes each one individually.

Input Size (number of headers)	Approx. Operations
10	10 operations
100	100 operations
1000	1000 operations

Pattern observation: The work grows directly with the number of headers to forward.

Final Time Complexity

Time Complexity: O(n)

This means the time to forward headers grows linearly with the number of headers.

Common Mistake

[X] Wrong: "Forwarding more headers does not affect performance because headers are small."

[OK] Correct: Even small headers require processing; more headers mean more work linearly.

Interview Connect

Understanding how nginx handles headers helps you reason about request processing time and scalability.

Self-Check

"What if nginx had to modify each header value dynamically instead of just forwarding? How would the time complexity change?"