Maybe I'm being dense, but why not set it to what you want it to be?
Clearing it is leaving the decision up to the browser which will not
necessarily have the effect you want for all users.
Incidentally, it might not be possible if Apache is setting it. Not sure
if PHP has the ability to
Richard Heyes wrote:
Maybe I'm being dense, but why not set it to what you want it to be?
Clearing it is leaving the decision up to the browser which will not
necessarily have the effect you want for all users.
Incidentally, it might not be possible if Apache is setting it. Not
sure if PHP
I'm well-aware of what the headers are for, but you can construct expiry
headers that match the last-modified header.
If I do that the Expiry: header will be in the past and the page will be
considered expired.
--
Richard Heyes
+44 (0)800 0213 172
http://www.websupportsolutions.co.uk
Richard Heyes wrote:
I'm well-aware of what the headers are for, but you can construct
expiry headers that match the last-modified header.
If I do that the Expiry: header will be in the past and the page will be
considered expired.
Sorry, I didn't articulate what I meant very well. What I
Sorry, I didn't articulate what I meant very well. What I meant was that
you know the churn rate of your pages, so put in sensible expiry headers
based on that info.
Unfortunately I can't foresee when the pages are changed (it won't be me
who changes them).
But the better way to solve it is
FWIW, I found what was setting the cache headers - sessions. I may be
able to use session_cache_limiter(). Not Sure.
--
Richard Heyes
+44 (0)800 0213 172
http://www.websupportsolutions.co.uk
Knowledge Base and HelpDesk software
that can cut the cost of online support
--
PHP General Mailing
Richard Heyes wrote:
FWIW, I found what was setting the cache headers - sessions. I may be
able to use session_cache_limiter(). Not Sure.
Further, I found this to be what I needed:
session_cache_limiter('private_no_expire');
Cheers.
--
Richard Heyes
+44 (0)800 0213 172
Try this never gives me a problem. I use it to keep proxy servers from
caching.
?
header(HTTP/1.1 200 OK);
header(Status: 200 OK);
header(Expires: Mon, 26 Jul 1997 05:00:00 GMT); //
Date in the past
header(Last-Modified: . gmdate(D, d M Y H:i:s) . GMT); // always
modified
Try this never gives me a problem. I use it to keep proxy servers from
caching.
?
header(HTTP/1.1 200 OK);
header(Status: 200 OK);
header(Expires: Mon, 26 Jul 1997 05:00:00 GMT); //
Date in the past
header(Last-Modified: . gmdate(D, d M Y H:i:s) . GMT);// always
Let me reiterate, I want this page to get cached, but not based on an
Expires: header. Rather a Last-Modified header.
Have you tried setting the value to FALSE, NULL, or something else? I
recall having read something along those lines. I'll see if I can find
it again, meanwhile you could
[EMAIL PROTECTED] wrote:
Try this never gives me a problem. I use it to keep proxy servers from
caching.
But I want the page to be cached...
--
Richard Heyes
+44 (0)800 0213 172
http://www.websupportsolutions.co.uk
Knowledge Base and HelpDesk software
that can cut the cost of online support
Have you tried setting the value to FALSE, NULL, or something else?
Yes, nada I'm afraid.
--
Richard Heyes
+44 (0)800 0213 172
http://www.websupportsolutions.co.uk
Knowledge Base and HelpDesk software
that can cut the cost of online support
--
PHP General Mailing List
Richard Heyes wrote:
[EMAIL PROTECTED] wrote:
Try this never gives me a problem. I use it to keep proxy servers from
caching.
But I want the page to be cached...
Maybe I'm being dense, but why not set it to what you want it to be?
Clearing it is leaving the decision up to the browser which
13 matches
Mail list logo
