I had the exact same problem when using apache to do SSL + proxying. You can see it here:
I didn't find any fix to the jiveURL problem, but the solution suggested, albeit a bit hacky, did work.
- Shut down clearspace
- Go into /path/to/clearspace/server/webapps
- rm -rf ROOT
- ln -s clearspace ROOT
I suspect that this is not a best practice, but it did work for me to get apache+CS running at the root of my site, without relying on jiveURL.
Well, I'm actually not deploying it at the root of the site. It's still https://hostname/clearspace, I'm effectively just proxying the port number out. I've got several apps on the server that have web interfaces running on different ports and I'm attempting to just proxy all those requests through the main web server. SSL was something I thought I'd get for free since the main web server supported it and it would be the one my clients were trading data with.
Hm, I'm not sure what it would be then, I had proxying with apache+SSL working just fine with the site at htt://server/clearspace/. But I definitely did notice that jiveURL worked strangely at best and not at all most of the time...
I'm seeing the following behavior when running the standalone clearspace 1.5 distro through ssl:
When I am viewing the page through ssl, the clearspace logo in the upper left displays an https link. When I am not viewing the page through ssl, the clearspace logo displays an http link. When I click on a link in the site (e.g. to view a thread) I will see the page through https -- and the logo uses the https link.
Is this consistent with what everybody is seeing on their pages?
Are there any other specific places where the jiveurl property seems to break down?