Bird
Raised Fist0
Rest APIprogramming~5 mins

Last-Modified and If-Modified-Since in Rest API

Choose your learning style10 modes available
Introduction

These headers help servers and clients save time and data by checking if content has changed before sending it again.

When you want to avoid sending the same webpage or data if it hasn't changed since the last visit.
When building APIs that return data which updates occasionally, like news or weather.
When you want to reduce bandwidth usage by not sending unchanged files.
When improving website speed by letting browsers cache content smartly.
When you want to tell clients the last time your resource was updated.
Syntax
Rest API
Last-Modified: <HTTP-date>
If-Modified-Since: <HTTP-date>

Last-Modified is sent by the server to tell when the resource was last changed.

If-Modified-Since is sent by the client to ask the server to send data only if it changed after this date.

Examples
Server tells client the resource was last changed on this date.
Rest API
Last-Modified: Wed, 21 Oct 2015 07:28:00 GMT
Client asks server to send data only if it changed after this date.
Rest API
If-Modified-Since: Wed, 21 Oct 2015 07:28:00 GMT
Server replies with 304 status if resource has not changed since the date client sent.
Rest API
HTTP/1.1 304 Not Modified

Sample Program

This simple server sends a fixed last modified date. If the client sends the same date in If-Modified-Since, it replies with 304 Not Modified. Otherwise, it sends the content with the Last-Modified header.

Rest API
from http.server import BaseHTTPRequestHandler, HTTPServer
from datetime import datetime

class SimpleHandler(BaseHTTPRequestHandler):
    last_modified = datetime(2024, 6, 1, 12, 0, 0)

    def do_GET(self):
        # Format last_modified as HTTP date
        last_mod_str = self.last_modified.strftime('%a, %d %b %Y %H:%M:%S GMT')

        # Get If-Modified-Since header from client
        ims = self.headers.get('If-Modified-Since')

        if ims == last_mod_str:
            # Resource not modified
            self.send_response(304)
            self.end_headers()
            return

        # Resource modified or no If-Modified-Since header
        self.send_response(200)
        self.send_header('Content-type', 'text/plain')
        self.send_header('Last-Modified', last_mod_str)
        self.end_headers()
        self.wfile.write(b'Hello! This is the latest content.')

if __name__ == '__main__':
    server_address = ('', 8000)
    httpd = HTTPServer(server_address, SimpleHandler)
    print('Server running on http://localhost:8000')
    httpd.serve_forever()
OutputSuccess
Important Notes

The date format must follow the HTTP-date format like: 'Wed, 21 Oct 2015 07:28:00 GMT'.

Clients use If-Modified-Since to avoid downloading unchanged data, saving bandwidth.

Servers respond with 304 status to tell clients to use cached data.

Summary

Last-Modified tells when data was last changed.

If-Modified-Since asks if data changed since a date.

These headers help save time and data by avoiding unnecessary downloads.

Practice

(1/5)
1. What is the main purpose of the Last-Modified header in a REST API response?
easy
A. To tell the client when the resource was last changed
B. To tell the client the size of the resource
C. To tell the client the type of the resource
D. To tell the client the server's current time

Solution

  1. Step 1: Understand the role of Last-Modified header

    The Last-Modified header indicates the date and time when the resource was last changed on the server.
  2. Step 2: Compare options with the header's purpose

    Only To tell the client when the resource was last changed correctly describes this purpose. Other options describe unrelated information.
  3. Final Answer:

    To tell the client when the resource was last changed -> Option A
  4. Quick Check:

    Last-Modified = resource last change time [OK]
Hint: Last-Modified shows last change date of resource [OK]
Common Mistakes:
  • Confusing Last-Modified with Content-Length
  • Thinking it shows server current time
  • Mixing it up with Content-Type header
2. Which of the following is the correct syntax to send an If-Modified-Since header in an HTTP request?
easy
A. If-Modified-Since: 2023-01-01T12:00:00Z
B. If-Modified-Since = "2023-01-01 12:00:00"
C. If-Modified-Since -> 01/01/2023 12:00
D. If-Modified-Since: Sun, 01 Jan 2023 12:00:00 GMT

