Credit for that solution goes to the guys at Cynergy.
The max-age value lets a cached version sit on the client for x
seconds for cases where you want to read new data periodically, but
not necessarily on every visit. Perfect for my needs.
--- In [EMAIL PROTECTED], iko_knyphausen [EMAIL
I had the same problem. Needed to insure the client was not caching the
response so data
would be current. Pragma is an HTTP/1.0 header spec. If your server is
HTTP/1.1, you
can drop the Pragma header and change the Cache-Control to no-store which was
meant
for backup caching, but works
Thanks a lot. I will try it out and report back...
--- In [EMAIL PROTECTED], Paul Strange [EMAIL PROTECTED]
wrote:
I had the same problem. Needed to insure the client was not caching
the response so data
would be current. Pragma is an HTTP/1.0 header spec. If your server is
HTTP/1.1, you
Ran into the same problem here. The root issue is a bug in some
versions of IE. You can apply an MS patch at all clients (likely not
a feasible solution), or set the cache-control header to max-age=0,
must-revalidate. That header seems to work across all browsers,
with or without SSL.
---
First of all, thanks much to everyone for helping out. You saved me a
lot of head-ache. I ended up with the latest suggestion from Doug
Response.CacheControl = max-age=0, must-revalidate (this is
ASP/VBscript)
This seems to do the trick ...
-Iko
--- In [EMAIL PROTECTED], Doug Lowder
It works ok in FF but not in IE. Peter Farland kindly had a long
exchange with me offline, and it seems in my case that the offending
HTTP response is in the header pragma CacheControl = No-cache. Problem
is, without the pragma I am not getting up-to-date data from my
HTTPService requests.
So
On Tuesday 10 Apr 2007, iko_knyphausen wrote:
It works ok in FF but not in IE. Peter Farland kindly had a long
exchange with me offline, and it seems in my case that the offending
HTTP response is in the header pragma CacheControl = No-cache. Problem
is, without the pragma I am not getting
7 matches
Mail list logo