Automattic
[Boost] Critical CSS generation failure CF
I noticed in a tastewp site that critical CSS generation does not work. They use Cloud Flare and that may have something to do with it. The post request to set-provider-css is giving a 302 response, which I think might be related to what's going on.
After some investigating, any endpoint ending with css has a 302 redirect. Even if you do a GET request.
It appears to be either a server configuration or cloudflare that's causing this.
I've reached out to support for more information on this, as it appears it isn't something we can address on our end.
For our end, we could present this error in a way that makes sense. It's still a show stopper, however, the expanded message makes little sense to the user.
tastewp responded and they have fixed the issue.
We have internal caching in place to decrease out traffic bandwidth and speed up sites out of the box, so users won’t need any plugin to optimize their sites. CSS is one of 30 extensions that we cache automatically but regex was configured to match any URL that ends with „css" not with „.css”.
We adjusted it and now the REST API from your example works properly, we updated it for all sites at TasteWP.
Tested and confirm that it works. Closing this.