WordPress HTTPS conflict with W3 Total Cache
I’m having some trouble making WordPress HTTPS and W3 Total Cache play nice in regards to my cloudfront CDN.
WordPress HTTPS 3.3.0 would add a :443 after your domain if you filled in 443 for the port number. This would make W3 Total Cache not replace domains with my cloudfront domain on SSL pages.
The newest version of WordPress HTTPS does not add the :443 and thus W3TC keeps replacing my domains in HTTPS pages with the HTTP cloudfront domain.
Note that W3TC is set to auto detect protocol (which does not seem to work with WordPress HTTPS) and is also set to not even use the CDN on pages with SSL (also does not seem to work with WordPress HTTPS).
If anyone has any experience with making WordPress HTTPS, W3 Total Cache, and Amazon CloudFront all work together, I’d really appreciate it!
- The topic ‘WordPress HTTPS conflict with W3 Total Cache’ is closed to new replies.