Browser's micro-processing of F5

Today, I discussed with my colleagues about how to optimize the front-end cache. Pressing F5 in Firefox always finds that several iframe statements always return the 200 status, and 304 should be returned.

My colleague said, "ctrl + F5 indicates that this loading ignores all Expires settings, and F5 will request again ".

Then I read the article F5 and Ajax in-depth investigation, and told me that different browsers have different responses to F5.

 

New findings: It seems that the F5 of the browser (including IE/FF, other untested) should have special processing for text/html. When F5 is refreshed, almost all text/html objects do not have the Last-Modified response header information.

Colleague (xx) 16:14:54
We can understand that F5 is used to refresh the latest text/html page.