Pale Moon forum

"I'm really disappointed (but not entirely surprised...) that your engineering team keeps clinging to their initial statement. The risk for middleware boxes causing issues is effectively nil, because SDCH compression was removed from Google Chrome, and other Chromium products, in version 59 (2017-06-05). [1]"
Note on this particular point if you are using a specialist server tied to particular hardware which uses old software and you can't update it then you may not be able to use browsers this new because they won't run, if you have some old tablet type device it might not have updates available - such situations exist, and people use old browsers anyway just because.

That point has nothing to do with the browser in use. Besides, I doubt that anyone would be stuck on Chrome prior to 59 in combination with obsolete hardware nobody is still employing.

There are because I've just been dealing with this exact situation on a type of server that is commonly employed worldwide providing a very widely used everyday service which quite possibly you may unwittingly use, although obviously it would be unwise to give details. The problem is say you have some expensive bit of tech that costs as much as a new car or more that has a server attached, running some specialist software written when it was built on an OS of the time, you can't afford to just ditch it after 5 or 10 years, but you can't upgrade the OS because of the special closed source software etc, and the other stuff that interfaces with it has to be compatible with said old software too. 2017 might be a long while ago in browser versions but you see plenty of 20 or 30 year old cars about, not everything gets upgraded so quickly.

Dude, stop throwing hypothetical things in the mix while being vague and being just as bad as CF saying "you can't comment on the exact circumstances". C'mon it's a clear-cut issue.
if it's a concern, then don't configure the browser to use brotli as an accepted encoding and tada, it won't be used. Problem solved for any corner case and weird-ass hypothetical situation you want to use to somehow erode my post... Probably the smart thing to do anyway because if your software is that old, it'll probably not have a safe brotli implementation anyway.

I guess I'll just have to spend more time splitting this off into a discussion thread because all you're doing is muddying the waters.

EDIT: split off.

Also, some development in the discussion, it's not transformed into something one can vote for.
Not sure if it will do any good (because I've seen that system fail plenty for other software companies) but if you think CoudFlare should treat http with the same benefits as https in terms of bandwidth savings, then please go vote:
https://community.cloudflare.com/t/brot ... use/286210