vengavenga Posted September 28, 2004 Posted September 28, 2004 Hi all, I'm struggling with an osC site that uses SSL and wonder if anyone on here has any idea as to what the problem/solution might be? The SSL is one that I purchased and got TCH to setup within my reseller account. It's effectively shared SSL, but only for my clients to use. The osCommerce store appears to work normally until the customer tries to login to their account. On clicking the login link the url changes from http:// to https:// as it should do and the login screen appears as normal. The user enters username & pass, clicks on the Login button and gets taken to a non-existant page. ~username/catalog//catalog/account.php Now, that's obviously the path that's wrong, there should only be 1 /catalog, not 2. If the user doesn't login to their account and instead sets up a new one (which automatically logs them in when done) then everything works OK - it's insecure until they come to the payment page - it then goes secure and is fine ... until ..... When the "thanks for your order" message appears, clicking the Continue button (which should take them out of the ssl part of the site and back to the home page) the store tries to send them to /~username/catalog//catalog/index.php Same problem again with the double catalog. Ah ha - I hear you cry! His configure.php file is incorrect ... yep, but I can't see why! >/ Define the webserver and path parameters // * DIR_FS_* = Filesystem directories (local/physical) // * DIR_WS_* = Webserver directories (virtual/URL) define('HTTP_SERVER', 'http://www.clients-site.com'); // eg, http://localhost - should not be empty for productive servers define('HTTPS_SERVER', 'https://www.my-domain-for-ssl.com/~username/catalog/'); // eg, https://localhost - should not be empty for productive servers define('ENABLE_SSL', 'true'); // secure webserver for checkout procedure? define('HTTP_COOKIE_DOMAIN', 'www.clients-site.com'); define('HTTPS_COOKIE_DOMAIN', ''); define('HTTP_COOKIE_PATH', '/catalog'); define('HTTPS_COOKIE_PATH', ''); define('DIR_WS_HTTP_CATALOG', '/catalog/'); define('DIR_WS_HTTPS_CATALOG', ''); Above is the relevant part of configure.php I'm sure it's something dead easy, but my brain is frazzled now! Anyone any ideas? Thanks muchly Ali. Quote
TCH-Rob Posted September 28, 2004 Posted September 28, 2004 Here is mine; // Define the webserver and path parameters// * DIR_FS_* = Filesystem directories (local/physical) // * DIR_WS_* = Webserver directories (virtual/URL) define('HTTP_SERVER', '*****'); // eg, http://localhost - should not be empty for productive servers define('HTTPS_SERVER', 'https://www.****'); // eg, https://localhost - should not be empty for productive servers define('ENABLE_SSL', true); // secure webserver for checkout procedure? define('HTTP_COOKIE_DOMAIN', 'www.****'); define('HTTPS_COOKIE_DOMAIN', 'www.****'); define('HTTP_COOKIE_PATH', '/shop/'); define('HTTPS_COOKIE_PATH', '/shop/'); define('DIR_WS_HTTP_CATALOG', '/shop/'); define('DIR_WS_HTTPS_CATALOG', '/shop/'); See the difference? Try that and see if it works. Quote
TCH-Andy Posted September 28, 2004 Posted September 28, 2004 Or possibly change define('HTTPS_SERVER', 'https://www.my-domain-for-ssl.com/~username/catalog/'); // eg, https://localhost - should not be empty for productive servers to define('HTTPS_SERVER', 'https://www.my-domain-for-ssl.com/~username'); // eg, https://localhost - should not be empty for productive servers Quote
vengavenga Posted September 29, 2004 Author Posted September 29, 2004 Thanks Andy & Rob - your suggestions didn't work "straight out of the box", but by combining the two and messing around a bit more they helped solve the problem completely Don't know why I couldn't see it myself! Just in case anyone else has the same problem and comes across this thread in a search .... > define('HTTP_SERVER', 'http://www.clients-site.com'); // eg, http://localhost - should not be empty for productive servers define('HTTPS_SERVER', 'https://www.my-domain-for-ssl.com/~clients-username'); // eg, https://localhost - should not be empty for productive servers define('ENABLE_SSL', 'true'); // secure webserver for checkout procedure? define('HTTP_COOKIE_DOMAIN', 'www.clients-site.com'); define('HTTPS_COOKIE_DOMAIN', 'https://www.my-domain-for-ssl.com/~clients-username'); define('HTTP_COOKIE_PATH', '/catalog/'); define('HTTPS_COOKIE_PATH', '/catalog/'); define('DIR_WS_HTTP_CATALOG', '/catalog/'); define('DIR_WS_HTTPS_CATALOG', '/catalog/'); What made it a bit more complicated is the fact that the store is a domain within my reseller account rather than my main account. Thanks again Ali. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.