[Solved] Why does this Remix loader not cache the response as expected?export async function loader() { return new Response('Data', { headers: { 'Cache-Control': 'max-age=0, must-revalidate' } }); } | Remix

Remix - Performance

Why does this Remix loader not cache the response as expected?

export async function loader() {
  return new Response('Data', {
    headers: { 'Cache-Control': 'max-age=0, must-revalidate' }
  });
}

ACache-Control header is ignored without ETag

Bmax-age=0 forces cache to expire immediately, so no caching occurs

Cmust-revalidate disables caching completely

DResponse body must be JSON to cache

Step-by-Step Solution

Solution:

Step 1: Understand max-age=0 effect
max-age=0 means the cached response expires immediately, so browser must revalidate every time.
Step 2: Analyze must-revalidate role
must-revalidate requires revalidation but does not disable caching alone.
Final Answer:
max-age=0 forces cache to expire immediately, so no caching occurs -> Option B
Quick Check:
max-age=0 means no effective caching [OK]

Quick Trick: max-age=0 disables caching by immediate expiration [OK]

Common Mistakes:

MISTAKES

Master "Performance" in Remix

9 interactive learning modes - each teaches the same concept differently

More Remix Quizzes

Why does this Remix loader not cache the response as expected?