193834 - expose prefs for HTTP 1.0/1.1 and keep-alives

Status: RESOLVED WONTFIX

(Firefox :: Settings UI, enhancement, P3)

Description

[jfchadeyron]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030217 Phoenix/0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030217 Phoenix/0.5

There isn't preference menu to enable/disable the pipelining.
We must go to locatin about:config and change :
"network.http.pipelining" and "network.http.proxy.pipelining".

Isn't possible to change that in the preferences menu like Mozilla ?

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Actual Results:  
Must go to about:config

Expected Results:  
Go to preferences menu

Comment 1

[David Tenser [:djst]]

That's a pref that would fit perfectly in my proposed new Advanced section:
http://www.mozillazine.org/forums/viewtopic.php?t=5747

Confirming.

Comment 2

[Mike Connor [:mconnor]]

taking QA contact, sorry about the bugspam

Comment 3

[Mike Connor [:mconnor]]

-> taking to evaluate what network settings are needed/wanted

Comment 4

[Mike Connor [:mconnor]]

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

Comment 5

[Mike Connor [:mconnor]]

morphing bug.  People stuck behind older proxies need to be able to choose HTTP
1.0 if required.

realistic options come down to making the connections dialog a tabbed interface
to include these options, or adding a section to the Advanced panel.

For consistency, it really should be in the connections dialog.  IE separates
this, however I think that's more confusing.

Comment 6

[Mike Connor [:mconnor]]

adding this so I don't bitrot myself, tabbed dialog looks a-okay.

Comment 7

[alanjstr]

How about moving the SSL stuff from Advanced to there, too?

But I dunno if a tabbed interface is the best way to go.

Comment 8

[Mike Connor [:mconnor]]

no, SSL doesn't belong in the connection settings, its security-related and
belongs with the security prefs (yes, there's more coming)

Comment 9

[Mike Connor [:mconnor]]

after reading things about current pipelining support (i.e. on Darin's blog) I
don't think pipelining should be exposed for now, since its not quite
stable/supported enough for a mass-market product.

Morphing bug to address prefs that may belong in the build.  Leaving at 0.8, but
this may slip

Comment 10

[Mike Connor [:mconnor]]

slipping, mostly for evaluation of need from a user vs. support perspective

Comment 11

[Mike Connor [:mconnor]]

Futuring until pipelining is useful enough to expose.  Anyone who really needs
HTTP 1.0 is "probably" a corporate entity that will deploy with that configured.

-> reassign to default owner/QA

Comment 12

[Troodon]

(In reply to comment #11)
> Futuring until pipelining is useful enough to expose.  Anyone who really needs
> HTTP 1.0 is "probably" a corporate entity that will deploy with that configured.
> 
> -> reassign to default owner/QA

It's not only about pipelining, but also about keep-alive. For example, I'm
behind a proxy, and there are very BIG problems when keep-alive is enabled. Of
course, I disabled it via about:config (I also could have done it directly on
prefs.js), but many users just don't know about these ways.

Comment 13

[Jo Hermans]

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

Comment 14

[Mike Connor [:mconnor]]

sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs,
filter on "beltznerLovesGoats" to get rid of this mass change

Comment 15

[:Gavin Sharp [email: [e-mail]]]

I don't think we have any reason to do this now.