On Fri, 2003-07-25 at 04:32, Frank Maas wrote:
Come to think of it, I have never had problems with mod_proxy caching
thing I didn't want cached. Quite the opposite -- I had to be very
careful with Expires headers to get anything cached at all.
I think you might be mis-diagnosing the
On Fri, 2003-07-25 at 04:32, Frank Maas wrote:
But the idea of setting the Expiry header back in time is appealing...
Come to think of it, I have never had problems with mod_proxy caching
thing I didn't want cached. Quite the opposite -- I had to be very
careful with Expires headers to get
Hi,
Recently I found some strange behaviour of the caching-functionality of
Apache. I had configured one httpd as caching proxy and a second one
creating the pages. Two kind of pages are created: dynamic ones (with
no_cache(1)) and static ones (with an expiry set to some minutes or
hours).
What I
use Expires headers instead of the no_cache() stuff?
- Perrin
David Wheeler wrote:
Huh, according to the mod_perl guide:
http://thingy.kcilink.com/modperlguide/correct_headers/2_1_3_Expires_and_Cache_Control.html
Those headers are not added by no_cache(1). But I see that, according to
the mod_perl Changes file, those headers were added
Ask Bjoern Hansen wrote:
On Thu, 15 Nov 2001, Rasoul Hajikhani wrote:
I am using $request_object-no_cache(1) with no success. Isn't it
supported any more? Can some one shed some light on this for me...
What do you mean with no success? What are you trying to do?
--
ask bjoern
#set the content type
$big_r-content_type('text/html');
$big_r-no_cache(1);
# some more code
return OK;
You *are* remembering to do
$r-send_http_header();
somewhere in (some more code), arent you?
L8r,
Rob
#!/usr/bin/perl -w
use Disclaimer qw
$r-no_cache(1) adds the headers Pragma: no-cache and Cache-control:
no-cache. So, you need to call no_cache before calling
$r-send_http_header. You can verify that it works by looking at the
headers returned by the server when you request your document. If your
browser is caching the page w/o
On Fri, 2001-11-16 at 11:59, Kyle Oppenheim wrote:
$r-no_cache(1) adds the headers Pragma: no-cache and Cache-control:
no-cache.
snip /
Huh, according to the mod_perl guide:
http://thingy.kcilink.com/modperlguide/correct_headers/2_1_3_Expires_and_Cache_Control.html
Those headers
Rob Bloodgood wrote:
#set the content type
$big_r-content_type('text/html');
$big_r-no_cache(1);
# some more code
return OK;
You *are* remembering to do
$r-send_http_header();
somewhere in (some more code), arent you?
L8r,
Rob
Hello folks,
I am using $request_object-no_cache(1) with no success. Isn't it
supported any more? Can some one shed some light on this for me...
#set the content type
$big_r-content_type('text/html');
$big_r-no_cache(1);
# some more code
return OK
On Thu, 15 Nov 2001, Rasoul Hajikhani wrote:
I am using $request_object-no_cache(1) with no success. Isn't it
supported any more? Can some one shed some light on this for me...
What do you mean with no success? What are you trying to do?
--
ask bjoern hansen, http://ask.netcetera.dk
Hello,
KOFrom the code in Apache.xs, it seems like setting $r-no_cache(0) will
KOunset the flag, but not remove the headers.
Well, the Expires header is also removed. But it's still broken; you can
verify this buggy behavior with this simple script:
use Apache ();
my $r = Apache
Dear all,
There is some kind of confusion in my head, and the Eagle book seems
to me even more confusing. Any help appreciated.
First, I always thought that no_cache() does everything regarding
headers, and that you have just to turn it on or off.
However I discovered yesterday that, at least
Apache (as in httpd) will set the 'Expires' header to the same value as the
'Date' header when no_cache is flagged in the request_rec. When your Perl
handler sets $r-no_cache(1), mod_perl (in Apache.xs) is setting the
'Pragma: no-cache' and 'Cache-control: no-cache' headers in addition
On Sun, Jan 09, 2000 at 08:45:11PM +, G.W. Haywood wrote:
On Fri, 7 Jan 2000, Randy Harmon wrote:
Does anybody have experience detecting such a condition, perhaps through one
of the client headers? I haven't had a chance to dump them - many hats.
No idea - ditto.
In any case, I
I notice that the Guide omits the mention of Netscape's ignorance of
Expires: set to the same as Date: when it mentions $r-no_cache(1)
performing that function.
Currently, I'm experiencing the problem with Netscape 4.7, although I seem
to recall the same problem in earlier releases
On Fri, 7 Jan 2000, Ask Bjoern Hansen wrote:
On Fri, 7 Jan 2000, Randy Harmon wrote:
The latest version from CVS also sets the Cache-Control: and the Pragma:
headers when you use $r-no_cache(1).
(latest version of mod_perl that is, not Apache).
- ask
--
ask bjoern hansen - http
Hi there,
On Fri, 7 Jan 2000, Randy Harmon wrote:
Currently, I'm experiencing the problem with Netscape 4.7, although I seem
to recall the same problem in earlier releases, in the case where the target
browser's clock is slow.
[snip] can be corrected by explicitly setting an Expires
Doug has made the following modification to modperl (in the CVS tree):
$r-no_cache(1) will now set the r-headers_out "Pragma" and
"Cache-control" to "no-cache"
This should work even with buggy browsers.
--
Eric
I notice that the Guide omits the m
Hello,
I would like to deny caching of pages which are under access control.
So, I looked at no_cache and browsed through the http header
produced by this method.
As far as I discovered, no_cache(1) behaves like the A option of
mod_expires. The httpd header field looks like
Expires: current
Hello,
I would like to deny caching of pages which are under access control.
So, I looked at no_cache and browsed through the http header
produced by this method.
As far as I discovered, no_cache(1) behaves like the A option of
mod_expires. The httpd header field looks like
Expires
22 matches
Mail list logo
