Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Trouble with SSL


jentel

Recommended Posts

This must be something simple and stupid but:

 

I have the SSL installed and working. Confirmed by entering https://mackinacmedia.com/catalog/index.php and have a secure page. ISP has also verified that SSL is installed properly.

 

osCommerce is configured as follows:

  define('HTTP_SERVER', 'http://www.mackinacmedia.com'); // eg, http://localhost - should not be empty for productive servers
 define('HTTPS_SERVER', 'https://mackinacmedia.com'); // eg, https://localhost - should not be empty for productive servers
 define('ENABLE_SSL', true); // secure webserver for checkout procedure?
 define('HTTP_COOKIE_DOMAIN', 'wwww.mackinacmedia.com');
 define('HTTPS_COOKIE_DOMAIN', 'mackinacmedia.com');
 define('HTTP_COOKIE_PATH', '/catalog/');
 define('HTTPS_COOKIE_PATH', '/catalog/');
 define('DIR_WS_HTTP_CATALOG', '/catalog/');
 define('DIR_WS_HTTPS_CATALOG', '/catalog/');

 

Documentation from SSL provider shows that SSL was issued as "mackinacmedia.com".

 

Yet when I test the shopping cart it does not change to https to enter the credit card. What am I missing here?

Link to comment
Share on other sites

Double check in catalog/includes/local for an extra configure.php file.

 

If you find one rename it.

Local: Mac OS X 10.5.8 - Apache 2.2/php 5.3.0/MySQL 5.4.10 • Web Servers: Linux

Tools: BBEdit, Coda, Versions (Subversion), Sequel Pro (db management)

Link to comment
Share on other sites

Double check in catalog/includes/local for an extra configure.php file.

 

If you find one rename it.

Sorry but this did not solve the problem. It caused osc to stop running and report a database error. I checked the php in that configure file and found not reference to https or ssl.

 

I have also searched all other PHP files to make sure any other HTTPS reference was not missed.

Link to comment
Share on other sites

Well, you've got an extra 'w' here, but that's not the cause of the problem:

define('HTTP_COOKIE_DOMAIN', 'wwww.mackinacmedia.com');

 

Other than that the includes/configure.php file you posted yesterday appears to be correct. As per the advice from Alan you don't use the configure.php file in the 'local' folder - this is for development work only.

 

It's more likely that your hosting company has an atypical way of setting ssl configuration. Do a search on this forum for 1and1 and the solutions offered for getting the ssl lock for people who host with them, and this may solve your problem too.

 

Vger

Link to comment
Share on other sites

Sorry but this did not solve the problem. It caused osc to stop running and report a database error. I checked the php in that configure file and found not reference to https or ssl.

 

I have also searched all other PHP files to make sure any other HTTPS reference was not missed.

 

You missed the point.

 

Rename that file and make sure the data in catalog/includes/configure.php is correct.

 

The ssl is working correctly because you do get a solid padlock.

 

The problem is almost certainly in the configure.php file.

Local: Mac OS X 10.5.8 - Apache 2.2/php 5.3.0/MySQL 5.4.10 • Web Servers: Linux

Tools: BBEdit, Coda, Versions (Subversion), Sequel Pro (db management)

Link to comment
Share on other sites

Maybe I am to close to the forest but, I see the catalog/localconfigure.php, I rename it and I get the error I desribed above.

 

We have confirmed that the catalog/includes/configure.php is set right (yes we took out the extra 'w').

 

Please be spcific, what point am I not getting here?

Link to comment
Share on other sites

Maybe I am to close to the forest but, I see the catalog/localconfigure.php, I rename it and I get the error I desribed above.

 

We have confirmed that the catalog/includes/configure.php is set right (yes we took out the extra 'w').

 

Please be spcific, what point am I not getting here?

 

If renaming the includes/local/configure.php file causes an error it means the includes/configure.php file is wrong. It probably has the wrong database info.

 

The idea is to focus on one file and correct that one, not deal with conflicts and confusion.

Local: Mac OS X 10.5.8 - Apache 2.2/php 5.3.0/MySQL 5.4.10 • Web Servers: Linux

Tools: BBEdit, Coda, Versions (Subversion), Sequel Pro (db management)

Link to comment
Share on other sites

OK I have the answer why.

 

When the site was first setup there was not a SSL available so we set everything to no or false during setup (by the way I was not involved at that point).

 

We setup the site and installed the SSL after. We followed the instructions and ended up with our problem.

 

In the file catalog/includes/local/configure is the setting

define('ENABLE_SSL', 0);

I did not see this before as everywhere else anything for the SSL was marked HTTPS and that is what I had been searching for.

 

Although the documentation does not show this file or how to set it I changed it to

define('ENABLE_SSL', 1);

and it started working.

Link to comment
Share on other sites

It's real simple...

 

Lines 25 & 26 in application_top.php

 

// Set the local configuration parameters - mainly for developers
 if (file_exists('includes/local/configure.php')) include('includes/local/configure.php');

 

The second file is redundant. You can leave it there if you wish but it loads after the primary one so any settings in it override the first. Just remember that any changes you make to catalog/includes/configure.php are not recognized.

Local: Mac OS X 10.5.8 - Apache 2.2/php 5.3.0/MySQL 5.4.10 • Web Servers: Linux

Tools: BBEdit, Coda, Versions (Subversion), Sequel Pro (db management)

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...