Rendering parameters:
maxRenderTime:
Once the rendering exceeds this parameter, the Spartacus SSR rendering slot will release a position, allowing more new requests to come in and get responses.
If a request hangs, the rendering resource occupied by hanging render will not be automatically released.
The value should always be higher than timeout and forcedSsrTimeout.
Default time: 300 seconds (5 minutes).
Cache-Control: The meaning and examples of no-store
Cache-Control is one of the HTTP header fields used to control caching behavior. Among them, no-store is an important directive, which indicates that the cache should not store anything about the client request or the server response. This directive forces every request and response to go through the network and does not allow any data to be cached.
1. Cache-Control Overview
Cache-Control is an instruction used to specify the HTTP caching mechanism, including cache storage, expiration, verification and other behaviors. no-store is one of the directives that tells all caches not to store anything, even encrypted or authenticated requests and responses. This ensures that each request obtains the latest data directly from the server, ensuring the real-time and security of the data.
2. no-store implication
2.1 No content is stored
no-storeThe main meaning of the directive is that the cache must not store data, whether it is a request or a response. The purpose of this is to ensure that the latest data is obtained from the origin server every time instead of reading from the local cache. This is important for sensitive information, personal data, or content that needs to be updated in real time.
2.2 Security and Privacy
no-store is especially important when dealing with sensitive information. For example, by using no-store when a browser handles a request that contains user authentication credentials, you can prevent these credentials from being stored in the client cache, reducing the risk of leakage.
2.3 Preventing offline access
no-store also helps prevent data leakage when accessed offline. If a device is stolen or a user forgets to log out, using no-store reduces the chance of sensitive information being leaked.
3. Usage examples of Cache-Control:no-store
Here is an example of an HTTP request and response containing Cache-Control: no-store:
3.1 Example of request header
GET /api/data HTTP/1.1
Host: example.com
Cache-Control: no-store
In this example, the client initiated a request for the /api/data resource and explicitly stated that it did not want any response data to be cached.
3.2 Response header example
HTTP/1.1 200 OK
Date: Tue, 14 Dec 2023 12:00:00 GMT
Content-Type: application/json
Cache-Control: no-store
The server uses Cache-Control: no-store in the response to ensure that the client does not cache the response. This is critical for data that contains user private data or needs to be updated in real time.
4. Summary
Cache-Control: no-storeIt is a powerful cache control directive that ensures that sensitive information is not cached and that the latest data is obtained directly from the server with each request. This is crucial to ensure the real-time, privacy and security of data. It is a good practice to use this directive when working with applications that require a high degree of security and privacy.
By using Cache-Control: no-store in HTTP headers, developers can effectively control caching behavior to ensure that sensitive data is not leaked while providing a better user experience and data security. When designing web applications, a thorough understanding and correct use of cache control directives is crucial.