Re: Strange Caching Problem With Latest Tux

Certainly not being served as-is.  They look fine (except for they are 
out of date).  I did not see any diff between HEAD requests either.

With *.php o+r
--
HTTP/1.1 200 OK
Date: Tue, 16 Apr 2002 18:53:45 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 
18:53:45 GMT; path=/
Set-Cookie: phpbb2mysql_sid=abe71abb99920917dd3241d1e6e97fec; path=/
Cache-Control: private, pre-check=0, post-check=0, max-age=0
Expires: Tue, 16 Apr 2002 18:53:46 GMT
Last-Modified: Tue, 16 Apr 2002 18:53:46 GMT
Connection: close
Content-Type: text/html


and with *.php o-r
--
HTTP/1.1 200 OK
Date: Tue, 16 Apr 2002 18:55:08 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 
18:55:08 GMT; path=/
Set-Cookie: phpbb2mysql_sid=609e8ee8770bed70382340539af87d8c; path=/
Cache-Control: private, pre-check=0, post-check=0, max-age=0
Expires: Tue, 16 Apr 2002 18:55:08 GMT
Last-Modified: Tue, 16 Apr 2002 18:55:08 GMT
Connection: close
Content-Type: text/html


Got me?  But, it does seem to work correctly if *.php files are all not 
readable by Tux.  Very strange.

Greg



Ingo Molnar wrote:

>On Tue, 16 Apr 2002, Gregory Whalin wrote:
>
>>OK, now we are getting somewhere.  I started adding file types back one
>>by one.  Strange, but it broke when I changed php files back to o+r
>>(this was the last change).  But, they are getting passed through to
>>Apache or they would not even work, so this is strange.  I am forwarding
>>them through via /etc/tux.mime.types
>>
>>TUX/redirect redir shtml cgi pl jsp php
>>
>>Any ideas now?
>>
>
>safest thing would be to make the php file unreadable for TUX - that
>causes redirection anyway. Apache could still be able to read it if you
>make it owned by user nobody (or user apache - depending on your setup).
>
>TUX serving the php page as-is is definitely something that could cause
>the symptom you describe, but that should also break the page's
>functionality badly.
>
>hm, perhaps HEAD requests are somehow confused and not getting redirected
>properly? Could you check that bit?
>
>	Ingo
>
>
>
>_______________________________________________
>tux-list mailing list
>[email protected]
>https://listman.redhat.com/mailman/listinfo/tux-list
>