HTTP/1 Pipelining support has been removed in Firefox 54

Talk about code development, features, specific bugzilla bugs, enhancements, patches, and other highly technical things.

Moderator: satrow

Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific referenced Bugzilla bugs, mercurial, etc.

This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Most "bug reports" do not belong in this board and should initially be posted in Community Support or other relevant support boards.

Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Posts: 50
Joined: Mon, 16 Sep 2013, 16:09
Location: EU

HTTP/1 Pipelining support has been removed in Firefox 54

Unread postby alex04 » Sun, 01 Oct 2017, 16:52

HTTP/1 Pipelining support has been removed in Firefox 54. Maintaining it as we make the move into a new world full of HTTP/2 and other substantial, standardized improvements to networking performance is not worthwhile given pipelining's compatibility and performance issues. The network.http.pipelining preference (as well as the other preferences that start with "network.http.pipelining") is now ignored. See bug 1340655 for further information.

what about PM?


Re: HTTP/1 Pipelining support has been removed in Firefox 54

Unread postby dark_moon » Sun, 01 Oct 2017, 17:14

We Pale Moon should remove that? Works fine
I dont see any reason. Even as nice to have fallback from HTTP2

User avatar
Pale Moon guru
Pale Moon guru
Posts: 23047
Joined: Sun, 28 Aug 2011, 17:27
Location: 58°2'16"N 14°58'31"E

Re: HTTP/1 Pipelining support has been removed in Firefox 54

Unread postby Moonchild » Sun, 01 Oct 2017, 17:57

Sorry but pipelining is as much part of the HTTP standard as anything else. The fact that Mozilla is convinced it has serious enough issues (of which the only ones we've seen were incomplete standards support by routers and proxies on occasion) to remove it does not impact us.
They seem to have decided to remove it because of Firefox crashing on them (probably e10s related) in certain situation with pipelining enabled, and they don't want to have the maintenance burden for something they don't use, so instead of saying "no customer support for this", it's yanked out.
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne

Return to “Development (discussion)”

Who is online

Users browsing this forum: No registered users and 2 guests