4 ms·
> What about serving uncompressed content over https? I have limited bandwidth. I don't want to serve uncompressed content over HTTPS. > What about serving up
by mmstick 9y ago
> What about serving uncompressed content over https?
I have limited bandwidth. I don't want to serve uncompressed content over HTTPS.
> What about serving up an error page when the user's browser odesn't have compressor you support?
I will do that once I figure out how to get the Request header from Rocket's API.
> What about paying attention to web standards?
I'm already complying with HTTPS web standards. I'm even pending for the HSTS preload list ( https://hstspreload.org/?domain=mmstick.tk https://hstspreload.org/?domain=mmstick.tk ).
> What about people who are stuck with old software for one reason or another?
That's their problem, not mine. You shouldn't be using old web browsers and outdated systems on the web. That makes you vulnerable.
- sqeaky 9y ago> That's their problem, not mine. You shouldn't be using old web browsers and outdated systems on the web. That makes you vulnerable. You wouldn't host a page if you didn't want to share its content, doesn't failing to do so make it atleast partially your problem? You are ignoring the list of encodings the client gives you, you are paying attention to some and not all. If we all did the web wouldn't work. Maybe they have good reasons, you aren't them and you don't know their situation. But you have chosen to not share with people with tech older than one year... Step back, and try to take an objective look at this. Do you know what percentage of web browsers actually in use will work? Do you know what percentage of people visiting your page see only gibberish? Finally, Why are so many of your comments in the gray and everyone else's not in the gray? Why do so many of your technical peers disagree with you?