Re:The CSS at w3.org is gone
by zekica on Wednesday January 25, 2023 @07:03AM
(#34517263)
The problem is that they are sending gzipped css without specifying Content-Encoding in the response headers.
[ Parent
| on HN ]
HTML:
<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?!
Re:The CSS at w3.org is gone
by justinclift on Wednesday January 25, 2023 @07:15AM
(#34517353)
Tested 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) is gz encoded.
https://www.w3.org/2008/site/css/advanced.css is even still there unzipped.
Re:The CSS at w3.org is gone
by justinclift on Wednesday January 25, 2023 @07:20AM
(#34517396)
Interestingly, 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.
Re:The CSS at w3.org is gone
by ThreePinkApples on Wednesday January 25, 2023 @07:32AM
(#34517481)
And the size difference appears to be only 0.2kB? 6.1kB from the zipped version and 6.3kB for the unzipped one