When CSS contains an @supports block, e.g.
@supports (display: flex) { .myClass { display: flex }}
It works on the first request (cache miss), which means that the
application is working properly and the CSS is fully present. However,
once CloudFlare caches CSS, we consistently see that the cache hit
cuts like so:
@supports (display: flex) { .myClass { display: flex
If anything appeared later in the original CSS file, it is missing in
the cache response.
This is an even worse problem if the CSS is embedded inline (which I
think mod_cloudflare might do automatically for some files), because
CloudFlare cuts the entire HTTP response in the same way for inline
CSS.
I am not sure if this problem extends to other CSS @ blocks, like
@media, but you should ensure that it does not cause such a
devastating condition as it currently does. Web sites affected by this
issue either appear unstyled, or do not appear at all, when serving
from the Cloudflare cache.
Please resolve this and push it out to your customers ASAP.
(released August 9, 2016)
- Users Browsing the Wiki
- Fixed unclosed BB-Code options preventing parsing
- Fixed some wiki BB-Codes not working in non-wiki posts
- Fixed some counters not updating when wiki content is deleted
- About 55 other bugs were fixed
(released September 19, 2016)
- Improved performance of some functions
- Fixed wiki overlays not matching forum overlay style
- Fixed Manual Mode causing unexplainable problems during install/upgrade
- About 90 other improvements and bug fixes
(released November 8, 2016)
- Fixed non-inline attachments in wiki comments
- Fixed some race conditions
- Fixed ability to delete old edits
- At least 90 other fixes and improvements
Please uninstall and try again with the new version.Getting an error here.
This is fixed in 4.0.15 PL 1 as of today. Reinstall required if you got the error already.Getting an error here.
We use essential cookies to make this site work, and optional cookies to enhance your experience.