Welcome to WebmasterWorld Guest from 18.206.48.142

Forum Moderators: open

Message Too Old, No Replies

HTTPS setup

     
3:44 am on Nov 27, 2006 (gmt 0)

Junior Member

10+ Year Member

joined:May 19, 2003
posts:71
votes: 0


I have searched and searched for an answer - probably a simple solution but please would someone point me in the right direction.

I cannot get my https pages to appear without a warning like "Parts of the page you are viewing were not encrypted before being transmitted over the Internet"

We have verified a certificate with Thawte? Tried to have all parts of the page have absolute https links for images, css etc.

I am sure there is a simple answer but from completing search after search, it appears that I am the only one who has come across this problem.

4:17 am on Nov 27, 2006 (gmt 0)

Administrator from JP 

WebmasterWorld Administrator bill is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Oct 12, 2000
posts:15159
votes: 170


Are all the images and CSS files located within the same directory as the pages?
10:18 am on Nov 27, 2006 (gmt 0)

Junior Member

10+ Year Member

joined:May 19, 2003
posts:71
votes: 0


No they are not - is this the problem?
10:34 am on Nov 27, 2006 (gmt 0)

Senior Member

WebmasterWorld Senior Member rocknbil is a WebmasterWorld Top Contributor of All Time 10+ Year Member

joined:Nov 28, 2004
posts:7999
votes: 0


Tried to have all parts of the page have absolute https links for images, css etc.

But you said they are. (?)

It's not so much absolute links. Make sure everything is coming from a secure location. For example, if your secure location is a virtual location, you can use this:

<img src="/images/myimage.jpg">

By virtual location I mean often yoursite.com and yoursecurehost.yoursite.com are often the same physical location. So if you use /images to link your images and call this page via [yoursecurehost.yoursite.com,...] the images will be linked from [securehost.yoursite.com...] on the secure server, [yoursite.com...] on the non-secure version. But it's the same physical place (sometimes.)

The same is true of external CSS, if you have an [yoursite.com...] for a background-image, changing it to /images will fix this.

The other thing to look for are external items called by scripts or objects. An example is Flash or adSense/google analytics - Google has secure location for their urchin.js, see documentation. It doesn't have to be **your** secure location, but it has to be a secure location with a cert. The codebase of Flash (if you use it) also has a secure location.

If all else fails, use the process of elimination - start deleting stuff on a test page until the warning goes away.

10:58 am on Nov 27, 2006 (gmt 0)

Junior Member

10+ Year Member

joined:May 19, 2003
posts:71
votes: 0


Thanks - have finally managed to sort it out - eventually it was a matter of trial and error - IE starting with nothing but a text only page. I think it was the css that was the main problem. Cheers
1:05 pm on Nov 27, 2006 (gmt 0)

Administrator from JP 

WebmasterWorld Administrator bill is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Oct 12, 2000
posts:15159
votes: 170


Why was the CSS a problem?
 

Join The Conversation

Moderators and Top Contributors

Hot Threads This Week

Featured Threads

Free SEO Tools

Hire Expert Members