Closed Bug 16274 Opened 25 years ago Closed 25 years ago

Writing out bad proxy prefs

Categories

(Core :: Networking, defect, P3)

x86
Other
defect

Tracking

()

VERIFIED DUPLICATE of bug 19177

People

(Reporter: tomerde, Assigned: gagan)

References

Details

I'm running milestone 10. I can't connect to site outside our fire wall. Our
proxy is running on port 80.
Assignee: chofmann → gagan
Component: other → Necko
Moving to Necko.  This is probably a DUP, and there's not much info here, but I
don't know the right bug#.
Probably unrelated to the M10 problem (was HTTP proxy support implemented in
M10), but relavent to this whole proxy issue:

I just talked to a friend of mine who was trying to use proxies in M11 and
having problems. She set up the proxy info in the M11 prefs dialog but kept
getting "can't load" messages when trying to connect through it. The problem
seemed to be that we were writing out bogus pref data to the prefs file:

user_pref("network.proxy.type", 1);
user_pref("string:network.proxy.ftp", "192.168.0.1");
user_pref("string:network.proxy.ftp_port", "80");
user_pref("string:network.proxy.http", "192.168.0.1");
user_pref("string:network.proxy.http_port", "80");
user_pref("string:network.proxy.none", "");

Both the string: before the pref name and the quotes around the port number are
bogus. Changing these manually fixed the problem.
Summary: Proxy problem → Writing out bad proxy prefs
Target Milestone: M13
Changing summary from: Proxy problem
to: Writing out bad proxy prefs
Blocks: 20400
Resetting QA Contact.
Bulk move of all Necko (to be deleted component) bugs to new Networking

component.
Based on issues, this ia a DUP of bug 19177,
"user_pref("string:network.proxy.http", "proxyhost") fails", also ASSIGNED and
M13.

Is this a "libPref" problem or a "Networking" problem? Guessing "libPref",
so that would make this bug a DUPLICATE of bug 19177.
*** Bug 19177 has been marked as a duplicate of this bug. ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
This was incorrectly marked. This is a dup of 19177 and not the other way around.


*** This bug has been marked as a duplicate of 19177 ***
Status: RESOLVED → VERIFIED
Verified this is a dupe of bog 19177
You need to log in before you can comment on or make changes to this bug.