Reputation: 41
We recently started using Azure CDN however some users reported an issue and we got a screenshot from one of them:
We were not able to get any more information on the issue. Any idea what could cause this and how to fix it?
Our origin server returns correctly the file with the following response headers:
Accept-Ranges: bytes
Access-Control-Allow-Origin: https://www.google.com
Cache-Control: max-age=31536000
Content-Encoding: gzip
Content-Length: 1956119
Content-Type: text/css
Date: Tue, 16 Feb 2021 18:44:10 GMT
ETag: "011889dd7ffd61:0"
Expect-CT: max-age=604800, enforce,
Feature-Policy: autoplay 'none'; camera 'none'
Last-Modified: Wed, 10 Feb 2021 18:07:38 GMT
strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Vary: Accept-Encoding
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Upvotes: 1
Views: 1920
Reputation: 5323
I have this issue when my web server sends compressed responses. If I disable response compression in my web server and enable it only on the Azure Front Door side, then the error goes away, and everything works.
Older Azure Verizon CDN didn't have this issue.
It's a bit sad. I would have preferred to compress the files on my web server and then have CDN be a blind tool for distributing compressed files.
Upvotes: 0
Reputation: 6951
I got a similar problem. I was able to fix this by enabling cache i Dev Tools. Enable cahce in Dev Tools
Upvotes: 0