Strange Caching Problem With Latest Tux

So, I have been going through the list archives and reading some of the 
issues with caching control and tux.  I am experiencing a problem that 
is somewhat related.  Namely, I can't stop IE (especially) and other 
browsers from caching when I do not want them to.

My setup:
Linux 2.4.18 w/ tux2-full-2.4.18-final-A3
tux utils 2.2.5

front end: Tux (serving all html and images)
back end:  Apache 1.3.24 w/ mod_perl 1.26 and PHP 4.1.2

Tux is listening on port 80.  Apache is on 8080 on 127.0.0.1

Everything is working fine for the most part.  However, I am hosting a 
user forum site (using phpBB 2.0) for some friends and it has suddenly 
stopped working correctly.  Namely, it seems the HTTP headers are being 
ignored and IE is caching everything served by Apache/PHP (i.e. 
/index.php).  I have checked that the correct headers are being received 
on the client (see below):

--
[greg] [~] > telnet callandor 80
Trying 216.46.76.20...
Connected to callandor.whalin.com.
Escape character is '^]'.
HEAD /forums/index.php HTTP/1.1
Host: uccforum.whalin.com

HTTP/1.1 200 OK
Date: Tue, 16 Apr 2002 15:37:41 GMT
Server: Apache/1.3.24 (Unix) mod_perl/1.26 PHP/4.1.2
X-Powered-By: PHP/4.1.2
Set-Cookie: phpbb2mysql_data=s%3A0%3A%22%22%3B; expires=Wed, 16-Apr-03 
15:37:41 GMT; path=/
Set-Cookie: phpbb2mysql_sid=2464b0b6719b6ca7a6d0ecbc6a46c43f; path=/
Cache-Control: private, pre-check=0, post-check=0, max-age=0
Expires: Tue, 16 Apr 2002 15:37:41 GMT
Last-Modified: Tue, 16 Apr 2002 15:37:41 GMT
Connection: close
Content-Type: text/html

Connection closed by foreign host.
[greg] [~] >
--

Yet, all browsers seem to be caching the pages.  With IE, even have to 
CTRL-Reload to get the page to load from the server.  Obviously, with a 
forum, this is pretty troublesome (new posts don't show up).

Now, I was able to solve this problem by shutting off etags and last 
modified generation in Tux ...

echo 0 > /proc/sys/net/tux/generate_etags
echo 0 > /proc/sys/net/tux/generate_last_mod

Now, everything works like it should.  Or no it does not!  Now, it seems 
that no images served by tux are being cached client side.  This is 
obviously not what I want either.

So, my  question is this.  Why is tux interfering with caching 
directives for pages served by Apache (or is it?)?  Any ideas as to what 
I am seeing here?

Thanks!

Greg
--
Gregory Whalin
[email protected]