I am getting the security alert: “You are about to be directed to a connection that is not secure. the information you are sending to the current site might be transmitted to a non-secure site. Do you wish to continue?” when I try to login as a customer on my clients oscommerce website. I noticed the link in the status bar goes from a https prefix to a nonsecure http prefix. The site has a SSL certificate, so how do I ensure the entire store portion of the site directs to the secured site?
Question posted in Oscommerce
The official documentation can be found here
The official documentation can be found here
5
Answers
It is likely that some parts of the page, most often images or scripts, are loaded non-secure. You’ll need to go through them in the browser’s “view page source” view one by one and eliminate the reason (most often, a configuration setting pointing to
http://
).Some external tools like Google Analytics that you may be embedding on your site can be included through
https://
, some don’t. In that case, you may have to remove those tools from your secure site.If you can’t switch all the settings, try using relative paths
but the first thing is to identify the non-secure elements using the source code view of your browser.
An immediate redirection from a
https://
page to ahttp:/
one would not result in a warning as you describe. Can you specify what’s up with that?Ensure that the following are included over https:
If you’re confident none of your own stuff is included over http, check things like tracking pixels and other third-party gadgets.
Edit: Now that you’ve linked your page, I see that your
<base>
tag is the problem:Change to:
Use Fiddler and browse your site, in the listing it should become evident what is using HTTP and HTTPS.
It sounds to me like the HTML form you are submitting is hardcoded to post to a non-secure page.
If the suggestion from Pekka doesn’t suit your needs you can try using relative links based on the schema (http or https):
e.g.,
The only problem with this technique is that it doesn’t work with CSS files in all browsers; though it does work within Javascript and inline CSS. (I could be wrong here; anyone want to check?).
e.g., the following :
…might fail.
A simple Find/Replace on your source code could be easy.