3 ms·

The problem with this technique is that CDNs usually don't support HTTPS. It would require a dedicated IP address for the CDN and a separate certificate. The on

by keltex 17y ago

The problem with this technique is that CDNs usually don't support HTTPS. It would require a dedicated IP address for the CDN and a separate certificate. The only thing I've been able to come up with is to replace http://cdn.example.com http://cdn.example.com with https://www.example.com https://www.example.com on SSL pages.

benatkin 17y ago
DHH has a solution to this problem that I like: http://gist.github.com/29752 http://gist.github.com/29752 It's rails code, but the concept could be ported to other languages/frameworks.
- jhancock 17y ago
  WOW!!! Why is this ever hitting the ruby process? These are static assets. The decision should be made at the http proxy (apache, nginx) not your ruby proc.
  - mbrubeck 17y ago
    This controls which URLs are included in the dynamic content. It's not serving the actual assets.
    - jhancock 17y ago
      hmmm...my mistake. ;) thanks
sokoloff 17y ago
The two CDNs that I'm most familiar with (Akamai and Cotendo) do offer CDN/DSA services over SSL. I would imagine that the other big CDNs also offer SSL service. (Otherwise, how would they compete for e-commerce business?) We pay Akamai a non-trivial amount of money for SSL service, and they in fact host separate certificates for us (in addition to our origin servers hosting "our" own [different] certificates).