TRENDING

TECHNOLOGY NEWS FROM AROUND THE WORLD

→
ETags and HTTP caching: why unchanged content should not be sent again
Software Engineering · 2012
Software Engineering2012

ETags and HTTP caching: why unchanged content should not be sent again

HTTP caching has long reduced unnecessary transfer between browsers and servers. In web applications of the 2012 era, ETag and If-None-Match were useful for checking whether a resource had changed.

Yazılımcının GünlüğüPublished: Nov 17, 20263 min read
JOIN THE DISCUSSION
✎ Write a comment
Reading progress0%

Historical and technical context

HTTP caching has long reduced unnecessary transfer between browsers and servers. In web applications of the 2012 era, ETag and If-None-Match were useful for checking whether a resource had changed. Correct configuration saves bandwidth as well as improving perceived performance.

Architectural decisions and constraints

After a server assigns an ETag to a resource, a client can include that value in a conditional request. If the representation is unchanged, a 304 Not Modified response may avoid sending the body again. But personalized responses must not leak through shared caches, so Cache-Control rules are equally important.

Service architectureConceptual sketch · summary of the article's technical flow
A four-stage architecture illustration prepared specifically for this article.

A practical scenario

A stable article cover image can often be cached aggressively when its URL changes for new versions. Live comment totals and authenticated account details need different rules. Experiments should inspect response headers, CDN behavior, browser network traces, and actual bytes transferred rather than relying on a single load-time number.

Verification and implications

An ETag may encode a representation identifier, but compression variants and intermediate layers affect its behavior. Cache design is therefore not simply about choosing the longest lifetime. It requires a clear policy for freshness, invalidation, privacy, and the acceptable delay before new content becomes visible.

Take a working example into real usage

A solution is not production-ready merely because a demo works. Test malformed input, access denial, network failure, timeouts, concurrency and retries. Keep API contracts explicit and display actionable errors in the interface. Verify both desktop and mobile layouts. Safe defaults, observability and reproducible tests reduce long-term maintenance cost.

Publish and maintain with measurements

Document the original problem, impacted screens and changed behavior before release. Test database compatibility, permissions and performance. A healthy HTTP response is not enough: validate rendered content and key user journeys. Retain application and data backups so a failed deployment can be rolled back responsibly.

Be the first reader ✎ Write a comment

Comments

No comments yet. Be the first to contribute.

What might reader discussion look like?Illustrative

These names, comments and editor replies are illustrative, not real visitor posts. Interactions are not saved. Use the real form below to contribute.

Riley Thompson

Reading “ETag ve HTTP önbelleklemesi: değişmeyen içeriği neden yeniden göndermemeli?” raised this question for me: migration and rollback plans should be explained.

Sample editor reply

Editor note: Forward-looking claims in an announcement are not the same as established performance results. Further evidence may change the assessment.

Shannon Blake

It is important to distinguish what the source verifies from projections about the future.

Taylor Reed

The next version's measurements should be compared with the initial announcement.

✎ Write a comment

Your first and last name will appear publicly alongside your comment.