The caching of the Web page is controlled by the "Cache-control" in the HTTP message header, the common value has private, No-cache, Max-age, must-revalidate, etc., the default is private. Its role is divided into the following situations according to different ways of re browsing:
(1) Open a new window
If the specified Cache-control value is private, No-cache, and Must-revalidate, the server will be accessed again when a new window is opened. If the Max-age value is specified, the server is not again accessed within the time of this value, for example:
Cache-control:max-age=5
Indicates that accessing the Web page after 5 seconds will not go to the server
(2) Enter in the Address bar
If the value is private or must-revalidate (unlike what is said on the web), the server is accessed only on the first visit and is no longer accessible. If the value is No-cache, it is accessed every time. If the value is Max-age, the access is not repeated until it expires.
(3) Press the Back button
If the value is private, must-revalidate, Max-age, it will not be accessed, and if No-cache, repeat access each time
(4) Press the Refresh button
Regardless of the value, repeated access
Use filters in projects to set Web page caching