Can Actinic cope with have the standard network settings running using our domain name but then having the ssl settings using a different url?
The Actinic partner hosting solution (Artisan) have provided documentation that suggests they have remapped our URL to a secure URL i.e. "https://<servername>.<domainname>/<sitename>/" = "http://<mydomain.com/". It is also suggested that for the remapping to work relative paths rather than absolute paths have to be used so I have also selected "Use relative CGI-BIN URL's in Catalog Pages" Ping on the the secure server brings back the same ip address as a ping on the domain name.
The following are the current settings :
Standard Settings
Catalog URL = http://<mydomain.com/acatalog/
CGI-BIN URL = http://<mydomain.com/cgi-bin/
SSL Settings
Catalog URL = https://<servername>.<domainname>/<sitename>/acatalog/ (this needed to be changed as well?)
CGI-BIN URL = https://<servername>.<domainname>/<sitename>/cgi-bin/
The site uploads without any errors but as soon as you select Checkout a redirect takes place to the SSL cgi-bin path which results in a HTTP 404 error indicating the page cannot be found. The redirect path being used is https://<servername>.<domainname>/<sitename>/cgi-bin/os000001.pl
Will this setup work?
They are running Apache/2.0.55. Does anyone know if (this being a shared server which I assume it is) it is possible to run Shared and Private SSL Certs side by side on the same server? One option maybe for me to purchase my own cert and run with that.
Other options
Maybe to use the built-in Actnic encryption. The only problem with this is that there is no visual indicator i.e. the industry standard golden padlock. I personally do not know anyone who would shop on the Internet and give out personal details without them being able to see that they are running in an encrypted session. Granted you could add into the T&C's that a proprietry built-in encryption method is being used but at the end of the day it's just words on a page which anyone could write. How do you go about proving to your customers otherwise?
The Actinic partner hosting solution (Artisan) have provided documentation that suggests they have remapped our URL to a secure URL i.e. "https://<servername>.<domainname>/<sitename>/" = "http://<mydomain.com/". It is also suggested that for the remapping to work relative paths rather than absolute paths have to be used so I have also selected "Use relative CGI-BIN URL's in Catalog Pages" Ping on the the secure server brings back the same ip address as a ping on the domain name.
The following are the current settings :
Standard Settings
Catalog URL = http://<mydomain.com/acatalog/
CGI-BIN URL = http://<mydomain.com/cgi-bin/
SSL Settings
Catalog URL = https://<servername>.<domainname>/<sitename>/acatalog/ (this needed to be changed as well?)
CGI-BIN URL = https://<servername>.<domainname>/<sitename>/cgi-bin/
The site uploads without any errors but as soon as you select Checkout a redirect takes place to the SSL cgi-bin path which results in a HTTP 404 error indicating the page cannot be found. The redirect path being used is https://<servername>.<domainname>/<sitename>/cgi-bin/os000001.pl
Will this setup work?
They are running Apache/2.0.55. Does anyone know if (this being a shared server which I assume it is) it is possible to run Shared and Private SSL Certs side by side on the same server? One option maybe for me to purchase my own cert and run with that.
Other options
Maybe to use the built-in Actnic encryption. The only problem with this is that there is no visual indicator i.e. the industry standard golden padlock. I personally do not know anyone who would shop on the Internet and give out personal details without them being able to see that they are running in an encrypted session. Granted you could add into the T&C's that a proprietry built-in encryption method is being used but at the end of the day it's just words on a page which anyone could write. How do you go about proving to your customers otherwise?
Comment