are you using super simple test such as "hello world" for the first one then
"hello planet" for the second and seeing the change?

I dont meant to insult your intelligence, just making sure (:

also we are talking about a file you are using <@include> with right? not a
javascript include or something like apache's #include or anything like
that?

----- Original Message ----- 
From: "Roland Dumas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 08, 2004 4:31 PM
Subject: Re: Witango-Talk: Perplexing cache situation


>
> If I have a page that uses an include and hit it, that include should be
> cached.
>
> Then I change the include and upload to server and hit that page again.
The
> change in the include is visible.
>
> Therefore include not cached
>
>
>
> On 11/8/04 4:29 PM, "Alan Wolfe" <[EMAIL PROTECTED]> wrote:
>
> > maybe you can post the include file and say how you know that it's
getting
> > changed?
> >
> > it might be some obscure thing happening where it only apears like it
isnt
> > cacheing them but in fact it is.
> >
> > ----- Original Message -----
> > From: "Roland Dumas" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Monday, November 08, 2004 4:23 PM
> > Subject: Re: Witango-Talk: Perplexing cache situation
> >
> >
> >>
> >> Ok
> >>
> >> Updated to 5.065 and got it launched.
> >>
> >> Still won't cache includes. Haven't tried applications yet.
> >>
> >> What can cause this?
> >>
> >>
> >>
________________________________________________________________________
> >> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
> >
> > ________________________________________________________________________
> > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
> >
>
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to