Closed Bug 136857 Opened 22 years ago Closed 22 years ago
Enable Pipelining doesn't remain disabled when HTTP 1
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9+) Gecko/20020409 BuildID: 2002040903 If I go to Edit->Preferences->Advanced->HTTP Networking and choose HTTP 1.0, then the "Enable Pipelining" option becomes disabled. This, from my sketchy understanding, is correct. However, if I shut down Mozilla, restart, and again go to Edit->Preferences->Advanced->HTTP Networking, then HTTP 1.0 is still activated, but the "Enable Pipelining" option is enabled. Reproducible: Always Steps to Reproduce: 1. Edit->Preferences->Advanced->HTTP Networking 2. Choose HTTP 1.0 3. Notice that "Enable Pipelining" becomes disabled. 4. Close Mozilla 5. Restart Mozilla 6. Edit->Preferences->Advanced->HTTP Networking 7. See that "Enable Pipelining" is enabled and can be chosen. Expected Results: I think "Enable Pipelining" should remain disabled, because it was introduced with HTTP 1.1. At the least, it shouldn't be disabled and then reenabled after restarting Mozilla.
Confirming on linux cvs 2002041022
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 2000 → All
Hardware: PC → All
doh! we should probably try to get this fix in the branch?
Target Milestone: --- → mozilla1.0
Comment on attachment 78713 [details] [diff] [review] One-line patch r=brade
Attachment #78713 - Flags: review+
Comment on attachment 78713 [details] [diff] [review] One-line patch rs=darin brade: now it all makes sense! ;-)
Attachment #78713 - Flags: superreview+
David Barnes--do you have checkin privileges? If not, I can check this fix in for you.
I don't have checkin privileges - could you do it? Thanks - that was a fast fix!
i'll land this on the trunk today.
fixed-on-trunk waiting for approval to land this on the 1.0 branch reassigning to brade
Assignee: ben → brade
Comment on attachment 78713 [details] [diff] [review] One-line patch a=asa (on behalf of drivers) for checkin to the 1.0 branch
Attachment #78713 - Flags: approval+
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Removing adt1.0.0. It's already been checked in.
adding fixed1.0.0 keyword (branch resolution). This bug has comments saying it was fixed on the 1.0 branch and a bonsai checkin comment that agrees. To verify the bug has been fixed on the 1.0 branch please replace the fixed1.0.0 keyword with verified1.0.0.
vrfy'd fixed using 2002.07.02.0x-1.0 branch comm bits on linux rh7.2, win2k and mac 10.1.5.
You need to log in before you can comment on or make changes to this bug.