More SSL Issues After Server Upgrade

[sparrowce]

I'm having similar troubles as discussed in this link, http://www.zen-cart.com/forum/showth...sl+certificate, and have done the testing, been on the phone and online support w/host, so far the only answer is to change all the links to https on the buy buttons for products that are on ezpages (am using hidden categories module and all listings are through ezpages . . . some ezpages are html pages, some are the zencart category/product listing, depending on products and how they need to be displayed).

Had other recent issues (http://www.zen-cart.com/forum/showthread.php?t=183552), which was able to be resolved, but there is still something I've got wrong somewhere. I've also done the http and https versions of the ssltest.php recommended in 1st post. My question is, when I'm changing all links to https, if there is an image that is being referenced, for example, src="store/images/myimage_01.png, would I need to go back and put the full https://www...... path in front of store/?

It also seems to depend on what browser it's in. Example, Safari in a mac is giving me the error, but Firefox is not. On a PC, IE is not, and SeaMonkey is. Thank you for any help.

[DrByte]

Um ... "Buy Now" buttons on EZPAGES?

EZ-Pages are for *content*, not for products/purchases.

[sparrowce]

Possibly I have not set this up right, am using a combination of html pages for some of the products, depending on the product and display needs, and using the EZ pages to link to them. Am using the Hidden Categories to hide the categories from the store and displaying ez pages links in sidebar to simulate the categories. That part of things was working well, gave alot of flexibility where needed, and the products/cart/ssl was working great until the server move. They keep telling me it's a zencart issue and they also tell me the ssl certificate is pointing to the right IP, but I'm not clear on any of this, anyway, I will keep checking things that could be a problem, thanks.

[DrByte]

Does login and regular checkout (normal products from product listing/categories) work fine, with the whole checkout process running in SSL?

If so, then perhaps you've hardcoded some paths in your ezpages content and will need to change that.
But, adding complete URLs where they are NOT already present is a step backwards, and the wrong direction to take, especially since that's likely to cause *more* problems at a future date if you move "again".

[sparrowce]

No. Mostly this is surfacing in Mac's Safari and PC SeaMonkey, though I haven't tried alot of other browsers except IE8 on PC and an older Mac Firefox. Though SeaMonkey (I use it for the SeaMonkey composer feature) is probably not a popular one, Safari is, and there is no telling what set up the customers will have and sure don't know why such a difference in browsers. I can recreate it all the time in Safari by clearing cache (if I've accepted the error once I need to clear cache, close/reopen, as I'm trying to experience what a first time customer would)

In Safari, for example, if I'm in regular products/listings it says http at the top and I can add listings to the cart with no trouble, but as soon as I click 'go to checkout', the url changes to https and the warning pops up.

Thank you for your help.

[sparrowce]

Update, I found some links that say they diagnose SSL, such as www.digicert.com/help and www.sslshopper.com/ssl-checker.html, both seems to give ok checkmarks to everything, correct name matching, etc., so it must be something I have done in setting up the store somewhere.

[DrByte]

Without an actual URL to see it in action, I can't offer anything further.

[sparrowce]

Thank you, sent link to you via PM, site still under construction.

[DrByte]

Your configure.php file has an inconsistency:

HTTP_SERVER has a http://domainname.com URL
but your
HTTPS_SERVER has a http://www.domainname.com URL

Why do you have www. in one, but not in the other? You will have fewer problems if you maintain consistency.
Your certificate is issued primarily to the www. version, so probably best to settle with that.

[sparrowce]

Sorry, thought I had corrected that the other day when you helped me in another post about returning customers not being able to login, but I must not have done it right. Have corrected it now, and it didn't seem to change anything, possibly I still have not made the proper corrections.