Wipe_out Posted September 16, 2002 Share Posted September 16, 2002 Hi All, I know that OSC can run quite happily on a shared SSL setup.. I would like to know from those of you running shared SSL setup's is what settings you have had to modify in the 'configure.php' file.. I am having some trouble getting all the paths to play nicely together.. The setup is as follows.. non-ssl URL: http://www.site1.com shared ssl URL : https://www.securesite.com/www.site1.com catalog path : /catalog admin path : /admin /www.site1.com in the secure site is an alias in Apache pointing to the home directory (/var/www/www.site1.com/html) of the non secure website... The other option which may solve the problem would be to use a symlink form the secure site to the non secure home directory instead of the alias and then configuring the paths in configure.php to reflect paths within the secure site itself which would probably work but if possible I would like to manage as much as possible from Apache.. So I guess what I am asking is for as much information as possible from people on shared ssl servers so I can see what the best way to go is.. and which setups you are using (Alias or symlink??).. Thanks.. Link to comment Share on other sites More sharing options...
jalil Posted September 17, 2002 Share Posted September 17, 2002 I may not answer you correctly, but try changing the setting in /includes/configure.php the setting of the https pointing to https://www.securesite.com/www.site1.com. Does it works? Alternatively, try getting a free SSL cert at http://www.freessl.com which is valid for one year so that it can point to https://www.site1.com/ Regards, Jalil Please give your rating on OSCommerce at FreebiesCafe.com, a search directory for free scripts, software, services and resources. Link to comment Share on other sites More sharing options...
Wipe_out Posted September 17, 2002 Author Share Posted September 17, 2002 Thanks Jalil.. I am quite farmiliar with the configure.php now...but unfortuantely this is not the issue..the main question is wheather to use an apache alias or a symlink in the linux filesystem and which is easier to administer all round.. The problem with the freeSSL cert is the limited browser compatibility and the fact that people are still a little uneasy about using their credit card online so a message warning them about the cert really doesn't halp matters.. for that reason I use a Thawte Cert which gives the best browser compatibility at the best price...In a few years when the older browsers dissapear the certs from places like instanssl and geotrust will be very cost effective.. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.