Tux handeling requests it shouldn't handle

Hello list,

I have a strange problem now and then. Im running a fairly loaded website (+
50 r/s) and now and then i get complaints from my visitors that a reload of
a dynamic page results in an HTTP/1.1 304 Not Modified.

This is bad, because Tux is configured to leave that page to apache, but
somehow it won't.

Some data:
/etc/tux.mime.types
...
TUX/redirect                    php dsp fok phps inc phtml php3 php4 dps
...
(and a lot of stuff for the caching, which works)

Logfile:
logs# tux2w3c tux | grep 304 | grep php
213.73.241.29 - - [19/Oct/2002:15:58:55 +0200] "GET forum.fok.nl/index.php
HTTP/1.1" 304 0 "-" ""
213.46.86.33 - - [19/Oct/2002:15:58:57 +0200] "GET forum.fok.nl/index.php
HTTP/1.1" 304 0 "-" ""

telnet 0 80:
GET /index.php HTTP/1.1
Accept: */*
Referer: http://forum.fok.nl/showtopic.php/211421
Accept-Language: en-us
Accept-Encoding: gzip, deflate
If-Modified-Since: Sat, 19 Oct 2002 12:00:53 GMT
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461)
Host: forum.fok.nl
Connection: Keep-Alive

HTTP/1.1 304 Not Modified
Connection: Keep-Alive
Date: Sat, 19 Oct 2002 12:47:54 GMT
ETag: "2115-dnkjlkef"

Well this is tux, only tux uses keep alive, apache has keep alive disabled.

Can someone enlighten me?
-kees