Post by MimJannat99 on Nov 14, 2023 3:12:10 GMT
Server caching is not surprisingly performed on the server. Browser caching is done on the client side, the visiting user. Take a closer look at the differences between caching types: Browser caching When you visit a website, you don't just download what you see the content of the page you see. In addition to images and fonts, you also need many other resources, such as CSS style sheets and Javascript files, which are downloaded and processed in the background by your browser browser caching.
Caching your browser allows it to store these files for a period of time so that you don't have to use your bandwidth to download them every time you visit a site. The storage time for files in memory is determined separately for each page photo editor by its administrator. See it in practice: Go to another subpage or article on our blog. Pay attention to how long it will take to load. Then close this page or go back in your browser and reopen it. See the difference in loading times.
Server caching Imagine you own a blog with caching enabled. The first time you visit your home page, you receive its content in the standard way: the request is received and processed by the server, and the page to be displayed is transformed into an HTML file and sent to the user's browser. server caching Since caching is enabled, the server stores the above HTML file in its RAM which is extremely fast. The next time someone views your page, the server doesn't have to re-process and convert the HTML version.
Caching your browser allows it to store these files for a period of time so that you don't have to use your bandwidth to download them every time you visit a site. The storage time for files in memory is determined separately for each page photo editor by its administrator. See it in practice: Go to another subpage or article on our blog. Pay attention to how long it will take to load. Then close this page or go back in your browser and reopen it. See the difference in loading times.
Server caching Imagine you own a blog with caching enabled. The first time you visit your home page, you receive its content in the standard way: the request is received and processed by the server, and the page to be displayed is transformed into an HTML file and sent to the user's browser. server caching Since caching is enabled, the server stores the above HTML file in its RAM which is extremely fast. The next time someone views your page, the server doesn't have to re-process and convert the HTML version.