Re: Strange Caching Problem With Latest Tux

No, I agree, those headers are being generated by the php script and 
being served by Apache.  That I am aware of.  What has me worried is 
that they stopped being respected by browsers once I put tux in front of 
Apache (unless I shut down last_modified and etags (both have to be shut 
down)).  Tux should be serving nothing from that page except for the 
images.  Yet the entire page is being cached even with the headers sent 
below (sent by Apache).

Meaning, if I take tux out of the picture, it all works perfectly.  But 
I since Tux is supposed to be passing the request off to Apache, I do 
not understand why it is not working now.

Greg

Alex Kramarov wrote:

>From: "Gregory Whalin" <[email protected]>
>
>>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
>>
>
>since i wrote the last-modified and http expiration features in tux, i can
>tell you, that tux doesn't use the "Expires:" header, so it is probably your
>apache setting it (tux uses "Cache-Control: max-age" only )
>
>new feature coming soon - referrer image protection, like i described in my
>previous emails.
>
>Alex.
>
>
>
>_______________________________________________
>tux-list mailing list
>[email protected]
>https://listman.redhat.com/mailman/listinfo/tux-list
>