ssl with boost and securepages module I have this doubt. 
I have a website in drupal 7 currently live (Kickstart2) and use as cache management boost 
I have to buy a ssl certificate on my domain and with this certificate I would like to cover only the path checkout/* and user/* 

I would like to proceed in this steps: 


buy ssl certificate for the main domain
install the module securepages
configure the module with the path checkout / * and user / *


by this configuration I expect something like that:
http://www.example.com/mypage but https://www.example.com/checkout
only /checkout will be in https. Is it right?

This is just as reasoning and how to configure the module? Is it the right way?

Last question: 
I read that boost module does not work well with ssl, that it means that my checkout/* pages will not be under cache, but the rest of the pages? Rest of the path like /about or /news are all done under cache? 
You can confirm this to me?

Ty guys
Should I use securepages?


No. The best practice these days is to just go with https for the whole site.  


How do I go about caching my https content?


On a normal site, the https wouldn't matter, you can cache static content regardless of how encrypted it travels. BUT. The caching questions are legitimate because it is an eCommerce site and with that (by default), even anonymous users will have a session. Most default caching systems do not work with per-user sessions, unless you use something like authcache.