ProductCart Shopping Cart Software Forums : Leaving the https: https://forum.productcart.com/ Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved. Sun, 12 Apr 2026 10:37:15 +0000 Mon, 16 May 2011 08:39:42 +0000 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 12.04 360 https://forum.productcart.com/RSS_post_feed.asp?TID=4471 <![CDATA[ProductCart Shopping Cart Software Forums]]> https://forum.productcart.com/forum_images/pc_logo_50.png https://forum.productcart.com/ <![CDATA[Leaving the https: : Thanks, fellas, got some of this...]]> https://forum.productcart.com/leaving-the-https_topic4471_post17526.html#17526 Author: SharpDataInc
Subject: 4471
Posted: 16-May-2011 at 8:39am

Thanks, fellas, got some of this stuff cleared away.
 
SDI
]]> Mon, 16 May 2011 08:39:42 +0000 https://forum.productcart.com/leaving-the-https_topic4471_post17526.html#17526 <![CDATA[Leaving the https: : For the Authorize.net logo just...]]> https://forum.productcart.com/leaving-the-https_topic4471_post17485.html#17485 Author: cognecy
Subject: 4471
Posted: 11-May-2011 at 10:30am

For the Authorize.net logo just change the link to use https all the time. I checked and this worked just fine.  You can check suspicious elements/objects yourself by just plugging in the source link into your browser address bar with an https.   So your trust seal code will now look like this:
 
<a href="http://www.authorize.net/"><img
src="https://www.authorize.net/files/PreferredReseller.gif" width="140" height="50" border="0"
alt="Authorize.Net Preferred Reseller" />
</a>

NOTE the only part that I changed to https was for the "object" that is being added to your page from an external source.
 
 
As a rule of thumb:  You can build a non-secure page using secure objects ... you cannot build a secure page using non-secure objects.
 
 
I just checked the link for the google translate code and it does not appear the gmodules.com portion (the first URL) will allow you to use https.  The second portion that uses "google.com" will allow https so you could try this in your code:
 
<script src="http://www.gmodules.com/ig/ifr?url=https://www.google.com/ig/modules/translatemypage.xml&up_source_language=en&w=160&h=60&title=&border=&output=js"></script>
 
 
I have not ever used that code in a website but if it is giving you problems after using my modification, you may have to leave that out of your code where the store is concerned.  
 
 


Edited by cognecy - 11-May-2011 at 10:32am]]> Wed, 11 May 2011 10:30:45 +0000 https://forum.productcart.com/leaving-the-https_topic4471_post17485.html#17485 <![CDATA[Leaving the https: : Each of those very likely have...]]> https://forum.productcart.com/leaving-the-https_topic4471_post17483.html#17483 Author: Greg Dinger
Subject: 4471
Posted: 11-May-2011 at 10:17am

Each of those very likely have an SSL, and changing to HTTPS should be successful.  Just experiment a bit.
 
Keep in mind that once you overcome any objects that are causing the SSL warning, my original comments still apply.  If someone has gone to the "my account" login, or to checkout, and then browses back to the store - you still want to force them back to HTTP.
]]> Wed, 11 May 2011 10:17:17 +0000 https://forum.productcart.com/leaving-the-https_topic4471_post17483.html#17483 <![CDATA[Leaving the https: : What about using Google Translate?...]]> https://forum.productcart.com/leaving-the-https_topic4471_post17481.html#17481 Author: SharpDataInc
Subject: 4471
Posted: 11-May-2011 at 9:00am

What about using Google Translate? An even Authorize.net logo, you are governed by their code for the logo.

Authorize.net
<a href="http://www.authorize.net/"><img
src="http://www.authorize.net/files/PreferredReseller.gif" width="140" height="50" border="0"
alt="Authorize.Net Preferred Reseller" />
</a>

Google Translate
<script src="http://www.gmodules.com/ig/ifr?url=http://www.google.com/ig/modules/translatemypage.xml&up_source_language=en&w=160&h=60&title=&border=&output=js"></script>

I cant have these on the asp pages. I will check with them, I believe they need to support https:, I thought Google did...

Thanks
SDI]]> Wed, 11 May 2011 09:00:21 +0000 https://forum.productcart.com/leaving-the-https_topic4471_post17481.html#17481 <![CDATA[Leaving the https: : Ah, yeah its actually the js call...]]> https://forum.productcart.com/leaving-the-https_topic4471_post17480.html#17480 Author: SharpDataInc
Subject: 4471
Posted: 11-May-2011 at 8:20am

Ah, yeah its actually the js call that is causing the issue. The html is not the problem. Thanks!]]> Wed, 11 May 2011 08:20:06 +0000 https://forum.productcart.com/leaving-the-https_topic4471_post17480.html#17480 <![CDATA[Leaving the https: : Keep in mind that a hard-coded...]]> https://forum.productcart.com/leaving-the-https_topic4471_post17479.html#17479 Author: cognecy
Subject: 4471
Posted: 11-May-2011 at 8:06am

Keep in mind that a hard-coded "Link" as you have written it below will NOT cause a security warning.

These security warnings are caused by calling (or inserting into) the current page an object like an image, a .js file, an includes statement with a full path etc.
 
The reason is that while your page is trying to switch to https you are trying to build the page with elements that are not secure.
 
The way to avoid security warnings is to ensure that all objects are referenced using a relative path ... something like:  src="/somedirectory/someimage.jpg"
]]> Wed, 11 May 2011 08:06:21 +0000 https://forum.productcart.com/leaving-the-https_topic4471_post17479.html#17479 <![CDATA[Leaving the https: : How do you avoid the security...]]> https://forum.productcart.com/leaving-the-https_topic4471_post17478.html#17478 Author: SharpDataInc
Subject: 4471
Posted: 11-May-2011 at 7:23am

How do you avoid the security warning in the checkout? At the time of checkout, if there is a hard coded path in the header.asp:

href="http://www.website.com/html/myhtml"

you will get the security warning message box.

]]> Wed, 11 May 2011 07:23:40 +0000 https://forum.productcart.com/leaving-the-https_topic4471_post17478.html#17478 <![CDATA[Leaving the https: : we make a point of hard-coding...]]> https://forum.productcart.com/leaving-the-https_topic4471_post17477.html#17477 Author: Greg Dinger
Subject: 4471
Posted: 11-May-2011 at 12:56am

we make a point of hard-coding our stores, once they launch, so that all links point to fully-pathed HTTP or HTTPS URLs, dependant upon whis is appropriate.  That is the way we avoid the conflict you describe.]]> Wed, 11 May 2011 00:56:03 +0000 https://forum.productcart.com/leaving-the-https_topic4471_post17477.html#17477 <![CDATA[Leaving the https: : My header.asp file has the pathslike...]]> https://forum.productcart.com/leaving-the-https_topic4471_post17476.html#17476 Author: SharpDataInc
Subject: 4471
Posted: 11-May-2011 at 12:49am

My header.asp file has the paths like this

../../index.html
../../contactus.html
 
Problem is when the user starts a secure session (https:) and then decides to click on a link  (away from asp) it keeps the secured session active (https:) not http:.  So the html page get the security warning because its https: not http:.
 
Is this avoidable?
 
Thanks
SDI
]]> Wed, 11 May 2011 00:49:20 +0000 https://forum.productcart.com/leaving-the-https_topic4471_post17476.html#17476