Expiration-based caching in Rest API

Introduction

Expiration-based caching helps store data temporarily so your app can use it quickly without asking the server every time. It automatically removes old data after a set time to keep things fresh.

When you want to speed up repeated requests for the same data in a web app.

When you want to reduce server load by not fetching unchanged data too often.

When you want to make sure users see updated information after a certain time.

When you want to save bandwidth by avoiding unnecessary data transfers.

When you want to improve user experience by showing cached content instantly.

Syntax

Rest API

Cache-Control: max-age=<seconds>

This header tells the browser or client how long to keep the cached data before asking the server again.

max-age is the number of seconds the data is fresh.

Examples

Cache the response for 60 seconds before it expires.

Rest API

Cache-Control: max-age=60

Do not cache the response; always check with the server.

Rest API

Cache-Control: max-age=0, no-cache

Cache the response for 1 hour and allow shared caches (like proxies) to store it.

Rest API

Cache-Control: max-age=3600, public

Sample Program

This simple Flask app returns JSON data with a Cache-Control header telling clients to cache the response for 10 seconds. If you request the endpoint multiple times within 10 seconds, the client can use the cached data instead of asking the server again.

Rest API

from flask import Flask, jsonify, make_response
import time

app = Flask(__name__)

@app.route('/data')
def data():
    response = make_response(jsonify({'message': 'Hello, world!', 'time': time.time()}))
    response.headers['Cache-Control'] = 'max-age=10'
    return response

if __name__ == '__main__':
    app.run(debug=False)

Important Notes

Expiration-based caching works best when data changes predictably or infrequently.

Clients may ignore caching headers, so always validate important data on the server.

Use short expiration times for fast-changing data to avoid showing stale info.

Summary

Expiration-based caching stores data temporarily to speed up repeated requests.

Use the Cache-Control: max-age header to set how long data stays fresh.

This method helps reduce server load and improve user experience by avoiding unnecessary data fetching.

Practice

1. What does the Cache-Control: max-age header do in expiration-based caching?

easy

A. It deletes the cache immediately after the response.

B. It disables caching for the resource.

C. It sets how long the cached data is considered fresh.

D. It forces the client to always fetch new data.

Solution

1. Step 1: Understand the role of Cache-Control header

   The Cache-Control header controls caching behavior for HTTP responses.

2. Step 2: Identify the meaning of max-age directive

   The max-age directive specifies the time in seconds that the response is considered fresh and can be served from cache.

3. Final Answer:

   It sets how long the cached data is considered fresh. -> Option C

4. Quick Check:

   max-age = cache freshness duration [OK]

Hint: Remember max-age sets cache freshness time in seconds [OK]

Common Mistakes:

• Confusing max-age with disabling cache
• Thinking max-age deletes cache immediately
• Assuming max-age forces fresh fetch every time

2. Which of the following is the correct syntax to set a cache expiration of 300 seconds in an HTTP response header?

easy

A. Cache-Control: maxage: 300

B. Cache-Control: max-age=300

C. Cache-Control: expire=300

D. Cache-Control: timeout=300

Solution

1. Step 1: Recall correct Cache-Control syntax

   The Cache-Control header uses directives separated by commas, with max-age specified as max-age=seconds.

2. Step 2: Compare options to correct syntax

   Only Cache-Control: max-age=300 uses the correct format: max-age=300.

3. Final Answer:

   Cache-Control: max-age=300 -> Option B

4. Quick Check:

   Correct header syntax = max-age=seconds [OK]

Hint: Use equal sign (=) with max-age, no spaces [OK]

Common Mistakes:

• Using colon instead of equal sign
• Using incorrect directive names like expire or timeout
• Adding spaces inside the directive

3. Given this HTTP response header:
Cache-Control: max-age=10
What will happen if a client requests the same resource 5 seconds later?

medium

A. The client will use the cached response without contacting the server.

B. The client will ignore the cache and fetch new data from the server.

C. The client will receive a 404 error.

D. The client will refresh the cache but still use old data.

Solution

1. Step 1: Understand max-age meaning

   max-age=10 means the cached data is fresh for 10 seconds after the first fetch.

2. Step 2: Check time elapsed since caching

   5 seconds is less than 10 seconds, so cache is still fresh and valid.

3. Final Answer:

   The client will use the cached response without contacting the server. -> Option A

4. Quick Check:

   Elapsed time < max-age = use cache [OK]

Hint: If request time < max-age, cache is used [OK]

Common Mistakes:

• Assuming cache expires immediately
• Thinking client always fetches new data
• Confusing max-age with cache invalidation

4. You set Cache-Control: max-age=60 but clients still fetch new data every time. What is the likely mistake?

medium

A. The client does not support caching headers.

B. The max-age value should be in milliseconds, not seconds.

C. The resource URL is missing a file extension.

D. The server is sending no-cache header overriding max-age.

Solution

1. Step 1: Check for conflicting headers

   If the server sends a no-cache directive, it forces clients to revalidate or fetch fresh data despite max-age.

2. Step 2: Understand max-age units and client support

   max-age is in seconds, and most clients support caching headers, so these are unlikely causes.

3. Final Answer:

   The server is sending no-cache header overriding max-age. -> Option D

4. Quick Check:

   no-cache overrides max-age [OK]

Hint: Check for no-cache header overriding max-age [OK]

Common Mistakes:

• Confusing seconds with milliseconds for max-age
• Blaming client support without checking headers
• Assuming URL format affects caching

5. You want to cache API responses for 5 minutes but ensure clients always get fresh data after expiration. Which header setup is best?

hard

A. Cache-Control: max-age=300, must-revalidate

B. Cache-Control: max-age=300, no-store

C. Cache-Control: no-cache, max-age=300

D. Cache-Control: max-age=0, public

Solution

1. Step 1: Understand caching for 5 minutes

   max-age=300 sets cache freshness for 300 seconds (5 minutes).

2. Step 2: Ensure fresh data after expiration

   must-revalidate forces clients to check with server after max-age expires before using cached data.

3. Step 3: Evaluate other options

   no-store disables caching, no-cache forces revalidation every time, max-age=0 means no caching.

4. Final Answer:

   Cache-Control: max-age=300, must-revalidate -> Option A

5. Quick Check:

   max-age + must-revalidate = cache then fresh after expiry [OK]

Hint: Use must-revalidate with max-age for fresh data after expiry [OK]

Common Mistakes:

• Using no-store disables caching completely
• Using no-cache forces revalidation every request
• Setting max-age=0 disables caching