Browser Cache

The browser cache is a store on the visitor's device holding copies of resources such as images, CSS, JavaScript and sometimes HTML. When the same resource is needed again, the browser can reuse the copy instead of downloading it.

Why it matters

Caching makes repeat page views faster and reduces load on your server and bandwidth bill. It also explains why visitors sometimes see an old version of a page after you update it. Response headers like Cache-Control and ETag decide how long a copy is considered fresh.

Example

Cache-Control: public, max-age=31536000, immutable

This tells the browser it may reuse a file for a year without asking. Many sites name files with a hash (app.3f9c2.js) so a new version gets a new URL and bypasses the old cached copy.

Common mistakes

• Caching HTML for a long time, so visitors miss updates.
• Giving static assets no cache headers at all, forcing re-downloads every visit.
• Debugging with a warm cache; test with a hard refresh or private window.

Related

• Cache-Control
• Web browser
• TTL
• CDN
• टूल: Http header checker

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.