Patrick Gallagher wrote:
> 
> I've never had any problems at all with the cache - Moz has been showing
> me the correct versions of pages ever day for 2 years or so - with the
> exception of a few builds that wouldn't run properly or at all. Perhaps
> your ISP corrected some sort of error in their proxy server?
> 
> Patrick
>

Well again, that would have affected IE and NC4.7x.  They worked 100%
fine, as they always have, throughout this period.  But what about the
other folks that have been seeing this - is it fixed for you guys too
now?
 
> JTK wrote:
> 
> > Johnny Yen wrote:
> >
> >> "Jay Garcia" <[EMAIL PROTECTED]> wrote in message
> >> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> >>
> >>> JTK wrote:
> >>>
> >>>
> >>>> Ok, well let me put it another way: was something broken in such a way
> >>>> that the cache now temporarily works?  I agree this is an equally
> >>>> likely
> >>>> scenario.  And one much more likely for AOL to cop to - otherwise
> >>>> they'd
> >>>> have to admit that by bringing this severe defect to the public, I
> >>>> caused the corpse to twitch a little.  For the good of the code.  And
> >>>> the Politburo.  And the handful of Mozilla users.  Everybody wins!
> >>>>
> >>>> Then again, tomorrow is another day.  Or the same day a week ago if
> >>>> the
> >>>> cache is in fact not fixed.
> >>>>
> >>>
> >>> Simply put I have no idea as I've never been able to reproduce this
> >>>
> >> problem.
> >>
> >> Has anyone?
> >
> >
> >
> > At least two others.
> >
> >>  Maybe he's been working offline...
> >
> >
> >
> > No.
> >
> >> either way, clearing the
> >> cache periodically is normal for N *and* IE.  That's why it's one of the
> >> first buttons on the pref.
> >>
> >
> >
> > I have never once done it in either IE or NC4.7x, nor have I had any
> > need to.
> >
> >
> >
> >

Reply via email to