I'm wondering whether anyone else has come across this issue.
We have a site which has both HTTP and HTTPS pages, on our single server setup W3TC has done a great job of rewriting urls to static assets on our CDN based on the request protocol (http/https). We have outgrown our single server environment and we are moving to a much bigger data-center with load balanced servers, to reduce overhead on internal network traffic, we are terminating SSL at the load balancer, and requests between the load balancer and apache are over plain HTTP. This has in turn caused mixed asset issues because W3TC doesn't know to rewrite CDN urls over HTTPS.
Is there a way to make W3TC use the fairly common
X-Forwarded-Proto header (passed on by the load balancer) to determine whether to rewrite asset urls as HTTPS? Or is there another standard W3TC way to handle this issue where SSL is terminated at the load balancer?
Appreciate any insight into this.