> 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 p
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 anyt
> On Thu, 2003-07-24 at 09:55, Frank Maas wrote:
>> What I found was that sometimes users got served 'cached' dynamic
>> pages. Although the server should not cache the page it looked like
>> this happened whenever two requests were received at (nearly) the
>> same time by the server.
>
> What happ
On Thu, 2003-07-24 at 09:55, Frank Maas wrote:
> What I found was that sometimes users got served 'cached' dynamic pages.
> Although the server should not cache the page it looked like this happened
> whenever two requests were received at (nearly) the same time by the server.
What happens if you
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 to t
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 y
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".
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 ad
our
browser is caching the page w/o regard to these headers, then it's your
browser, not mod_perl that's broken or misconfigured.
- Kyle
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 16, 2001 10:48 AM
> To: Ask Bjo
>#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
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?
>
> --
>
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,
KO>From the code in Apache.xs, it seems like setting $r->no_cache(0) will
KO>unset 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->req
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 to
settin
13 matches
Mail list logo
