Actually, for what you intend, the solution proposed by @sandro covering
/wp-* should work just fine. You don’t actually need to have a “Cache Level: Bypass” setting on that rule. To be effective, this page rule must be placed before the “Cache Level: Cache Everything” page rule, which won’t ever trigger for the areas covered by
So you could have:
Security Level: High
Rocket Loader: OFF
Cache Level: Cache Everything
The first rule will trigger for anything under
/wp-*, which of course includes
/wp-content/*, but since it isn’t setting a cache level for the path, the default caching policy will apply: static files such as image, JS and CSS files will be cached, HTML won’t.
And because of the way Rocket Loader works, the first page rule won’t prevent it from working on the JS files invoked by the HTML covered by the Cache Everything page rule, even though these files will probably be under
Make sure you hit Purge Everything and wait a bit after you set the rules as proposed, to purge any already cached assets that shouldn’t have been cached.