title: Control caching and CDN on Cloudflare when SSL is forced "on" via a page rule
body: <p>This question is specifically about page rules in Cloudflare, which allow you to specify wildcard patterns on your site using rules - and handle each pattern differently.</p>
  
  <p>One of the patterns is "Force SSL" - in effect, any request that matches that pattern will be forced down the path of https:// - whether that's Flexible SSL or otherwise.</p>
  
  <p>The problem with choosing this option is that <em>all other options over the CDN/cache time, etc. disappear</em>.</p>
  
  <p>This raises some obvious issues to which I've found no clear answer:</p>
  
  <ul>
  <li>If Cloudflare serves a https:// resource, does it still cache static resources?</li>
  <li>How do I control the nature of the resources cached? In other words, the settings equivalent to "Simple" caching, and "Aggressive" caching.</li>
  <li>Is there any ability to set options such as cache expiry, time that they reside on edge servers before expiration, etc?</li>
  <li>Is it possible to set "Cache Everything" when serving requests over https://? It certainly exists on the http:// equivalent.</li>
  </ul>
  
  <p>I would like Cloudflare to re-direct my visitors from http:// to https:// automatically as opposed to do it on my app, because the various apps on my domain (Wordpress included) have various quirks that make configuring each one both tedious and error-prone. </p>