- This topic has 5 replies, 1 voice, and was last updated 7 years ago by
.
-
Posts
-
Hey Everyone.
I noticed a new Https discussions around on here, I am wondering how everyone is getting around trailers and mixed content… I have a few of my sites on Https, but they host all content on the same server, i’ve noticed a lot of affiliate programs and thier respective CDN’s have not yet moved over to secure URLs for trailers yet, so is there a workaround other than having to host all trailers on your own servers, which to me seems a little over the top for smaller sites who usually hotlink videos (where allowed).
I have one blog which is small and i currently embed the videos, but this will obviously cause mixed content warnings, red warning pages and possibly even the content being blocked on some browsers… any thoughts??
I don’t think there’s any way around this at all, unfortunately. If any content on a https page is being delivered from a http there’s nothing you can do about the warnings.
I would suggest creating a list of the most important content and then host that yourself securely to maximise its exposure. It might be a pain to do it but if you’re losing out on sales or valuable views because of it it’s probably worth it in the end.That is just one more reason why I insist on hosting all my own content. Those sponsor URLs that are causing broken locks also have a habit of going dead after a while. And they will slow down your page load times. There is a lot of reasons to not use sponsor hosted resources. That is just part of a long list.
Thanks guys, you echo my thoughts, but needed a little reassurance I had read everything right. I do host myself for the bigger personal adult projects I have going on, I suppose I will just host for the smaller also.
Yes MRA, I had noticed things like links tend to die over a period of time, and obviously page load is effected due to an external resource, thinking it all just makes sense really!
I’m in the process of moving over adult sites I manage to HTTPS. We just finished one of the sites, a tube site. In this case we sorted out wildcard certs for the video CDN and other apps we use and then use Cloudflares own certs / SSL for everything else (html and images).
I bought the certs from ssls.com.
If we had used content hosted by sponsors it just wouldnt have been possible. Now days there just isnt any reason not to host everything yourself. And no, there is no way of getting around it. All resources on your page has to be loaded from a secure URL, you can’t cheat it.
To overcome from this issue, you must upload all media files (images, videos, .js, etc.) on your own server instead of embedding from insecure remote location. The next step is to look for mixed content warning on your whole platform (use this great tool: whynopadlock.com/) You should also refer to this (cheapsslshop.com/blog/what-is-mixed-content-warnings) tutorial which can help you understand profoundly. Use of relative URLs can always be helpful to avoid unwanted mixed content warnings.
