RE: Strange Caching Problem With Latest Tux

Hi Jorge,

The second case works the first doesn't. You are right, it is a shot in the dark :-)

Cheers,
Nikos
> -----Original Message-----
> From: Jorge Nerin [mailto:[email protected]]
> Sent: Wednesday, April 17, 2002 5:22 PM
> To: [email protected]
> Subject: Re: Strange Caching Problem With Latest Tux
> 
> 
> Gregory Whalin wrote:
> > 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
>  > 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
> 
> In this headers there is a one second difference between date 
> and the expieres 
> and last-modified header.
> 
> > 
> > 
> > and with *.php o-r
> > -- 
> > HTTP/1.1 200 OK
> > Date: Tue, 16 Apr 2002 18:55:08 GMT
>  > 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
> 
> This time there is no difference, perhaps the browsers need 
> this difference.
> 
> > 
> > 
> > Got me?  But, it does seem to work correctly if *.php files 
> are all not 
> > readable by Tux.  Very strange.
> > 
> > Greg
> 
> It's just a shot in the dark.
> 
> -- 
> Jorge Nerin
> <[email protected]>
> 
> 
> 
> _______________________________________________
> tux-list mailing list
> [email protected]
> https://listman.redhat.com/mailman/listinfo/tux-list
>