Detailed explanation of HTTP caching mechanism
HTTP caching is a technology that improves web page performance by reducing server load, speeding up client response and saving network bandwidth. HTTP caching is mainly divided into two types: forced caching and negotiated caching.
Force caching
Forced caching allows the client to directly use locally cached resources within a specified period of time without sending a request to the server. Forced caching is controlled by the response header specified by the server, mainly through two fields: Cache-Control and Expires.
Cache-Control
Cache-Control is a general header that specifies the maximum validity period of the resource (max-age), whether the cache can be shared (public or private) and whether modification is allowed (no-cache or no -store).
Example:
<code>Cache-Control: max-age=3600</code>
The above means that the resource is valid for 3600 seconds and can be cached.
Expires
Expires is a deprecated field that specifies the absolute expiration time of the cache.
Example:
<code>Expires: Wed, 23 Aug 2024 03:36:26 GMT</code>
This means the resource will expire on August 23, 2024 at 3:36:26 AM.
If both Cache-Control and Expires exist, then Cache-Control takes precedence.
Negotiation Cache
Negotiating caching requires the client to check whether the server resource has been updated on every request. If not updated, the server returns a 304 status code and an empty response body, allowing the client to continue using the local cache. If updated, the server will return a 200 status code and the new resource, replacing the local cache. Negotiating cache involves server and client headers, mainly Last-Modified/If-Modified-Since and ETag/If-None-Match.
Last-Modified/If-Modified-Since
Last-Modified is a server-side field indicating the last modified time of the resource. Example:
<code>Last-Modified: Tue, 22 Aug 2024 02:36:26 GMT</code>
This means the resource was last modified on August 22, 2024 at 2:36:26 AM.
If-Modified-Since is a client-side field indicating the last time the resource was retrieved. Example:
<code>If-Modified-Since: Tue, 22 Aug 2024 02:36:26 GMT</code>
This means that the client retrieved the resource on August 22, 2024 at 2:36:26 AM.
If the two timestamps are equal or Last-Modified is earlier, the resource is not updated. If Last-Modified is later, the resource has been updated.
ETag/If-None-Match
ETag is a server-side field that represents a unique identifier for a resource. Example:
<code>ETag: '5d3a9f6d-1f86'</code>
This means that the identifier of the resource is "5d3a9f6d-1f86".
If-None-Match is a client-side field indicating the expected identifier of the resource. Example:
<code>If-None-Match: '5d3a9f6d-1f86'</code>
This means that the client expects a resource identifier of "5d3a9f6d-1f86".
If the two values ??match, the resource is not updated. If they are different, the resource has been updated.
HTTP Caching Best Practices
Combining negotiated caching and forced caching can effectively reduce unnecessary network requests while ensuring that users always have the latest content.
General method:
Force caching: For static resources (e.g. CSS, JS, images), set a longer cache duration. This allows the browser to retrieve resources directly from local storage without contacting the server.
Negotiation Cache: For resources that may change, use the negotiation cache. The browser will send a request to check if the resource has changed. If not, the server will return a 304 Not Modified response, allowing the browser to use local cache. If the resource has changed, the server will return 200 OK and the updated resource.
Example implementation:
Suppose we use Express.js as the backend framework:
<code>Cache-Control: max-age=3600</code>
Key Considerations
- Versioning: To maximize the effectiveness of forced caching, include version information in the resource URL, such as /static/js/main.2024082301.js. When a resource is updated, change the version number to ensure users always get the latest version.
- Cost of Negotiation Caching: Although negotiation caching reduces unnecessary data transfers, it still requires a network round trip. For resources that rarely change, forcing caching may be more efficient.
Leapcell: Your best choice for hosting backend projects
Leapcell is a new generation serverless platform for web hosting, asynchronous tasks and Redis:
Multi-language support
- Develop with Node.js, Python, Go, or Rust.
Deploy unlimited projects for free
- Pay only for what you use - no requests, no fees.
Unmatched cost-effectiveness
- Pay as you go, no inactivity fees.
- Example: $25 supports 6.94 million requests with an average response time of 60 milliseconds.
Simplified developer experience
- Intuitive UI, easy to set up.
- Fully automated CI/CD pipeline and GitOps integration.
- Real-time metrics and logging for actionable insights.
Easy scalability and high performance
- Auto-scaling to easily handle high concurrency.
- Zero operational overhead - just focus on building.
Learn more in the documentation!
Follow us on X: @LeapcellHQ
Read our blog
The above is the detailed content of HTTP Caching : Everything You Need to Know. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three common ways to initiate HTTP requests in Node.js: use built-in modules, axios, and node-fetch. 1. Use the built-in http/https module without dependencies, which is suitable for basic scenarios, but requires manual processing of data stitching and error monitoring, such as using https.get() to obtain data or send POST requests through .write(); 2.axios is a third-party library based on Promise. It has concise syntax and powerful functions, supports async/await, automatic JSON conversion, interceptor, etc. It is recommended to simplify asynchronous request operations; 3.node-fetch provides a style similar to browser fetch, based on Promise and simple syntax

