Proxy settings seem to be ignored, so only direct connect works!

Mass move of all bugs without target milestones to M13.

Bulk move of all Networking-Core (to be deleted component) bugs to new Networking component.

The release notes point to bug 8559 for setting up proxies (this isn't completely finished yet in preferences (bug 16274, among others): Quoting bug 8559, "http proxy support is broken in apprunner", FIXED >------- Additional Comments From paulmac@netscape.com 09/24/99 16:31 ------- >this is working now, on all platforms, just add the prefs below to your mozilla >prefs.js file. Note the UI is not quite functional so this must be done >manually for now. Substitute servername for your server and port# for your >port. Same prefs as 4.x, BTW. >user_pref("network.proxy.http", "servername"); >user_pref("network.proxy.http_port", port#); bigler@shellus.com, please try the above and report back if it worked; Also please provide the Build ID for the version of Mozilla you are testing, located at the right-hand end of the status bar at the bottom of the window (it will look something like this: "Build ID: 2000010108" and encodes the date and hour the version you were using was built). Thanks!

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

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

As far as I can test it, proxies are working just as fine as ever. I am going to have to mark this bug as WORKSFORME. There is a separate bug 24304 which I have filed recently that prevents the changes from being reflected right away (you have to shutdown and restart the browser to be able to use proxy preferences) which might be the reason for this bug (and its dups)

I would like to reconfirm this bug -- it still doesn't work for me in 14, build 2000022414. I have tried quitting and restarting the browser and it seems to have no effect. The symptoms, if you want more detail, are that with the proxy in the Manual Proxy Configuration field for HTTP I get the error message "http://www.mozilla.org coud not be found". If I put the proxy details into auto-configure the connections time out. The proxy does work with other browsers, Mozilla does work with a direct connection, I'm restarting Mozilla between changes in deference to bug 24304. As is this bug is eminently reproducible on my system, is there anything I can do towards resolving it? Any more details I can give you

Sorry to be a pain, but good news. After my comments I re-read the notes on Bugzilla about prefs.js and opened it up in BBEdit and checked what was in there -- it matches what's in the note here (sidr@albedo.net 2000-01-02). It occurred to me to try the bare IP address of the proxy, 210.8.232.1, which worked! Then I tried the domain name of the proxy without a preceding "http://" and that worked too. That might explain the WORKSFORME status...

Based on the last comment, and the many DUPs of bug 24304, and reports of repeated proxy authentication for each GET, basic proxy functionality must be working, so reinstating WORKSFORME.

proxies working - marking verified