Why Last-Modified and If-Modified-Since in Rest API? - Purpose & Use Cases

The Big Idea

What if your website could magically skip sending the same data twice?

The Scenario

Imagine you run a website that shows news articles. Every time a visitor opens your page, their browser asks your server for the full list of articles, even if nothing has changed since their last visit.

The Problem

This means your server sends the same data again and again, wasting time and internet data. Visitors wait longer, and your server works harder for no good reason.

The Solution

Using Last-Modified and If-Modified-Since headers, the server tells the browser when the content was last changed. The browser then asks only if the content is newer than what it has. If not, the server replies: "Nothing new," saving time and data.

Before vs After

✗ Before

GET /news
// Server sends full news list every time

✓ After

GET /news
If-Modified-Since: Wed, 21 Oct 2020 07:28:00 GMT
// Server replies 304 Not Modified if no changes

What It Enables

This makes websites faster and lighter by avoiding sending unchanged data repeatedly.

Real Life Example

When you refresh your favorite blog, your browser uses these headers to check if new posts exist. If not, it loads instantly without downloading everything again.

Key Takeaways

Manual repeated data sending wastes time and bandwidth.

Last-Modified and If-Modified-Since let servers and browsers talk efficiently.

This improves speed and reduces unnecessary data transfer.