A better fix would be to have this as a configurable parameter in the config script.
Try adding this option:
configure --disable-cache
-Nigel
--
Nigel Horne. Arranger, Composer, Conductor, Typesetter.
Owner of the brass band group of the Internet. ICQ#20252325
[EMAIL PROTECTED] http://bandsman
> Note my problem is with a TRANSPARENT proxy. I do not explicitly
> set up use of a proxy, it just sits there on my ISP's network and
> intercepts anything going out on port 80 (using a non-standard port does
> cut it out of the loop).
Don'tcha just love the ntl: proxies?
A little patch to fresh
On Thu, 17 Oct 2002, Nigel Horne <[EMAIL PROTECTED]> wrote
>On Thursday 17 Oct 2002 6:32 pm, Chris Hastie wrote:
>
>> Or perhaps if the server returned a
>> suitable header about not caching it it would help, eg
>>
>> Cache-Control: no-cache, must-revalidate
>> Pragma: no-cache
>
>It would be a mis
On Thursday 17 Oct 2002 6:32 pm, Chris Hastie wrote:
> Or perhaps if the server returned a
> suitable header about not caching it it would help, eg
>
> Cache-Control: no-cache, must-revalidate
> Pragma: no-cache
It would be a mistake to put that in.
What values do you have for these environment
Hi
I've had this problem a couple of times now. I suffer from being behind
a transparent HTTP proxy that intercepts all traffic on port 80. It's
well known amongst ntl: users that it's crap and doesn't refresh as
often as it should.
The problem I'm having is that I can see that the virus datab
