Brotli does not work over HTTP. Period. It doesn't work, and you have yet to prove that it works. I am not the only person who can provide proof that it will not work. It clearly states it on the Google URLs that I sent you that it does not work without HTTPS, along with some reasons as to why that decision was made. You are, instead, trying to argue in face of reality. That is foolish.

> You clearly did not test this, because Chrome interprets Brotli responses just fine over HTTP. I wager Firefox does too, but I'm not about to install Firefox just to test.

This is just willful ignorance on your part. I have already tested this, and it is partially why I moved towards implementing HTTPS. The web is full of resources to back this up: https://encrypted.google.com/search?hl=en&q=Brotli%20require...

> Google engineers are right, but you are not right. You don't understand what the Google engineers are saying. The link you provided specifically has to do with the Accept-Encoding header and not Brotli support as a whole.

You don't seem to understand what you think you understand. Accept-Encoding means that it will not publicly state that it supports Brotli. I wonder why that is..... because Brotli is disabled for HTTP connections. End of story again! Stop beating the dead horse! You are wrong.

> I still don't understand why you're intentionally breaking the open web. It makes no sense.

I don't understand why you think I am. If anything, you are merely trolling and wasting your time.

> You should try actually listening

I've listened and listened, but you aren't speaking anything worth listening to. You yourself refuse to listen to my point of view and explanations, so why should I bother listening to your BS?

> You keep explaining things that are factually wrong or completely irrelevant.

I have done nothing of the sort. You, however, are stating that Brotli works over HTTP. This is factually incorrect. It is not allowed.

http://www.omgchrome.com/brotli-http-compression-coming-to-c...

> Be aware that while the compression algorithm is designed for HTTP content encoding it currently only works over HTTPS.

https://samsaffron.com/archive/2016/06/15/the-current-state-...

> Brotli is HTTPS only
>
> If you visit a site over HTTP your browser will not accept the br encoding. The reasoning for this is documented at the end of the chromium issue.

https://ayesh.me/apache-brotli

> 'm not sure if there is a technical reason behind this, but all the browsers I tested with require HTTPS in order to enable Brotli support. I have written a small post about more reasons to switch to HTTPS as well.

You are basically calling Google and each of these authors that I've linked as liars as we all have tested Brotli over HTTP and HTTPS and can concur precisely what Google and Mozilla engineers stated: Brotli is only supported with HTTPS!

> And you're going out of your way to break 99% of tools out there for no discernible reason.

First you said it was 40%, and now you are saying it's 99%? Both statistics are bogus given that around 80% of users are using either Chrome or Firefox, and versions that support Brotli!

And going out of my way? I already explained to you how I did not go out of my way. I am not targeting anyone. It was only a few lines of code to change my content cache from being Gzip-backed to Brotli-backed. You just have a persecution complex. I actually had to go out of my way earlier in order to implement a quick error message page for each of my routes because you cried so much about it. But that's all I'm going to give you, an error message.

Here's my advice to you: stop being childish. No matter how many times you are told that you are wrong, with evidence to back it up, you simply ignore it. That's called ignorance. I've repeatedly told you that you're wasting your time with this ignorance. And no matter how many times you demand someone to do something, you can't make them do something they aren't going to do.