26 Jun 2019 
Support Center » Knowledgebase » Technical FAQs » Content not secure warning on Nanancast-hosted pages
 Content not secure warning on Nanancast-hosted pages

IE is giving a prompt stating that some of the page elements are "not secure" and if a client doesn't download the non secure elements, the page formatting and design looks bad. What can I do?

The real issue appears that you are putting https for a site that is not secure. You do not have an SSL installed on that site.

To use https you need to actually have a secure site with an SSL installed.

Here are some tips for being able to use https images with Nanacast for remote images and designs:

1. Add your Amazon s3 hosting account credentials to your Nanacast profile so that you can use Nanacast's built in Amazon s3 integration.

2. In the left menu go to Create > Custom Buttons/Images and then add a new image. You will see a check box option to define the image as an https image for use on secure checkout pages. Upload your image to Amazon s3 using those options in Nanacast.

3. Once you have uploaded your image and it appears in the display list on the Create > Custom Buttons/Images page right click on it and copy the url of the location of that image. If you have checked the https option when you uploaded it you will notice that it is now an https url hosted at Amazon s3 using their SSL.

You can now use those images because they are hosted on a secure server. So just modify all the image paths in your code to point to each image you upload through Nanacast checking the https option.

4. Finally just strip out all your CSS from your remote css file and place it right in the head of your secure checkout page code and call it locally. This way you won't have to find a way to host your CSS file on an SSL site if you do not have one to upload it to.

You can see an example where I have done exactly what I described by clicking on the order page link for http://optimizeyourvideo.com. View the source of that secure order page and you will see that I did exactly as I described above for that secure checkout page and it eliminates all insecure warnings etc because all the content is properly hosted on SSL protected pages. The images remotely and the css and html locally.

Additional Keywords: Secure Content

Article Details
Article ID: 210
Created On: 12 Feb 2011 03:06 PM

 This answer was helpful  This answer was not helpful

 Login [Lost Password] 
Remember Me:
 Article Options
Home | Register | Submit a Ticket | Knowledgebase | News

Help Desk Software By Kayako eSupport v3.60.04