Why is the status code returned by both the first request and the forced cache 200? Are they the same?
first request juejin.im
the first three are from disk cache
the following request does not have a from disk cache, which is from the server. How to understand the 200 status code returned by both the first request and the strong cache?
browser cache:
1. Find the memory first and load it from the memory if it exists in the memory.
2. If it is not found in the memory, select the hard disk to get it, and if it is in the hard disk, load it from the hard disk;
3, if it is not found in the hard disk, then make a network request;
4, cache the loaded resources to the hard disk and memory;
the first three were loaded successfully from the hard disk, but were not found later. The request was sent successfully
the cache is not directly related to the status code, which reflects the final status of the request, such as successful 2xx, failed 5xx, address exception 4xx, redirect 3xx, and so on. Caching obviously has nothing to do with this
the server is nginx, and the following code is configured: location ~* .(css|js|apk)$ { root usr local resources; expires 12h; } using chrome access, you can see that both js and css are from memory cache and ...