HTTP/1 Pipelining support has been removed in Firefox 54

Talk about code development, features, specific bugs, enhancements, patches, and similar things.
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 bugs, git, the repositories, 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. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.

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.
alex04
Moonbather
Moonbather
Posts: 57
Joined: 2013-09-16, 16:09

HTTP/1 Pipelining support has been removed in Firefox 54

Unread post by alex04 » 2017-10-01, 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.
https://developer.mozilla.org/en-US/Firefox/Releases/54

what about PM?

dark_moon

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

Unread post by dark_moon » 2017-10-01, 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
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35478
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

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

Unread post by Moonchild » 2017-10-01, 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.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

Locked