{"id":1478,"date":"2016-01-19T23:47:24","date_gmt":"2016-01-20T04:47:24","guid":{"rendered":"https:\/\/www.redline13.com\/blog\/?p=1478"},"modified":"2016-01-19T23:47:24","modified_gmt":"2016-01-20T04:47:24","slug":"jmeter-http-cache-manager","status":"publish","type":"post","link":"https:\/\/www.redline13.com\/blog\/2016\/01\/jmeter-http-cache-manager\/","title":{"rendered":"JMeter HTTP Cache Manager"},"content":{"rendered":"

HTTP Cache Manager<\/strong>\u00a0– Why I should use it and an example.<\/p>\n

\"Screen<\/a><\/p>\n

JMeter is not a browser, but JMeter provides config elements which helped to mimic the browser behavior and make your tests more realistic. \u201cCache manager\u201d is used to simulate the browser caching behavior in Jmeter by adding caching functionality to HTTP requests within its scope.<\/p>\n

In general,\u00a0a browser caches files locally including any documents that make up a website, such as HTML files, CSS style sheets, JavaScript scripts, as well as graphic images and other multimedia content. When you revisit a website, the browser checks which content was updated in the meantime and only downloads updated files or what is not available in the cache.\u00a0Bandwidth\u00a0usage is reduced on both the user and server side and allows the page to load faster.<\/p>\n

During load testing, we do not consider static resource files (like HTML, CSS, js, images, etc.) and JMeter\u00a0does not download these static resources until it is explicitly configured to do so. HTTP Cache Manager must be included in your test plan if you have enabled your HTTP sampler to \u201cRetrieve All Embedded Resources”.<\/p>\n

\"retrieve-resources\"<\/p>\n

HTTP Cache Manager will cache these downloaded resources and will not download again from the server until these are modified.<\/p>\n

Cache manager properties<\/h3>\n

\"Screen<\/p>\n