Home > Article > Backend Development > A brief analysis of HTTP message header web page cache control and introduction to common header instructions_PHP tutorial
The cache of web pages is controlled by the "Cache-control" in the HTTP message header. Common values include private, no-cache, max-age, must-revalidate, etc. The default is private. Its function is divided into the following situations according to different re-browsing methods:
(1) Open a new window
The value is private, no-cache, must-revalidate, then open a new window to visit The server will be accessed again every time.
If a max-age value is specified, the server will not be accessed again within this value, for example:
Cache-control: max-age=5 (indicates 5 seconds after accessing this web page) Accessing again within seconds will not go to the server)
(2) Press Enter in the address bar
if the value is private or must-revalidate, the server will be accessed only the first time, and will not be accessed in the future. Visit again.
The value is no-cache, then it will be accessed every time.
If the value is max-age, it will not be accessed again before expiration.
(3) Press the back button
If the value of is private, must-revalidate, max-age, it will not be accessed again. If the value of
is no-cache, it will be accessed every time. Repeated visits
(4) Press the refresh button
No matter what the value is, it will be visited repeatedly
When the Cache-control value is "no-cache", accessing this page will not be on the Internet Temporary article folder leaves page backup.
In addition, caching can also be affected by specifying the "Expires" value. For example, if the Expires value is specified as a time that has long passed, then if you press Enter repeatedly in the address bar when accessing this network, the access will be repeated each time: Expires: Fri, 31 Dec 1999 16:00:00 GMT
For example : Disable page caching in IE
http response message header setting:
CacheControl = no-cache
Pragma=no-cache
Expires = -1
Expires is a good thing. If the web pages on the server change frequently, set it to -1 to indicate immediate expiration. If a web page is updated at 1 am every day, you can set Expires to 1 am the next day.
When the HTTP1.1 server specifies CacheControl = no-cache, the browser will not cache the web page.
Legacy HTTP 1.0 servers cannot use the Cache-Control header.
So in order to be backward compatible with HTTP 1.0 servers, IE provides special support for HTTP using the Pragma:no-cache header.
If the client communicates with the server over a secure connection (https://)/ and the server returns the Pragma:no-cache header in the response,
Internet Explorer will not cache the response. Note: Pragma:no-cache only prevents caching when used in a secure connection. If used in a non-secure page, the handling is the same as Expires:-1. The page will be cached but marked as expired immediately.
Header common commands
The header is divided into three parts:
The first part is the version of the HTTP protocol (HTTP-Version);
The second part is the status code (Status);
The third part is the reason phrase (Reason-Phrase).