Closed mroskamp closed 8 months ago
@mgol I'm not sure. I purged it just now to test with curl and the newly populated entry is working correctly with gzip on and off depending on browser headers (e.g. curl
gets raw, and curl --compressed
, like browsers, gets gzip).
To increase chances of me making the first request after a purge, I used an old qunit release instead, and requested it via codeorigin.jquery.com
. And I tested it both with curl
making the first request with --compressed, and making the request without it. Either way results in a correctly working cache entry that is served correctly both ways.
OK, maybe let’s just hope it was a one-off? And only investigate further if we get another report?
@mroskamp can you confirm it works correctly now?
@mgol, confirmed. 3.6.1 is correctly compressed now. Thank you!
This is happening again and for some assets that were working fine for me originally (e.g. minified 3.7.1
): #103.
It appears that the minified release of jQuery Core 3.6.1 (https://code.jquery.com/jquery-3.6.1.min.js) does not use the standard gzip compression. The minified release of other jQuery versions (3.6.0-3.6.3) are compressed with gzip. Similarly, the slim and slim minified releases of jQuery 3.6.1 are also compressed with gzip.