To pipeline Firefox or not to pipeline Firefox?

That is the question. Still says it's not supported by everything etc etc, 
so: do you do it, and does it help?  THX JLJ 

On 16-Jul-09 15:38, JLJ wrote:
> That is the question. Still says it's not supported by everything etc
> etc, so: do you do it, and does it help?  THX JLJ

If you're talking about HTTP pipelining in HTTP/1.1, it should be fine
to use it. I've always had it turned on, but never noticed anything
detrimental for it.

To turn it on, use about:config (there used to be GUI options for it,
but I don't see them anymore).

network.http.keep-alive must be set to true and network.http.version
must be set to 1.1 (which are the default values).

Set networking.http.pipelining to true to turn it on.

You can also enable it on HTTPS and proxy connections but turning on
network.http.pipelining.ssl and network.http.proxy.pipelining, but I
don't recommend it for security reasons.

More information can be found at:
http://www.mozilla.org/projects/netlib/http/pipelining-faq.html
http://kb.mozillazine.org/Network.http.pipelining
http://en.wikipedia.org/wiki/HTTP_pipelining

On 16-Jul-09 19:49, Tom Ditmars wrote:
> Set networking.http.pipelining to true to turn it on.

Correction: The preference is "network.http.pipelining".

Tom Ditmars writes:

> Set networking.http.pipelining to true to turn it on.
> 
> You can also enable it on HTTPS and proxy connections but turning on
> network.http.pipelining.ssl and network.http.proxy.pipelining, but I
> don't recommend it for security reasons.

Just for the record, setting network.http.pipelining to true overrides
the network.http.pipelining.ssl setting of false so pipelining will be
used for secure websites as well as unsecured sites:

http://kb.mozillazine.org/Network.http.pipelining.ssl

-- 
When you don't know where you're going, every road will take you there.
-Dennis

Dennis Henderson wrote:

>> You can also enable it on HTTPS and proxy connections but turning on
>> network.http.pipelining.ssl and network.http.proxy.pipelining, but I
>> don't recommend it for security reasons.
> 
> Just for the record, setting network.http.pipelining to true overrides
> the network.http.pipelining.ssl setting of false so pipelining will be
> used for secure websites as well as unsecured sites:
> 
> http://kb.mozillazine.org/Network.http.pipelining.ssl

Would http pipelining a secure website be any less secure than not?


-- 
-Scott

Lab1 writes:

> Dennis Henderson wrote:
>> Just for the record, setting network.http.pipelining to true overrides
>> the network.http.pipelining.ssl setting of false so pipelining will be
>> used for secure websites as well as unsecured sites:
>>
>> http://kb.mozillazine.org/Network.http.pipelining.ssl
> 
> Would http pipelining a secure website be any less secure than not?

No. All pipelining does is send multiple http requests in one packet
instead of sending one request per packet and waiting for a response
from the server before sending the next request in another packet. A
high-latency connection (like my satellite connection) will see more
benefit from pipelining than will a low-latency wired connection.

-- 
When you don't know where you're going, every road will take you there.
-Dennis

Dennis Henderson wrote:
> Lab1 writes:
> 
>> Dennis Henderson wrote:
>>> Just for the record, setting network.http.pipelining to true overrides
>>> the network.http.pipelining.ssl setting of false so pipelining will be
>>> used for secure websites as well as unsecured sites:
>>>
>>> http://kb.mozillazine.org/Network.http.pipelining.ssl
>> Would http pipelining [to] a secure website be any less secure than not?
> 
> No. All pipelining does is send multiple http requests in one packet
> instead of sending one request per packet and waiting for a response
> from the server before sending the next request in another packet. A
> high-latency connection (like my satellite connection) will see more
> benefit from pipelining than will a low-latency wired connection.

Thanks Dennis.

BTW, nice to see you around again. :)

Lab1 wrote:
> 
> Thanks Dennis.
> 
> BTW, nice to see you around again. :)

He's just slummin...

Lab1 writes:

> Dennis Henderson wrote:
>> Lab1 writes:
>>> Dennis Henderson wrote:
>>>> Just for the record, setting network.http.pipelining to true overrides
>>>> the network.http.pipelining.ssl setting of false so pipelining will be
>>>> used for secure websites as well as unsecured sites:
>>>>
>>>> http://kb.mozillazine.org/Network.http.pipelining.ssl
>>> Would http pipelining [to] a secure website be any less secure than not?
>> No. All pipelining does is send multiple http requests in one packet
>> instead of sending one request per packet and waiting for a response
>> from the server before sending the next request in another packet. A
>> high-latency connection (like my satellite connection) will see more
>> benefit from pipelining than will a low-latency wired connection.
> 
> Thanks Dennis.

My pleasure...

> BTW, nice to see you around again. :)

Looks like y'all will be stuck with me for a while again. Sis-in-law is
having a series of operations--one per week for the next few weeks--and
Wife will play nursemaid to her for the duration, so I'll be home alone
with nothing better to do a good deal of that time...

-- 
When you don't know where you're going, every road will take you there.
-Dennis

nobody writes:

> Lab1 wrote:
>> Thanks Dennis.
>>
>> BTW, nice to see you around again. :)
> 
> He's just slummin...

It keeps me humble...

-- 
When you don't know where you're going, every road will take you there.
-Dennis