4 ms·

> You had to go out of your way to break support for these browsers. Literally every HTTP package (including Rocket) out of the box handles uncompressed files.

> You had to go out of your way to break support for these browsers. Literally every HTTP package (including Rocket) out of the box handles uncompressed files. You had to modify it to add always-on Brotli encoding. I did not have to go out of my way to 'break support for these browsers'. All I did was replace the gzip-compression code in my page cacher with brotli-compression code. In other words, I went from always-on Gzip encoding to always-on Brotli encoding! I have never supported serving uncompressed files! The web browsers I care about (Firefox, Chrome) support Brotli, and that's all I care about! There is no purposeful breaking of web browsers. That's just persecution complex talk. > Why do you keep repeating this? That's completely irrelevant to the discussion at hand. Nothing about this discussion has anything to do with whether or not the HTTP protocol is wrapped in SSL. You're the one that keeps bringing up that the only difference between HTTP and HTTPS is that HTTPS is HTTPS with SSL. I am merely responding to your comment that your comment about them doesn't matter! What does matter is that my website only supports the HTTPS protocol, not HTTP. The web server only listens on port 443 with TLS enabled. > So, you want a web site that completely breaks HTTP such that only works with a handful of browsers and doesn't work with the probably tens or hundreds of thousands of pieces of other software that speaks HTTP. This is nothing more than pure trolling. All major web browsers support Brotli over HTTPS. Apple's WebKit is the only man out, and they are, at best, a minority on the web. Firefox supports it, Chrome supports it, and Edge supports it. Even if Edge didn't support it, the fact that Firefox and Chrome support it is more than enough for me. Other browsers are just bonuses. Furthermore, yet again, I do not have a HTTP server, so there is no HTTP here to break! HTTPS is implemented to spec, HSTS headers and all! My website is meant to be viewed by people, not machines. In addition, as the web is moving to being HTTPS-exclusive, it's about time that you start getting used to it. You're wasting your time.

