Likely a “web application firewall” that thinks it sees “path traversal attacks”, can you try changing any instance URL’s with ../ with the “resolved” URL, e.g. wp-content/themes/flashy/css/../images/ becoming wp-content/themes/flashy/images/?
frank
I generated the above the fold CSS using sitelocity. BTW, I have BBQ Firewall in which there is no such setting that could see this as a “path traversal attack”. I just got the AO update. Will try the ATF setting again and will report back.
-
This reply was modified 2 years, 7 months ago by
ThePhysicist.
it’s pretty unlikely the AO update will make a difference 🙂
if it indeed still does not work try if adding something like whatever{this:works;} does. if so it confirms that *something* in the sitelocity CSS (maybe the path traversals) is not allowed by *something else* (possibly BBQ firewall, but could be something else).
Hey there.
I have noticed something after pasting the CCSS code into the ATF box in AO. Although the code doesn’t stay put after save and empty cache, AO does attempt to implement ATF optimization. However, this breaks my site for a split second. Hence, I disabled ATF opti altogether. Probably the fault lies in the CCSS as well.
Anyhow, since ATF isn’t a big impact on my site after I migrated to a much better host, I will leave it as is and focus on the business since I am the only one building it and running it.
Thanks for your cooperation anyway.
Did you test if the ATF-CSS saved with whatever{this:works;} as input 7hephysicist ?
No. It has been my recent understanding that using the CCSS generated by a third-party site is not gonna fully work.
Generally this can work, but in some specific cases manual tweaking of the generated critical CSS is needed.
But to be able to advance, first step would be testing if you can save a (utterly wrong) critical CSS string successfully?
