I guess all modern browsers automatically support htmlgz files etc. Basically just the html file gzipped, and that's it. Can be used as a direct replacement for html files.
Hopefully web services have proper integration for that, because HTTP already has gzip transfer (see Transfer-Encoding).
Ideally the server keeps the page as something like index.html.gz to reduce storage load, but the actual URL still just ends with index.html. Decompress to memory/cache to serve it plain, or serve it verbatim if HTTP gzip transfer actually is used.
Without that integration it is gay because it would affect URLs, and also probably double compress it if gzip transfer is used on top of the file already being gzip.
I think it’s just for if you’ve got some hd space limitations on the server. I believe if you have the server do the compression on the fly often the time to compress it is more than the time it’d take to just send raw. Depends.
It’s possible to create htaccess files that’ll auto swap calls for html files for htmlgz ones instead.
[ + ] MasklessTheGreat
[ - ] MasklessTheGreat 3 points 11 monthsMay 15, 2024 22:56:37 ago (+3/-0)
[ + ] drstrangergov
[ - ] drstrangergov 3 points 11 monthsMay 15, 2024 23:12:14 ago (+3/-0)
[ + ] SithEmpire
[ - ] SithEmpire 0 points 11 monthsMay 16, 2024 02:48:55 ago (+0/-0)
Ideally the server keeps the page as something like index.html.gz to reduce storage load, but the actual URL still just ends with index.html. Decompress to memory/cache to serve it plain, or serve it verbatim if HTTP gzip transfer actually is used.
Without that integration it is gay because it would affect URLs, and also probably double compress it if gzip transfer is used on top of the file already being gzip.
[ + ] CoronaHoax
[ - ] CoronaHoax [op] 0 points 11 monthsMay 16, 2024 06:37:18 ago (+0/-0)
It’s possible to create htaccess files that’ll auto swap calls for html files for htmlgz ones instead.
[ + ] ProudRebel
[ - ] ProudRebel 0 points 11 monthsMay 16, 2024 05:29:55 ago (+0/-0)