Guest Posted July 8, 2006 Posted July 8, 2006 this is a copy of a e-mail i sent to GEOtrust about my problem. Case Description: the front end of my website works great but when you try to go to check out you get a certificate error. name on certificate does not match the web url. I am not sure how to fix this. Does the certificate need to say "www.cplbutler.com" instead of "cplbutler.com" please let me know if you can help. there answer was: Your diagnosis is correct. The certificate is set for "cplbutler.com" but your secure HTTPS webpages have the WWW in front (e.g. https://www.cplbutler.com/checkout_shipping.php). The certificate cannot be changed -- it is bound to the domain name for security reasons. The solution that I suggest is to change all the links to secure pages. For example, when I click on "Checkout", send me to a link that does not have the WWW (https://cplbutler.com/checkout_shipping.php). Can i do that? if so where is the file and how? thanks Jim
ozcsys Posted July 8, 2006 Posted July 8, 2006 You need to edit your configure.php files and change the secure path (removing the www) The Knowledge Base is a wonderful thing. Do you have a problem? Have you checked out Common Problems? There are many very useful osC Contributions Are you having trouble with a installed contribution? Have you checked out the support thread found Here BACKUP BACKUP BACKUP!!! You did backup, right??
Guest Posted July 8, 2006 Posted July 8, 2006 You need to edit your configure.php files and change the secure path (removing the www) i ahve edited the configuration.php files (2) but it still doesn't work. i am assuming i have to change the path at the "checkout" button but don't know where to find it.
♥Vger Posted July 8, 2006 Posted July 8, 2006 All of the paths you need to edit are in the two configure.php files - so either you did not edit them correctly, or else you edited them and uploaded the changed files, but did not change the permissions on the online files to allow the uploaded ones to overwrite them. Did you edit the http and https cookie domain settings in includes/configure.php? From your original post they must read just 'cpbutler.com' and not 'www.cpbutler.com' nor should they have any http:// or https:// in them. The cookie domain setting is for a domain and not a url. Vger
Guest Posted July 8, 2006 Posted July 8, 2006 All of the paths you need to edit are in the two configure.php files - so either you did not edit them correctly, or else you edited them and uploaded the changed files, but did not change the permissions on the online files to allow the uploaded ones to overwrite them. Did you edit the http and https cookie domain settings in includes/configure.php? From your original post they must read just 'cpbutler.com' and not 'www.cpbutler.com' nor should they have any http:// or https:// in them. The cookie domain setting is for a domain and not a url. Vger Man i am sorry i still can't get it to work. this is what i have: define('HTTP_SERVER', 'http://www.cplbutler.com'); // eg, http://localhost - should not be empty for productive servers define('HTTPS_SERVER', 'https://www.cplbutler.com'); // eg, https://localhost - should not be empty for productive servers define('ENABLE_SSL', true); // secure webserver for checkout procedure? define('HTTP_COOKIE_DOMAIN', 'www.cplbutler.com'); define('HTTPS_COOKIE_DOMAIN', 'cplbutler.com');
ozcsys Posted July 8, 2006 Posted July 8, 2006 You need to remove the www from your https: define define('HTTPS_SERVER', 'https://www.cplbutler.com'); // eg, https://localhost - should not be empty for productive servers should be define('HTTPS_SERVER', 'https://cplbutler.com'); // eg, https://localhost - should not be empty for productive servers The Knowledge Base is a wonderful thing. Do you have a problem? Have you checked out Common Problems? There are many very useful osC Contributions Are you having trouble with a installed contribution? Have you checked out the support thread found Here BACKUP BACKUP BACKUP!!! You did backup, right??
♥Vger Posted July 8, 2006 Posted July 8, 2006 I'd also make HTTP_SERVER read 'http://cpbutler.com' and http_cookie_domain read 'cpbutler.com' - this saves customers getting confused when the address switches, and also allows you to use Force Cookie Use if you wish to. Vger
Recommended Posts
Archived
This topic is now archived and is closed to further replies.