Solution

  1. Step 1: Recall HTTP header date format

    HTTP headers use the RFC 1123 date format like Sun, 01 Jan 2023 12:00:00 GMT for date/time values.
  2. Step 2: Match options to correct format

    If-Modified-Since: Sun, 01 Jan 2023 12:00:00 GMT matches the correct header syntax and date format. Other options use invalid syntax or date formats.
  3. Final Answer:

    If-Modified-Since: Sun, 01 Jan 2023 12:00:00 GMT -> Option D
  4. Quick Check:

    If-Modified-Since uses RFC 1123 date format [OK]
Hint: Use RFC 1123 date format for If-Modified-Since header [OK]
Common Mistakes:
  • Using ISO 8601 instead of RFC 1123 format
  • Using '=' instead of ':' in header
  • Using arrow '->' instead of colon
3. Given the server responds with header Last-Modified: Wed, 10 May 2023 10:00:00 GMT, what will the server respond if the client sends If-Modified-Since: Wed, 10 May 2023 09:00:00 GMT?
medium
A. HTTP 400 Bad Request
B. HTTP 304 Not Modified
C. HTTP 200 OK with resource data
D. HTTP 500 Internal Server Error

Solution

  1. Step 1: Compare If-Modified-Since with Last-Modified

    The client's If-Modified-Since date is earlier (09:00) than the server's Last-Modified date (10:00).
  2. Step 2: Determine server response based on dates

    Since the resource was modified after the client's date, the server sends full data with HTTP 200 OK.
  3. Final Answer:

    HTTP 200 OK with resource data -> Option C
  4. Quick Check:

    If-Modified-Since < Last-Modified -> 200 OK [OK]
Hint: If client date before last change, server sends full data [OK]
Common Mistakes:
  • Thinking server sends 304 when resource changed after client date
  • Confusing 400 Bad Request with conditional headers
  • Assuming server error on date mismatch
4. A client sends If-Modified-Since: Tue, 09 May 2023 10:00:00 GMT but the server always responds with HTTP 200 OK and full data, ignoring the header. What is the likely error in server handling?
medium
A. Server does not check If-Modified-Since header before sending data
B. Server sends wrong Last-Modified date format
C. Client sent If-Modified-Since header incorrectly
D. Server is missing Content-Type header

Solution

  1. Step 1: Understand expected server behavior

    The server should compare If-Modified-Since with resource's Last-Modified and respond 304 if not changed.
  2. Step 2: Identify why server always sends 200 OK

    If server ignores the header and always sends full data, it likely does not check the If-Modified-Since header properly.
  3. Final Answer:

    Server does not check If-Modified-Since header before sending data -> Option A
  4. Quick Check:

    Ignoring If-Modified-Since means always 200 OK [OK]
Hint: Server must check If-Modified-Since to send 304 [OK]
Common Mistakes:
  • Blaming client for server ignoring header
  • Thinking wrong Last-Modified format causes 200 OK
  • Confusing Content-Type header with caching headers
5. You want to optimize your REST API to reduce bandwidth by using Last-Modified and If-Modified-Since. Which approach correctly implements this optimization?
hard
A. Ignore If-Modified-Since and always send full resource with Last-Modified
B. Send Last-Modified header with resource date; on request, check If-Modified-Since and respond 304 if unchanged
C. Send If-Modified-Since header from server to client to indicate last change
D. Use Last-Modified header only on POST requests

Solution

  1. Step 1: Understand how Last-Modified and If-Modified-Since work together

    The server sends Last-Modified header with the resource's last change date. The client sends If-Modified-Since header on next request to ask if resource changed since that date.
  2. Step 2: Implement correct server logic for optimization

    The server compares If-Modified-Since with resource's last modified date and returns HTTP 304 Not Modified if unchanged, saving bandwidth.
  3. Final Answer:

    Send Last-Modified header with resource date; on request, check If-Modified-Since and respond 304 if unchanged -> Option B
  4. Quick Check:

    Send Last-Modified + check If-Modified-Since -> 304 optimization [OK]
Hint: Send Last-Modified; respond 304 if If-Modified-Since matches [OK]
Common Mistakes:
  • Sending If-Modified-Since from server instead of client
  • Ignoring If-Modified-Since header in server logic
  • Using Last-Modified only on POST requests
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard