All geek questions in one place

How does Google offer to cache client-side requests?

Well, I played with Google autocompletion and noticed a funny thing: if I, for example, type the letter "m", it executes an Ajax jsonp request. Then, if I refresh my page and enter the letter "m" again, there will be no request. The same thing happens with longer sequences of letters.

Obviously, Google uses some client-side caching. And I'm pretty sure that it doesn't store anything in cookies. I know some technologies that allow you to cache large amounts of data on the client side for using JS, but I would like to know which one uses Google?

Their code is terribly confusing, and it will take me some time to find the answer myself, so if someone points me to some top-down updated article about Google, offer to answer my question, I would be very grateful.

+3
source share
1 answer

This is a browser that handles caching. Google simply implements all the relevant headers (for example, Expires) to make sure the script is cached correctly, and then the next time he asked the browser to extract it from the cache. No fancy google tricks or magic :-)

EDIT: , , http://code.google.com/speed/page-speed/docs/caching.html. , - .

+5

Source: https://habr.com/ru/post/1731897/

More articles:


All Articles