Hi, @Tom_Rupsis, I’ve check all four requests for the URL:
https://whitewater.dev/index_bundle.js
All four are getting the compressed brotli format. If some tool is telling you that some of these requested are uncompressed it is a bug in the tool itself. We sent all four compressed.
Note, I’m seeing a different user-agent
for the request you report as uncompressed. Again, all responses were served compress but the reported compressed user-agent
is this:
Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36
The user-agent
reported uncompressed (but it is really compressed) is this:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36 Edg/83.0.478.54
That is the tool/browser lying to you. Don’t believe it.
There are interesting differences in our response headers to the versions. These are the “reported uncompressed” response headers from the HAR file:
accept-ranges bytes
age 60864
cache-control public, max-age=0, must-revalidate
content-type application/javascript
date Mon, 22 Jun 2020 20:43:00 GMT
etag "1f6377ea62a71ea60cc6f10e0c64de6c-ssl-df"
server Netlify
status 200
strict-transport-security max-age=31536000
vary Accept-Encoding
x-content-encoding-over-network br
x-nf-request-id feb6caee-8f1d-49fd-9f40-173cef5c5295-13375013
Note the etag
ends in -ssl-df
. This means this response is a compressed version (the -df
is always in the etag
for a compressed response and never there for uncompressed). The -ssl
means this was an SSL response.
I also checked the x-nf-request-id
of feb6caee-8f1d-49fd-9f40-173cef5c5295-13375013
in our logs. It was Brotli compressed and the response size was 1741641 bytes.
Last but not least, the x-content-encoding-over-network
value of br
also validates that this was Brotli compressed content. The br
stands for Brotli.
If you check the headers for the reported compressed (again, they were all compressed) the headers are different but show all the same details (if in a different way):
accept-ranges bytes
age 348514
cache-control public, max-age=0, must-revalidate
content-encoding br
content-length 1741198
content-type application/javascript
date Fri, 19 Jun 2020 12:48:07 GMT
etag "1f6377ea62a71ea60cc6f10e0c64de6c-ssl-df"
server Netlify
status 200
strict-transport-security max-age=31536000
vary Accept-Encoding
x-nf-request-id 6d981e4f-93b1-408c-9043-c91fec97aca1-2309947
Again the etag
ends with -ssl-df
and the content-encoding
is br
which is Brotli. The transfer size in the logs was 1741641 bytes.
To summarize, yes, there is a bug but it isn’t at Netlify. It is in the browser or tool you are using. It might help to file a bug report with them about that.