Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Problems with ssl


Guest

Recommended Posts

Posted

Have you made the appropriate changes to configure.php?

 

BTW it's hard to look when I suspect that you don't really have www.domain.com

Posted

hello tbgo,

I have made appropriate changes to configure.php.

eg,

define('HTTP_SERVER', 'http://www.digispan.net'); // eg, http://localhost - should not be empty for productive servers

define('HTTPS_SERVER', 'https://secure.digispan.net'); // eg, https://localhost - should not be empty for productive servers

define('ENABLE_SSL', true); // secure webserver for checkout procedure?

define('HTTP_COOKIE_DOMAIN', 'www.digispan.net');

define('HTTPS_COOKIE_DOMAIN', 'secure.digispan.net');

define('DIR_WS_HTTP_CATALOG', '/store/');

define('DIR_WS_HTTPS_CATALOG', '/store/');

Posted

If your http and https files are in different directories, make sure that you copy all the secure files to the https directory. Also the contents of the includes directory tree.

 

Hth,

Matt

Posted

ok I found the error... it was in define('DIR_WS_HTTPS_CATALOG', '/store/'); ... changed that to '/' and now it works.

Problem now is that login.php, create_account.php, etc need /includes/application_top.php. Do I have to copy all the files in my /store/ to my /secure/ folder?

Posted

ok thanks mat.. just confirmed I need to copy /store/includes. I will give that a go and hopefully it works.

thanks

Posted

It is getting there... I now have to copy the /catalog/images/ to /secure/images/ ... I was wondering what the alternatives are?

It seems now, I will have to update both the /catalog/images /catalog/ and /secure/images /secure/ when I make changes to the site and add products.

Posted
Do you have to use secure.domain.com?
It doesn't matter. If the host configured things to send http and https to different places, it will send them to different places regardless (even with http://yourdomain.com and https://yourdomain.com). Conversely, the host can also send http://yourdomain.com and https://secure.host.com/~userid to the same place -- if they choose to do so.

 

In short, it's a host configuration problem, not a user (site owner) configuration problem.

 

The two fixes are to change the DocumentRoot to be the same for both in httpd.conf or to make the secure directory a symlink to the regular directory (requires Options FollowSymLinks to be on for Apache).

 

Hth,

Matt

Archived

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

×
×
  • Create New...