Cache-control max-age=0 Cache-control no-cache-forces each request to be sent directly to the source server, without the checksum of the locally cached version. This is useful for verifying the authentication application (which can be used in conjunction with public) or for applications that use the latest data (all the benefits of using the cache at the expense of)
Pragma when "No-cache" appears in the request message, the application should push the request to the original server, even if it has
A copy has been cached at the last request. This will ensure that the client receives the most authoritative response. It is also used to
A forced flush of the copy is made when the client discovers that the copy is unavailable or expires in its cache.
Cache-control
Max-age>0 is extracted directly from the browser cache
Max-age<=0 when sending HTTP request acknowledgement to server, whether the resource has been modified
Some words return 200, no words return 304. Reprint Address: http://blog.csdn.net/ysdaniel/article/details/7969766
Go Cache-control max-age=0