eridius 9y ago
Always-on gzip encoding is also technically broken, it's just far more likely to be supported out of the box by other HTTP clients. > What does matter is that my website only supports the HTTPS protocol No, that has literally no bearing on this discussion about your use of Brotli encoding. You're weirdly fixated with this, but it's completely irrelevant. > This is nothing more than pure trolling. Do you normally go out of your way to insult people who are trying to have a discussion with you? Because that's what calling someone a troll is. > All major web browsers support Brotli over HTTPS Why doesn't Safari count in your eyes as a major browser? Or perhaps more interestingly, why doesn't iOS Safari count? Are you really ok with your site not working for 100% of iOS users? > In addition, as the web is moving to being HTTPS-exclusive, it's about time that you start getting used to it. You're wasting your time. Why do I have to keep repeating this? HTTPS has literally nothing to do with this discussion. You keep bringing it up over and over again as if it's somehow meaningful, but all it tells me is that you literally have no idea what you're talking about.
- mmstick 9y ago
  > No, that has literally no bearing on this discussion about your use of Brotli encoding. You're weirdly fixated with this, but it's completely irrelevant. https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/JufzX024oy0/WEOGbN43AwAJ https://groups.google.com/a/chromium.org/forum/#!msg/blink-d... > > Important note: Brotli availability is restricted to HTTPS connections. You Cannot Use Brotli Without HTTPS. Chrome does not support this, and Firefox does not support this. The same goes for Edge. One of the major reasons for me moving my website to HTTPS is so that I could use Brotli compression. Otherwise, Firefox and Chrome will merely get a content encoding error page because br is an unknown encoding format when using HTTP! HTTPS is required, and Google engineers are telling you this themselves. You're wrong, and Google engineers are right. End of story. > Why doesn't Safari count in your eyes as a major browser? Or perhaps more interestingly, why doesn't iOS Safari count? Are you really ok with your site not working for 100% of iOS users? I do not care if iOS users using Safari are unable to access my website. In the same way that iOS app developers do not care that Android users cannot use their apps, I do not care if iOS users using Safari are unable to access my personal blog. My target audience is not iOS users. My target audience consists of Linux users using either Chrome or Firefox. So basically, you have tunnel vision and are just here to bicker and argue senselessly about things you don't understand or are unwilling to accept. I'm not sure why you're so upset that I have decided to not support your access to my personal blog. No matter how many times I explain things to you, you never seem to get it through your head. This is my website, not yours. I will not support gzip, and I will not support uncompressed content, nor will I support tools that only work with HTTP.
  - eridius 9y ago
    I already explained this in another comment almost an hour ago (https://news.ycombinator.com/item?id=14346188 https://news.ycombinator.com/item?id=14346188). Brotli works perfectly fine over HTTP. The only difference between HTTP and HTTPS here is Chrome does not include "br" in the Accept-Encoding header for HTTP. But it will still handle a Content-Encoding of "br" just fine over HTTP. > One of the major reasons for me moving my website to HTTPS is so that I could use Brotli compression. Why do you care so much about this particular compression format? > Otherwise, Firefox and Chrome will merely get a content encoding error page because br is an unknown encoding format when using HTTP! 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. > You're wrong, and Google engineers are right. End of story. 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. > My target audience consists of Linux users using either Chrome or Firefox. I still don't understand why you're intentionally breaking the open web. It makes no sense. > No matter how many times I explain things to you, you never seem to get it through your head. You should try actually listening. You keep explaining things that are factually wrong or completely irrelevant. You seem to not actually understand HTTP, HTTPS, Content-Encodings, or even the idea of the open web in general. And you're going out of your way to break 99% of tools out there for no discernible reason. Why do you love Brotli so much that you're willing to break HTTP just to use it?

eridius 9y ago

Always-on gzip encoding is also technically broken, it's just far more likely to be supported out of the box by other HTTP clients. > What does matter is that my website only supports the HTTPS protocol No, that has literally no bearing on this discussion about your use of Brotli encoding. You're weirdly fixated with this, but it's completely irrelevant. > This is nothing more than pure trolling. Do you normally go out of your way to insult people who are trying to have a discussion with you? Because that's what calling someone a troll is. > All major web browsers support Brotli over HTTPS Why doesn't Safari count in your eyes as a major browser? Or perhaps more interestingly, why doesn't iOS Safari count? Are you really ok with your site not working for 100% of iOS users? > In addition, as the web is moving to being HTTPS-exclusive, it's about time that you start getting used to it. You're wasting your time. Why do I have to keep repeating this? HTTPS has literally nothing to do with this discussion. You keep bringing it up over and over again as if it's somehow meaningful, but all it tells me is that you literally have no idea what you're talking about.

mmstick 9y ago
> No, that has literally no bearing on this discussion about your use of Brotli encoding. You're weirdly fixated with this, but it's completely irrelevant. https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/JufzX024oy0/WEOGbN43AwAJ https://groups.google.com/a/chromium.org/forum/#!msg/blink-d... > > Important note: Brotli availability is restricted to HTTPS connections. You Cannot Use Brotli Without HTTPS. Chrome does not support this, and Firefox does not support this. The same goes for Edge. One of the major reasons for me moving my website to HTTPS is so that I could use Brotli compression. Otherwise, Firefox and Chrome will merely get a content encoding error page because br is an unknown encoding format when using HTTP! HTTPS is required, and Google engineers are telling you this themselves. You're wrong, and Google engineers are right. End of story. > Why doesn't Safari count in your eyes as a major browser? Or perhaps more interestingly, why doesn't iOS Safari count? Are you really ok with your site not working for 100% of iOS users? I do not care if iOS users using Safari are unable to access my website. In the same way that iOS app developers do not care that Android users cannot use their apps, I do not care if iOS users using Safari are unable to access my personal blog. My target audience is not iOS users. My target audience consists of Linux users using either Chrome or Firefox. So basically, you have tunnel vision and are just here to bicker and argue senselessly about things you don't understand or are unwilling to accept. I'm not sure why you're so upset that I have decided to not support your access to my personal blog. No matter how many times I explain things to you, you never seem to get it through your head. This is my website, not yours. I will not support gzip, and I will not support uncompressed content, nor will I support tools that only work with HTTP.
- eridius 9y ago
  I already explained this in another comment almost an hour ago (https://news.ycombinator.com/item?id=14346188 https://news.ycombinator.com/item?id=14346188). Brotli works perfectly fine over HTTP. The only difference between HTTP and HTTPS here is Chrome does not include "br" in the Accept-Encoding header for HTTP. But it will still handle a Content-Encoding of "br" just fine over HTTP. > One of the major reasons for me moving my website to HTTPS is so that I could use Brotli compression. Why do you care so much about this particular compression format? > Otherwise, Firefox and Chrome will merely get a content encoding error page because br is an unknown encoding format when using HTTP! 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. > You're wrong, and Google engineers are right. End of story. 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. > My target audience consists of Linux users using either Chrome or Firefox. I still don't understand why you're intentionally breaking the open web. It makes no sense. > No matter how many times I explain things to you, you never seem to get it through your head. You should try actually listening. You keep explaining things that are factually wrong or completely irrelevant. You seem to not actually understand HTTP, HTTPS, Content-Encodings, or even the idea of the open web in general. And you're going out of your way to break 99% of tools out there for no discernible reason. Why do you love Brotli so much that you're willing to break HTTP just to use it?