5 ms·
The problem is that they are sending gzipped css without specifying Content-Encoding in the response headers.
by zekica 4y ago
The problem is that they are sending gzipped css without specifying Content-Encoding in the response headers.
- deleted 4y ago[deleted]
- justinclift 4y agoTested it just now (Firefox on Linux), and the response (for me) has 'Content-Encoding: br'. So, it seems more like it's indicating Brotli compression, but the actual file (https://www.w3.org/2008/site/js/main https://www.w3.org/2008/site/js/main) is gz encoded.
- mxfh 4y agohttps://www.w3.org/2008/site/css/advanced.css https://www.w3.org/2008/site/css/advanced.css is even still there unzipped.
- justinclift 4y agoInterestingly, at least with Firefox on Linux it seems to be decompressing the .css files ok... but borking on the javascript file that has the same incorrect content encoding header.
- ThreePinkApples 4y agoAnd the size difference appears to be only 0.2kB? 6.1kB from the zipped version and 6.3kB for the unzipped one
- citrin_ru 4y agoI see advanced.css uncompressed size is 25K and compressed (by zopfli) - 5.4K
- deleted 4y ago[deleted]
- brabel 4y agoHTML: <link rel="stylesheet" href="/2008/site/css/minimum" type="text/css" media="all" /> <style type="text/css" media="print, screen and (min-width: 481px)"> /*<![CDATA[*/ @import url("/2008/site/css/advanced"); /*]]>*/ </style> <link href="/2008/site/css/minimum" rel="stylesheet" type="text/css" media="only screen and (max-width: 480px)" /> <meta name="viewport" content="width=device-width" /> <link rel="stylesheet" href="/2008/site/css/print" type="text/css" media="print" /> /2008/site/css/minimum headers: Content-Type: text/css;charset=utf-8 Transfer-Encoding: chunked Connection: keep-alive content-location: minimum.css.gz vary: negotiate,Accept-Encoding Downloading this file, I can see it's valid "gzip compressed data". Seems to be missing the Content-Encoding header?!