|
Hello all-
I have a rather strange problem with the webservers in my LVS cluster.
I want to enable the modules expires and headers so that I can play
tricks with a customer's incorrectly setup proxy cache ("but our access
statistics don't match yours" crap like that). I am running apache
1.3.20 with tomcat 3.2.3 (all the problem docs are straight, static html
files though).
I run configure this way for apache:
$1> ./configure \
"--with-layout=Apache" \
"--prefix=/home/apache" \
"--enable-module=so" \
"--enable-module=rewrite" \
"--enable-module=headers" \
"--enable-module=expires" \
"--enable-shared=max" \
then I make and make install.
On the two other machines (same configure statement, same apache, these
are mirrors) when I place this .htaccess file in the desired directory,
the headers are returned with the proper expires and cache-control
entries.
.htaccess:
### activate mod_expires
ExpiresActive On
### Expire .gif's 1 month from when they're accessed
ExpiresByType image/gif A2592000
ExpiresDefault "now"
### Apply a Cache-Control header to *.htm
<Files *.htm>
Header append Cache-Control "public, must-revalidate"
</Files>
returned sample header:
200 OK
Cache-Control: max-age=0, public, must-revalidate
Connection: close
Date: Thu, 11 Oct 2001 22:53:37 GMT
Accept-Ranges: bytes
Server: Apache
Content-Length: 13683
Content-Type: text/html
ETag: "83901-3573-3b794a0c"
Expires: Thu, 11 Oct 2001 22:53:37 GMT
Last-Modified: Tue, 14 Aug 2001 15:55:56 GMT
Client-Date: Thu, 11 Oct 2001 21:52:58 GMT
Client-Peer: 192.168.1.20:80
On both my LVS webservers, I cannot get them to return the headers with
any of the expires or cache-control information. These servers are
configured and built the same as the ones that I can get to work, the
only difference being that they're in an LVS cluster instead of being
standalone machines. I can't find any other difference between them and
this is driving me up a wall. Any suggestions? What am I missing?
Thanks again,
Zack
|
