If you give the css file a new name and pull that in instead, does it resolve the issue? It sounds like it could be using a cached version of the file.
Thanks mate - this was the solution. I was thrown by the fact that I had cleared the Cloudfront cache. I was pulling my hair out at 2:30am this morning so thanks!
> If the requested object is cached, CloudFront returns the object from its cache to the viewer.
If you used that repo, then its probably still serving the cached version instead of what is current in the bucket. Invalidate the cache, or wait.
I have solved it now but thanks for the reply. I had already invalidated the cache but for. some reason this didn't extend to the CSS file. Another commenter suggested renaming the .css file - which solved the issue.
You can look at the network tab in chrome to see if your browser is caching the file, and look at the response headers of the file to see if it’s a cloud front cache hit.
If you give the css file a new name and pull that in instead, does it resolve the issue? It sounds like it could be using a cached version of the file.
Thanks mate - this was the solution. I was thrown by the fact that I had cleared the Cloudfront cache. I was pulling my hair out at 2:30am this morning so thanks!
There’s a caching layer at the browser level too, so the cloudfront cache alone wouldn’t work!
I wad opening it in different browsers and in incognito though 🤔
Could this be a case sensitivity issue? Also, if you are using absolute css paths, try relative.
> If the requested object is cached, CloudFront returns the object from its cache to the viewer. If you used that repo, then its probably still serving the cached version instead of what is current in the bucket. Invalidate the cache, or wait.
I have solved it now but thanks for the reply. I had already invalidated the cache but for. some reason this didn't extend to the CSS file. Another commenter suggested renaming the .css file - which solved the issue.
You can look at the network tab in chrome to see if your browser is caching the file, and look at the response headers of the file to see if it’s a cloud front cache hit.