shared ssl setup

[thesauce98]

I've searched these forums for about 5 hours a day the past week, trying to fix bugs I keep getting. One annoying I haven't found the answer to s this: My web hosting company provides shared SSL through another site. Therefore, my normal site is at www.domainname.com, and the ssl site is at www.3rdpartySSLsite.com/domainname

I got everything working kinda well between going to the different sites for different needs (logging in/out, checkout), except for some small problems.

Once your on the SSL site, all the images (like product images in whats new or specials on the side) come from the SSL site. How exactly is a new product image supposed to get to the SSL site, when u se the regular site's admin page to create the new product, and upload the image there? How of other people worked around this?

Also, when users go to login, they are redirected to the SSL site, which is fine. Once they fill it out and try to login, the page then gets redirected to a wierd URL, which is somewhat of a hybrid of the regular and SSL server, and then page cannot be displayed. However if you then retype the first part of the URL in the browser, it goes to the site and ur logged in. Seems like a redirection problem after logging in. Any ideas?

Thanks.

[thesauce98]

well i fixed the logging in part, but i'm still wondering how people on shared ssl from a different server are handling product images ... is there maybe a mod to store the images in the database (blob type) so all the images can be pulled from there? i'm really just trying to make the site owners life easy, so he doesn't have to add new products to the regular server and ftp a copy of the image to the shared ssl server. thanks.

[michael_s]

thesauce98, you have to manually FTP the images to the correct corresponding image dir on the SSL server.

The weird hybrid url is most likely due to a small syntax problem in the path setup. You will need to tweak the http and https server urls, as well as play around with the http and https cookie paths. Trial and error is really the best way. I suggest keeping a safe copy of the current config, since it mostly works, then tweak away on the paths until you get the desired result. Many times, it is just a matter of moving the username and maybe the first path dir to the https url and removing that from the cookie path.