My client's site is hosted on a shared server. The front end of the site will be available at the root of their domain, but as they doesn't have their own SSL cert, I want to use the shared cert from the web host for the backend. In order to do this, the backend will be accessed via a different URL, and it happens to also include a path.

That is to say, the front end of the site will be located at:

http://www.mysite.com/

But the backend will be located at:

https://www.webhost.com/~myaccount/

If I specify the front-end URL in the config file for K_SITE_URL, the backend doesn't work properly because all the references to CouchCMS css and images use the non-TLS URLs and the browser doesn't load them since the main URL is HTTPS. But if I specify the backend URL, the backend works, but the front-end has issues: links to uploaded files aren't right, etc (they look like "https://www.webhost.com/~myaccount/couch/uploads/image/foo.png" instead of "http://www.mysite.com/couch/uploads/image/foo.png").

Is there some way to simply specify separate roots for front-end and backend?

[KK]

Hi Brian,

I don't think that would be possible, I'm afraid - the URLs of the backend and frontend are much too intricately tied up with each other to make the separation.

Thanks for the reply.

Okay. Any other suggestions on how to allow my users to log in securely with this setup?

Brian

I think a self-signed certificate would be suitable for this purpose.

I think a self-signed certificate would be suitable for this purpose.

Well, maybe not. Same issue with unsecured content served from the http domain set in the config file.

It sounds like it's going to be the easiest to just buy a cert for the domain. We only need to secure the backend to protect the user credentials, so it doesn't need to be one of those EV certs. Thanks for the help!