Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Http to Https


Guest

Recommended Posts

Hello,

I have this problem, I renew my SSL certificate and unfortunately, on Chrome my site is not secure. 

When I inspect the page appear as mixed contents. A wee help, please?

Thanks

Link to comment
Share on other sites

@aquatib

Do you have access to the files on the server (via FTP or otherwise)? Please note that v2.3.3.1 is quite old (vintage 2013). As your host upgrades things, your shop will begin having problems (like, crashing!). I would strongly suggest you explore updating your shop.

If all of this is beyond your capability, you can post a RFQ (request for quote) in the commercial section of this forum to have a developer help you.

HTH

Link to comment
Share on other sites

15 minutes ago, ArtcoInc said:

@aquatib

Do you have access to the files on the server (via FTP or otherwise)? Please note that v2.3.3.1 is quite old (vintage 2013). As your host upgrades things, your shop will begin having problems (like, crashing!). I would strongly suggest you explore updating your shop.

If all of this is beyond your capability, you can post a RFQ (request for quote) in the commercial section of this forum to have a developer help you.

HTH

I think I will do what you told me, as you could see this stuffs are new to me. Thank you and could you direct Me?

Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...

Different browsers have different ways of dealing with "mixed content" (one or more non-SSL http: resource URLs) on an https: (SSL) page. Some will say nothing; some will ignore (suppress) non-SSL content, and some will give an error message. Some browsers permit non-SSL for some things (at a minimum, links to other pages), and some may be very strict about any URL that's not SSL. It's not uncommon to initially have some non-SSL content when you switch over to an SSL site, and you have to do some detective work and cleanup. This is most likely a problem with your configuration or some add-on content (ad banners, etc.) forcing non-SSL output. Bring up a page that reports mixed content, look at its HTML page source in the browser (often Ctrl+U), and search for http:. When you find something, if it's an image, Javascript file, CSS file, and maybe other resource types, you'll need to figure out where it came from and how to fix it. Links to other pages (<a href=...> links) shouldn't cause any problems. Also keep an eye out for form ACTIONs with an http: URL -- that may need to be changed. If you're lucky, it's a hard coded http: in a file somewhere. It's possible too that such an old version of osC is putting out a non-SSL URL because some tep_href_link() etc. calls are hard coded to NONSSL, but that's unlikely if your configure.php files are properly set to use https: everywhere and not a mixture of http: and https:. There might even be some place where a full http: URL is hard coded into the code, rather than using tep_href_link() -- this is not uncommon in poorly coded add-ons.

Even if you can find the offending entries and fix them easily, you should still be thinking about upgrading to 2.3.4.1BS Edge. It is the latest and greatest. Note that this is not the official release (apparently osC is no longer being developed), but is community-supported and is on GitHub (see my signature link below). Further note that this is a fresh (new) install, and migrate over your database and product images, and re-install any add-ons and rework any customizations. It's not trivial, but it will leave you completely up to date.

Link to comment
Share on other sites

I think using HTTPS is a must these days, as Google has recently said that all those sites have not integrated SSL on their website, would definitely be dropping their rankings. So get an SSL security certificate for your website and do not take a risk with Google. 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...