Considering the woes that can come with installing a SSL certificate. Yesterday, we ran into an issue with a client that I wanted to note, just in case anyone else may benefit from the scenario and solution.
Scenario
We had the Magento integrated with SVN and have a post-commit hook that auto-deploys into our root directory on the server, using great server services from sites as ServerMania Montreal Data Center online. We originally had the httpdocs folder and the httpsdocs folder mirroring each other so that the httpsdocs folder would handle SSL (https) requests and the httpdocs would handle all other non-SSL requests.
As we were installing our SSL certificate, we changed the base_url and the secure_base_url to the appropriate (specific) URLs in place of the {{unsecure_url}} and {{secure_url}} generic values. All of a sudden, as soon as SSL installation was complete, the frontend would no longer transition from the “shopping cart” (url: http://cart.crankbrothers.com/checkout/cart/) into the “checkout” (url: https://cart.crankbrothers.com/checkout/onepage/). The checkout URL would redirect back into the shopping cart.
Solution
We realized that the sub-domain and shared docroot setup (httpdocs and httpsdocs, together) could be creating the issue. Thus, we simplified our setup (cheers Eric Dennis) to make httpdocts the separate docroot for both HTTP and HTTPS requests.
Game, set, match. Problem solved. By the way, you should check out Crank Brothers for a working example 🙂
Hope this helps save time for someone else!
Elizabeth says
Can you elaborate more on how you fixed this? I think I am having the same issue. I checked out crankbrothers.com and it is a NICE looking site. My email is easmemphis@aol.com…thanks
Eddie says
did you create a symbolic link between the two docroots after you created the 2nd one? http://www.magentocommerce.com/boards/viewthread/70421/#t248958
Mike says
I had a similar incident where the www. subdomain was interfering with the certificate, which was set up for the .com address without the www. I fixed it by changing the secure and unsecure URLs to not have the www. prefix. The difference between my problem and theirs was that mine was a certificate problem, since it did not allow for subdomains (even the www. prefix)