This e-mail has been scanned for viruses by Verizon Business Internet
Managed Scanning Services - powered by MessageLabs. For further
information visit http://www.mci.com
--
Matthew Claridge
Product Support Engineer
RWA Limited
on 06/06/2006 15:35 Joshua Slive said the following:
On 6/6/06, Matthew Claridge <[EMAIL PROTECTED]> wrote:
on 06/06/2006 15:16 Joshua Slive said the following:
> On 6/6/06, Matthew Claridge <[EMAIL PROTECTED]> wrote:
>
>> Apache does send a Cache-control header
Seems like you have something else weird going on. The config used on
www.apache.org is
ExpiresActive On
ExpiresDefault A86400
And yet I get updated (non-zero) cache-control headers on 304 responses:
telnet www.apache.org 80
Trying 192.87.106.226...
Connected to www.apache.org.
on 06/06/2006 15:16 Joshua Slive said the following:
On 6/6/06, Matthew Claridge <[EMAIL PROTECTED]> wrote:
Apache does send a Cache-control header of "max-age=0", which if I'm
right means it isn't updatiing the expiry time?
It means the content is marked as
on 06/06/2006 14:50 Joshua Slive said the following:
On 6/6/06, Matthew Claridge <[EMAIL PROTECTED]> wrote:
on 06/06/2006 14:30 Joshua Slive said the following:
> On 6/6/06, Matthew Claridge <[EMAIL PROTECTED]> wrote:
>> We've looked into mod_expiry, bu
on 06/06/2006 14:30 Joshua Slive said the following:
On 6/6/06, Matthew Claridge <[EMAIL PROTECTED]> wrote:
Hi all,
I'm not sure if this is possible, because to me sending 304s is just
"how it all works"!...however, my boss is looking for ways to
prevent
on 06/06/2006 13:50 Marcos R. Cardoso said the following:
Boyle Owen escreveu:
There is no problem for a single instance of apache to have any
number of name-based HTTP VHs on port 80 *and* exactly one HTTPS VH
on port 443. What you can't have is name-based HTTPS VHs.
Regarding the origin
Hi all,
I'm not sure if this is possible, because to me sending 304s is just
"how it all works"!...however, my boss is looking for ways to
prevent a browser continually requesting images from our apache server -
these requests inevitably receive a 304 response and the thinking behind
this
an use the ErrorDocument directive to specify a HTML page to return
to the client in case the error occurs.
-ascs
-Original Message-----
From: Matthew Claridge [mailto:[EMAIL PROTECTED]
Sent: Friday, May 12, 2006 3:30 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Proxy errors
closed the connection.
The timeout value can be changed. ProxyTimeout surely applies, but you may also
have to change Timeout.
-ascs
-Original Message-----
From: Matthew Claridge [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 11, 2006 1:55 PM
To: users@httpd.apache.org
Subject: [EMAIL PROTEC
tanding is that this
error occurs because the proxy times out, but which timeout value is it
supposed to use?
Thanks in advance for any help you can give.
cheers
Matt
--
Matthew Claridge
Product Support Engineer
RWA Limited
Tel: 02920 815 054
Email: [EMAIL PROTECTED]
We
Hi,
This might seem like a really stoopid question, but is it possible to do
a "Redirect / http://another.server.com"; but keep the URL shown in the
address bar as the old one, at least until someone clicks a link on the
page?
I'd rather not do anything more complicated than a simple redir
On Fri, Mar 03, 2006 at 02:58:44PM +, Matthew Claridge wrote:
I'm using version 2.0.46, with Resin (not that important whats behind
apache...). I have the following config set up to rewrite some elements
of our dynamic URLs:
RewriteEngine On
ProxyMaxForward
Hi,
I've got a bit of an issue with mod_rewrite and I was hoping someone
could give me a little help :-)
I'm using version 2.0.46, with Resin (not that important whats behind
apache...). I have the following config set up to rewrite some elements
of our dynamic URLs:
RewriteEngine O
14 matches
Mail list logo
