How does NeoLoad effectively handle caching mechanisms within its performance testing framework?
How does NeoLoad effectively handle caching mechanisms within its performance testing framework?
NeoLoad uses different cache mechanisms HTTP headers like "IF-None-Match/If-Modified-Since based on the Etag and LastModified values.
If a page is configured to get the resources dynamically then resources will be in the cache for 5s and NeoLoad won’t ask them again until that time is reached.
Reply
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.