From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9+) Gecko/20010527 BuildID: 2001052708 If you use an automatic proxy settings and give an URL without http://-prefix (for example, www.tut.fi...) the connection refuses always. Reproducible: Always Steps to Reproduce: 1.Set an automatic proxy address without http-prefix 2.restart mozilla (?) 3.Try to connect www.mozilla.org Actual Results: I get a dialog box with connection refused Expected Results: IE can use an automatic proxy address without http-prefix.

I'm not sure what we can do here, PAC files are FILES, that need to be specified w/ URLs. Unless you can document the exact behavior of IE (what does it request if you type in just a hostname), this will probably be marked "INVALID."

This is the point: The IE works right even if I set an automatic configuration script address to www.tut.fi/network/web/cache_tut.pac but mozilla needs the address in format http://www.tut.fi/network/web/cache_tut.pac ^^^^^^^ The latter is right of course, but all other www-pages can be assigned without http-prefix, so at least the browser should generate a warning instead of refusing to connect.

I think that that is needless liberality, since a PAC file should be a user-entered value that comes from a presumably URL-literate proxy administrator. Then again I have been wrong. I would think that maybe pre-populating the field with: "http://" would be solution. Error messages on non-URL entries would be another solution.

Marking NEW.

-->jpm

adding PAC:

Serge, can you take a look at these PAC issues? Thanks - Jussi-Pekka

I have this same problem. I feel I should point out that this worked in Netscape 4.x. In fact, my settings were migrated to Mozilla with this intact.

Out of the blue, I realized how this worked in the past (or should work if we do this... For mozilla, I'm somewhat unsympathetic. For commercial products, I can see the desire to make this field less cryptic in appearance. We need to take the string in the box and call URIfixup. This has a lot of potentially strange concepts (because URI fixup is a strange thing in some ways...) Who wants to add some usability people to this bug?

to default owner

qa to me. -qawanted +4xp +nsenterprise RESOLVED/WONTFIX. If someone is really opposed to this in Mozilla, you can re-open and make your case. "A URL is a URL"

*** Bug 161908 has been marked as a duplicate of this bug. ***

I know what this has been resolved as WON'T FIX, but could I lobby for a *warning* at least? This just fails silently with a bad url string.

Sorry, didn't drill deep enough. Ignore comment.

I had trouble finding this bug, so I've tried to improve the searchability.

*** Bug 96149 has been marked as a duplicate of this bug. ***

V/wontfix: fixed in FF-only, see bug 243397.