My recorded request do not have "If-Modified-Since" field in the header. However during playback Neoload automatically adds this field with some timestamp. This results in server responding with http status code 304 instead of expected 200. Can I know why is Neoload inserting this field, and how does it determine the timestamp value.
This header is related to the cache of the resources. It is added to check if the resource has been modified on the server side.
When it is not the server replies back with a 304 which is completely normal. That means no need for the client to download the resource again since it has not been modified since the last check.
Is there a way I can disable Neoload from adding this field in header during playback.
Does someone have an answer to this question? This is still relevant today. How can we get NeoLoad to disable these fields from automatically being inserted into request headers?
You have control on the cache on the population settings: 'handle cache'.
If you want to simulate no cache, make sure you use 'New user'.
christophe answered
Toppar answered
Sathish answered
Nouredine answered
Sathish posted a new question
