Re: Netscape 2.x, proxy autoconfig and HTTP/1.1

Someone told me (I think) that NS2.0 autoproxy had some unspecified
problems, but couldn't tell me exactly what. Since we have an HTTP/1.1
webserver, this could explain a few of the more mysterious autoproxy
problems that some people experienced with NS2.0.

disclaimer: non-authoritative. May be the product of a caffiene-induced
hallucination.

D

Tom Minchin wrote:
>
> Hi,
> This isn't strictly Squid business, but recently we 'upgraded' our
> client webserver from NS Enterprise 2.0 to 3.5.1. This web server also
> houses their proxy auto config file for their 800 desktop PCs. Has anyone
> found problems with Netscape 2.0 - on a Mac - and having an HTTP/1.1 server
> handing out auto config files? The clients flounder around and claim to be
> unable to see the proxy servers defined in the config (it's a real basic
> one too).
> The only fixes are to set manual proxies or upgrade to NS 4.0 (their
> macs only have 16meg of RAM so it's not a real win-win situation).
> If it was a real server like Apache, I could just modify the response
> for the broken clients, but I don't seem to be able to.
>
> tom@interact.net.au

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GAT d- s++: a C++++$ UL++++B+++S+++C++H++U++V+++$ P+++$ L+++ E-
W+++(--)$ N++ w++$>--- t+ 5++ X+() R+ tv b++++ DI+++ e- h-@ 
------END GEEK CODE BLOCK------