title: Would it be wise to serve static content on a cookie-free domain in SSL?
body: <p>I have long read about "Use cookie-free domains" aka create a subdomain that can serve css, js, and images, all in 1 subdomain.</p>
  
  <p>However 99% of our site is served via ssl, and ssl certificates can be expensive.</p>
  
  <p>And so if we did this cookie-free subdomain, and to avoid that error that says "This page contains both secure and nonsecure items" error, we'd have to have ssl on the cookie-free subdomain.</p>
  
  <p>Have any of you done similar things?</p>
  
  <p>Would it really be worth the cost, to setup a 2nd ssl subdomain to host all the css, images, and javascript for all of our sites?</p>
  
  <p>Thank you.</p>