Expires directive in Nginx - Time & Space Complexity

Time Complexity: Expires directive

O(n)

Understanding Time Complexity

We want to understand how the Expires directive affects nginx's work as it handles many requests.

Specifically, how does the time nginx spends change when more files have expiration times set?

Scenario Under Consideration

Analyze the time complexity of the following nginx configuration snippet.

location /images/ {
    expires 30d;
    add_header Cache-Control "public";
}

This snippet sets a 30-day expiration for files in the /images/ folder, telling browsers to cache them.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: nginx checks the request URL against the location and applies the expires rule.
• How many times: This check happens once per request, no loops over multiple files.

How Execution Grows With Input

Each request triggers a simple check and header addition, regardless of how many files have expires set.

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

Pattern observation: The work grows directly with the number of requests, not with the number of files configured.

Final Time Complexity

Time Complexity: O(n)

This means nginx spends time proportional to the number of requests, doing a quick check each time.

Common Mistake

[X] Wrong: "Setting expires on many files makes nginx slower for each request."

[OK] Correct: nginx applies expires per request without scanning all files, so the number of files with expires does not slow down each request.

Interview Connect

Understanding how configuration directives affect request handling time helps you explain performance impacts clearly and confidently.

Self-Check

"What if we added multiple expires directives in nested locations? How would that affect the time complexity per request?"

Practice

1. What is the main purpose of the expires directive in an nginx configuration?

easy

A. To specify the file upload size limit

B. To control how long browsers cache files before requesting them again

C. To limit the number of simultaneous connections

D. To set the server's time zone

Solution

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

   The expires directive tells browsers how long to keep files cached before checking for updates.

2. Step 2: Compare options with this function

   Only To control how long browsers cache files before requesting them again matches this purpose; others relate to different server settings.

3. Final Answer:

   To control how long browsers cache files before requesting them again -> Option B

4. Quick Check:

   Expires directive = browser cache time [OK]

Hint: Expires controls browser cache duration for files [OK]

Common Mistakes:

• Confusing expires with server timezone settings
• Thinking expires limits connections
• Mixing expires with upload size limits

2. Which of the following is the correct syntax to set the expires directive to 1 day in nginx?

easy

A. expires = 1 day;

B. expires 1 day

C. expires 24hours;

D. expires 1d;

Solution

1. Step 1: Recall nginx expires syntax

   The correct syntax uses a time value followed by a semicolon, e.g., expires 1d; for one day.

2. Step 2: Check each option for syntax correctness

   expires = 1 day; uses invalid '=' and full word 'day'; expires 1 day lacks semicolon; expires 24hours; uses invalid time unit '24hours'. Only B matches correct syntax: expires 1d;.

3. Final Answer:

   expires 1d; -> Option D

4. Quick Check:

   Correct syntax ends with semicolon and uses short time unit [OK]

Hint: Use short time units with semicolon, like 'expires 1d;' [OK]

Common Mistakes:

• Omitting semicolon at the end
• Using spaces in time value
• Writing full words like 'day' instead of 'd'

3. Given this nginx config snippet:

location ~* \.(jpg|jpeg|png)$ {
  expires 30d;
}

What will the browser do when accessing a PNG file?

medium

A. Cache the PNG file for 30 seconds

B. Never cache the PNG file

C. Cache the PNG file for 30 days before re-requesting

D. Immediately re-request the PNG file every time

Solution

1. Step 1: Analyze the regex and expires directive

   The location matches .jpg, .jpeg, and .png files and sets expires 30d;, meaning 30 days caching.

2. Step 2: Understand browser caching behavior

   Browsers will keep the PNG file cached for 30 days before checking for updates.

3. Final Answer:

   Cache the PNG file for 30 days before re-requesting -> Option C

4. Quick Check:

   Expires 30d means 30 days cache [OK]

Hint: Regex matches file types; expires sets cache time [OK]

Common Mistakes:

• Confusing days with seconds
• Ignoring regex file matching
• Assuming no caching without explicit 'no-cache'

4. Identify the error in this nginx config:

location /static/ {
  expires 10days;
}

medium

A. The time unit '10days' is invalid; should be '10d'

B. Missing semicolon after expires directive

C. Location block syntax is incorrect

D. Expires directive cannot be used inside location

Solution

1. Step 1: Check the expires time unit

   The correct time unit uses short forms like 'd' for days. '10days' is invalid syntax.

2. Step 2: Verify other syntax elements

   Semicolon is present, location syntax is correct, and expires can be used inside location.

3. Final Answer:

   The time unit '10days' is invalid; should be '10d' -> Option A

4. Quick Check:

   Use short time units like 'd' not full words [OK]

Hint: Use short units like 'd' for days, not full words [OK]

Common Mistakes:

• Writing full words for time units
• Forgetting semicolon (not the case here)
• Thinking expires can't be in location block

5. You want to set caching so that CSS files are cached for 7 days, but HTML files are never cached. Which nginx config snippet achieves this?

hard

A. location ~* \.css$ { expires 7d; } location ~* \.html$ { expires -1; }

B. location ~* \.css$ { expires 7d; } location ~* \.html$ { expires 0; }

C. location ~* \.css$ { expires 7d; } location ~* \.html$ { expires off; }

D. location ~* \.css$ { expires 7d; } location ~* \.html$ { expires never; }

Solution

1. Step 1: Recall how to disable caching in nginx

   Setting expires -1; disables caching (forces no cache) for files.

2. Step 2: Check each option for correct disables and enables

   location ~* \.css$ { expires 7d; } location ~* \.html$ { expires -1; } uses expires 7d; for CSS and expires -1; for HTML, which is correct. Others use invalid or incorrect values.

3. Final Answer:

   location ~* \.css$ { expires 7d; } location ~* \.html$ { expires -1; } -> Option A

4. Quick Check:

   Use 'expires -1;' to disable caching [OK]

Hint: Use 'expires -1;' to disable caching for files [OK]

Common Mistakes:

• Using 'expires off;' which is invalid
• Using 'expires 0;' which sets immediate expiry but not no-cache
• Using 'expires never;' which is not valid syntax