Browser cache
The browser cache stores suitable HTTP responses for later use. Reuse and revalidation follow the applicable rules.
The browser cache stores suitable HTTP responses in the browser for reuse on later accesses. Depending on validity and instructions, a stored response can be reused or validated with the server again.
A graphic example
A hypothetical company portal uses the same logo on several pages. A usable stored response can avoid another full transfer. Reloading a page therefore does not necessarily download every file again.
The HTTP cache is not the same as cookies, local application data or the Cache API. Storage rules particularly matter for personal responses: a cookie alone does not prevent storage in a shared cache. The browser cache also does not replace an authorisation check.
Sources
Related terms
- CachingCaching reuses stored data or results. Validity and the permitted user scope belong in the design.
- Cache invalidationCache invalidation ends reuse of a stored copy under defined rules. The source record remains a separate concern.
- HTMLHTML describes the structure and meaning of web content. It identifies elements such as headings, tables and input fields.
- CSSCSS describes the presentation of structured content, including layout, colours and typography. It must fit interaction and actual content.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps