Closed Bug 37632 Opened 25 years ago Closed 25 years ago

nsHTTPHandler::PrefsChanged uses different preferences types from initial preferences file

Categories

(Core :: Networking, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: cks+mozilla, Assigned: ruslan)

Details

Build: current CVS tip. nsHTTPHandler::PrefsChanged disagrees about the types of several preferences with modules/libpref/src/init/all.js. PrefsChanged uses GetIntPref() for several that the normal all.js file has set up as boolean preferences (PrefsChanged uses 0 for false and 1 for true). The ones I can see are network.http.keep-alive, network.http.proxy.keep-alive, network.http.pipelining, and network.http.proxy.pipelining. The effect of this disagreement is to render it impossible for the user to set preferences for any of those variables in their own prefs.js file. I am not sure whether all.js is wrong or PrefsChanged is wrong, so I can't attach a patch. It does seem more appropriate to use boolean preferences for these; on the other hand the code predates the all.js preferences entries (at least in uncommented, active form). ruslan is cc'd here because bonsai says he made the change to all.js that made these preferences active with boolean values.
-> ruslan
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
-> ruslan
Assignee: gagan → ruslan
Status: ASSIGNED → NEW
Keywords: nsbeta2
Target Milestone: --- → M17
Status: NEW → ASSIGNED
Fixed
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
verif.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.