Validation-based caching in Rest API - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the cache control header for 60 seconds.

Rest API

response.headers['Cache-Control'] = '[1]'

Drag options to blanks, or click blank then click option'

Amax-age=60

Bno-cache

Cno-store

Dprivate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'no-cache' disables caching instead of setting duration.

Using 'private' restricts caching to private caches only.

Setting Cache-Control to max-age=60 tells clients to cache the response for 60 seconds.

2fill in blank

medium

Complete the code to check if the ETag header matches the client's If-None-Match header.

Rest API

if request.headers.get('If-None-Match') == [1]:

Drag options to blanks, or click blank then click option'

Arequest.headers['ETag']

Bresponse.headers['ETag']

Cresponse.headers['Cache-Control']

Drequest.headers['Cache-Control']

Attempts:

3 left

💡 Hint

Common Mistakes

Comparing with request headers instead of response headers.

Using Cache-Control header instead of ETag.

The server compares the client's If-None-Match header with the response's ETag to decide if content is unchanged.

3fill in blank

hard

Fix the error in setting the 304 Not Modified response status.

Rest API

if request.headers.get('If-None-Match') == response.headers.get('ETag'):
    return [1]

Drag options to blanks, or click blank then click option'

A500

B404

C200

D304

Attempts:

3 left

💡 Hint

Common Mistakes

Using 200 returns full content unnecessarily.

Using 404 or 500 are error codes, not cache-related.

HTTP status code 304 means Not Modified, telling the client to use cached content.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that caches only responses with status 200.

Rest API

cache = {url: response for url, response in responses.items() if response.status_code [1] [2]

Drag options to blanks, or click blank then click option'

A==

B!=

C200

D404

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' caches error responses.

Checking for 404 caches not found errors.

The comprehension keeps only responses where status_code == 200, meaning successful responses are cached.

5fill in blank

hard

Fill all three blanks to build a dictionary comprehension caching responses with ETag and max-age > 0.

Rest API

valid_cache = {url: resp for url, resp in responses.items() if resp.headers.get([1]) and int(resp.headers.get([2], 0)) [3] 0}

Drag options to blanks, or click blank then click option'

A'ETag'

B'Cache-Control'

C>

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Checking for Cache-Control in place of ETag.

Using '<' instead of '>' for max-age comparison.

This comprehension caches responses that have an ETag header and a Cache-Control max-age greater than zero.

Practice

1. What is the main purpose of validation-based caching in REST APIs?

easy

A. To encrypt data during transmission

B. To speed up the server response by skipping validation

C. To store data permanently on the client side

D. To check if the data has changed before downloading it again

Solution

1. Step 1: Understand validation-based caching concept

   It is used to avoid downloading data again if it has not changed.

2. Step 2: Identify the main purpose

   The main goal is to check if data changed before downloading again to save bandwidth and time.

3. Final Answer:

   To check if the data has changed before downloading it again -> Option D

4. Quick Check:

   Validation-based caching = check data change before download [OK]

Hint: Remember: caching avoids re-downloading unchanged data [OK]

Common Mistakes:

• Thinking caching stores data permanently
• Confusing caching with encryption
• Assuming caching skips validation

2. Which HTTP header does the client send to ask the server if the cached data is still valid?

easy

A. If-Modified-Since

B. ETag

C. If-None-Match

D. Cache-Control

Solution

1. Step 1: Identify client headers for validation

   The client uses headers to tell the server what version it has.

2. Step 2: Match header for ETag validation

   The If-None-Match header is sent with the ETag value to check if data changed.

3. Final Answer:

   If-None-Match -> Option C

4. Quick Check:

   Client asks with If-None-Match header [OK]

Hint: Client sends If-None-Match with ETag to validate cache [OK]

Common Mistakes:

• Confusing If-Modified-Since with If-None-Match
• Using Cache-Control header for validation
• Thinking ETag is sent by client

3. Given this server response to a client request with If-None-Match: "abc123" header:

HTTP/1.1 304 Not Modified
ETag: "abc123"

What does this response mean?

medium

A. The data has changed and new data is sent

B. The data has not changed; client should use cached data

C. The server does not support caching

D. The client must resend the request without ETag

Solution

1. Step 1: Understand HTTP 304 status meaning

   304 means Not Modified, so data is unchanged since last fetch.

2. Step 2: Interpret ETag match

   ETag matches client's value, so server confirms data is still valid.

3. Final Answer:

   The data has not changed; client should use cached data -> Option B

4. Quick Check:

   304 Not Modified = use cached data [OK]

Hint: 304 status means no new data, use cache [OK]

Common Mistakes:

• Thinking 304 means new data sent
• Confusing 304 with 200 OK
• Assuming server rejects caching

4. A client sends a request with header If-None-Match: "xyz789". The server responds with:

HTTP/1.1 200 OK
ETag: "abc123"
{ "data": "new content" }

What is the likely problem in this interaction?

medium

A. The server sent a different ETag, indicating data changed, so 200 OK is correct

B. The server should respond with 304 Not Modified instead of 200 OK

C. The client sent an invalid ETag header

D. The server response is missing the If-None-Match header

Solution

1. Step 1: Compare client and server ETags

   Client sent "xyz789", server responded with "abc123" which is different.

2. Step 2: Understand server response code

   Since ETags differ, data changed, so server correctly sends 200 OK with new data.

3. Final Answer:

   The server sent a different ETag, indicating data changed, so 200 OK is correct -> Option A

4. Quick Check:

   Different ETag means data changed, send 200 OK [OK]

Hint: Different ETag means new data, so 200 OK is correct [OK]

Common Mistakes:

• Expecting 304 when ETags differ
• Thinking client ETag must match server's
• Confusing If-None-Match with If-Match

5. You want to implement validation-based caching in your REST API. Which sequence correctly describes the interaction between client and server?

hard

A. Client sends request with If-None-Match header; server replies 304 if data unchanged or 200 with new data and ETag if changed

B. Server sends ETag in request; client replies 304 if data unchanged or 200 with new data if changed

C. Client sends ETag in response; server sends If-None-Match header to validate cache

D. Server always sends 200 OK with data and never uses ETag

Solution

1. Step 1: Identify correct client-server header roles

   Client sends If-None-Match with ETag to ask if data changed.

2. Step 2: Understand server response logic

   Server replies 304 if data unchanged, or 200 with new data and new ETag if changed.

3. Final Answer:

   Client sends request with If-None-Match header; server replies 304 if data unchanged or 200 with new data and ETag if changed -> Option A

4. Quick Check:

   Client sends If-None-Match; server replies 304 or 200 [OK]

Hint: Client sends If-None-Match; server replies 304 or 200 with ETag [OK]

Common Mistakes:

• Mixing up who sends ETag and If-None-Match
• Thinking server sends If-None-Match header
• Assuming server never sends 304