SSL expertise needed

[Jenna]

Hi there,

 

I really need some help on a SSL-problem. What's the problem ?

We have a OSC system (SRV1) running but want to use the checkout part on the SSL-system on a different server. The SSL-server (SRV2) has the complete OSC installed and uses the database of SRV1.

 

Is this possible, because when I use the it now and leave SRV1 to checkout on SRV2 (SSL) the cart is empty on SRV2.

 

Any help is highly appreciated. I tried every option in the configuration file to get it working.

 

Thanks,

Jenna

 

p.s. my first time I deal with SSL-connections this way. Using it on the SRV2 is no problem at all (when the shopping cart is used completely on one system...)

[Guest]

I just setup my first oscommerce package, and I'm having the exact same problem. Let me know if you find a way to fix it... (Sorry I wasn't any help in answering your question)

[Guest]

Actually, I was able to get mine working....

 

I fixed it by changing the file: catalog/includes/configure.php

 

Around line 18 on that file you'll find:

 

define('HTTPS_COOKIE_DOMAIN', 'www.xyz.com');

 

Replace the www.xyz.com with the address of your secure site.

 

That fixed it for me anyway.

[Guest]

post your configure.php without the database connection info

[Jenna]

HI Mibble,

 

This is the configuration-file.

 

Thanks,

Jenna

 

/ Define the webserver and path parameters

// * DIR_FS_* = Filesystem directories (local/physical)

// * DIR_WS_* = Webserver directories (virtual/URL)

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

define('HTTPS_SERVER', 'http://www.server2.com/'); // eg, https://localhost - should not be empty for productive servers

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

define('HTTP_COOKIE_DOMAIN', 'http://www.server1.com');

define('HTTPS_COOKIE_DOMAIN', 'http://www.server2.com');

define('HTTP_COOKIE_PATH', '/effies/');

define('HTTPS_COOKIE_PATH', '');

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

define('DIR_WS_HTTPS_CATALOG', '');

define('DIR_WS_IMAGES', 'images/');

define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

define('DIR_WS_INCLUDES', 'includes/');

define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');

define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');

define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');

define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');

[♥Vger]

define('HTTP_COOKIE_DOMAIN', 'www.server1.com');

define('HTTPS_COOKIE_DOMAIN', 'www.server2.com');

define('HTTP_COOKIE_PATH', '/effies/');

define('HTTPS_COOKIE_PATH', 'effies');

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

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

 

If www.server2.com is in fact a shared ssl address then it can be more complicated than that.

 

Vger