JavaScript data types are divided into primitive types and reference types. Primitive types include string, number, boolean, null, undefined, and symbol. The values are immutable and copies are copied when assigning values, so they do not affect each other; reference types such as objects, arrays and functions store memory addresses, and variables pointing to the same object will affect each other. Typeof and instanceof can be used to determine types, but pay attention to the historical issues of typeofnull. Understanding these two types of differences can help write more stable and reliable code.

Which JavaScript framework is the best choice? The answer is to choose the most suitable one according to your needs. 1.React is flexible and free, suitable for medium and large projects that require high customization and team architecture capabilities; 2. Angular provides complete solutions, suitable for enterprise-level applications and long-term maintenance; 3. Vue is easy to use, suitable for small and medium-sized projects or rapid development. In addition, whether there is an existing technology stack, team size, project life cycle and whether SSR is needed are also important factors in choosing a framework. In short, there is no absolutely the best framework, the best choice is the one that suits your needs.

Hello, JavaScript developers! Welcome to this week's JavaScript news! This week we will focus on: Oracle's trademark dispute with Deno, new JavaScript time objects are supported by browsers, Google Chrome updates, and some powerful developer tools. Let's get started! Oracle's trademark dispute with Deno Oracle's attempt to register a "JavaScript" trademark has caused controversy. Ryan Dahl, the creator of Node.js and Deno, has filed a petition to cancel the trademark, and he believes that JavaScript is an open standard and should not be used by Oracle

Promise is the core mechanism for handling asynchronous operations in JavaScript. Understanding chain calls, error handling and combiners is the key to mastering their applications. 1. The chain call returns a new Promise through .then() to realize asynchronous process concatenation. Each .then() receives the previous result and can return a value or a Promise; 2. Error handling should use .catch() to catch exceptions to avoid silent failures, and can return the default value in catch to continue the process; 3. Combinators such as Promise.all() (successfully successful only after all success), Promise.race() (the first completion is returned) and Promise.allSettled() (waiting for all completions)

CacheAPI is a tool provided by the browser to cache network requests, which is often used in conjunction with ServiceWorker to improve website performance and offline experience. 1. It allows developers to manually store resources such as scripts, style sheets, pictures, etc.; 2. It can match cache responses according to requests; 3. It supports deleting specific caches or clearing the entire cache; 4. It can implement cache priority or network priority strategies through ServiceWorker listening to fetch events; 5. It is often used for offline support, speed up repeated access speed, preloading key resources and background update content; 6. When using it, you need to pay attention to cache version control, storage restrictions and the difference from HTTP caching mechanism.

JavaScript array built-in methods such as .map(), .filter() and .reduce() can simplify data processing; 1) .map() is used to convert elements one to one to generate new arrays; 2) .filter() is used to filter elements by condition; 3) .reduce() is used to aggregate data as a single value; misuse should be avoided when used, resulting in side effects or performance problems.

JavaScript's event loop manages asynchronous operations by coordinating call stacks, WebAPIs, and task queues. 1. The call stack executes synchronous code, and when encountering asynchronous tasks, it is handed over to WebAPI for processing; 2. After the WebAPI completes the task in the background, it puts the callback into the corresponding queue (macro task or micro task); 3. The event loop checks whether the call stack is empty. If it is empty, the callback is taken out from the queue and pushed into the call stack for execution; 4. Micro tasks (such as Promise.then) take precedence over macro tasks (such as setTimeout); 5. Understanding the event loop helps to avoid blocking the main thread and optimize the code execution order.
