Dev Express
29-Aug-2006, 01:41 PM
Hi,
I just started testing Eurekalog in our ISAPI, and during my tests I had big
problems with getting it to work reliably until I figured out that the HTML
Responses generated from Eurekalog were cached.
This means that even though the exceptions are removed, the browser shows
the same error message when sending the same request.
To avoid caching of the responses we use something like:
Response.CustomHeaders.Add('Cache-Control=no-cache');
Response.CustomHeaders.Add('Expires=0');
I suggest to add some headers like this to the Response (perhaps optionally,
in case someone need their errors to be cacheable?)
Looks like a great product so far! Looking forward to getting it into
production.
Best Regards,
Paul Wiik
I just started testing Eurekalog in our ISAPI, and during my tests I had big
problems with getting it to work reliably until I figured out that the HTML
Responses generated from Eurekalog were cached.
This means that even though the exceptions are removed, the browser shows
the same error message when sending the same request.
To avoid caching of the responses we use something like:
Response.CustomHeaders.Add('Cache-Control=no-cache');
Response.CustomHeaders.Add('Expires=0');
I suggest to add some headers like this to the Response (perhaps optionally,
in case someone need their errors to be cacheable?)
Looks like a great product so far! Looking forward to getting it into
production.
Best Regards,
Paul Wiik