6 Answers, 1 is accepted
Hello Herson,
In the default case, a request satisfying the browser caching policies set through Cache-Control, Expires, Vary, and ETag headers will be loaded from a local cache and won't go through the proxy. That said, as Fiddler is a web proxy, if your request is set to use a valid browser cache, it would be expected that it will continue to use that cache (until it is not expired and is a valid cache). So a solution would be to either clean your browser cache or test while changing the browser cache policies set through the related request/response headers.
Regards,
Nick Iliev
Progress Telerik
Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.
Hi Herson,
You should be able to set Cache-Control with max-age=<seconds> .
max-age=<seconds>
The maximum amount of time a resource is considered fresh. Unlike Expires, this directive is relative to the time of the request.
Alternatively you could use Expires header for the response:
The Expires header contains the date/time after which the response is considered stale. Invalid dates, like the value 0, represent a date in the past and mean that the resource is already expired. If there is a Cache-Control header with the max-age or s-maxage directive in the response, the Expires header is ignored.
So that said, use the Auto Responder to create a rule that sets the desired max age or the expiration date.
Regards,
Nick Iliev
Progress Telerik
Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.