Netscape for assumes port 80 for proxy servers if none given. This is not in the spec. Netscape Proxy Servers (2.5 at least, possibly all) generate proxy autoconfig files without port numbers. Our proxy autoconfig file is descended from a generated file, and has no port number for our proxy. Mozilla would not work at our site, because it couldn't understand the proxy file, but it didn't report any error, either, it just would not attempt to get any files through the proxy. Auto config file works fine for all earlier versions of Netscape and IE. Example file: function FindProxyForURL(url, host) { if (dnsDomainIs(host, ".tu-bs.de")) return "DIRECT"; else return "PROXY www-cache.tu-bs.de; DIRECT"; } Desired Functionality: Report error that the Proxy Config file is bad and is being ignored OR Report that the proxy port is not being specified, and is being guessed as 80. OR report that the proxy is badly formed, and skipping the entry or something like that. cheers, Woody

Changing component.

So that is where those files are coming from...

Reporter, is this still a problem in a current build (Mozilla 1.0 or 1.1alpha)?

no answer

Previous verions of Netscape assumed a default port of 80. This was accepted as a de facto standard, and covered in bug 91630. reporter: I haven't verified that bug, so I'd be interested in knowing if it happens w/ a newer build.

No response -> WFM pi

REOPEN: I need to look at this again.

http://lxr.mozilla.org/mozilla1.0/source/netwerk/base/src/nsProxyAutoConfig.js#107 I was worried about a regression, but if this happens I'm sure someone will reopen or file a bug. I don't think we are going to add error handling because this has been resolved as de facto behavior (another lesson about writing specs) and also the error message is useless, this file would work w/ other browsers, and a user can't change the network behavior. *** This bug has been marked as a duplicate of 91630 ***

Yep, same problem. Should be fixed by the bug this was duped to. pi