Back in the BV 2004 days, if a site was setup with shared SSL, and maybe SSL in general, it was required to have a copy of the webconfig file in the BVadmin area, in addition to the root directory, so I was wondering if this is still required?

Everett,

Does the SSL path need to be listed in the web config anywhere? I ask as I have a site that I just went live with and it is having trouble transitioning in and out of SSL, and appliedi.net is trying to nail down what is happening. It is a shared SSL certificate.

The shared domain path is https://secureserver33/appliedi.net/ihats/

I just received an email from Scott Brown at Appliedi, and he conferred with me that the path that is given by say the order to the admin area contains an absolute path, and not a relative path, which makes it impossible to use the shared SSL. In short, when I select the area on the email to go to the order, I am taken to the login page, but from there the absolute path is given to get to the order, which leaves out the ihats part of the secure path, which in turn goes to a page not found. I am using different top level domains, as it is shared SSL, and I did have that option checked. I did not have anything in the cookie area, as there is no documentation as to what to put in those areas of the security area.



Can you shed some light on this?