Re: "mounting" helma app behind apache

Hello Walter,

VividVisions, Walter Krivanek schrieb:
> I think you'll have to set "baseUri" in app.properties.
> http://helma.org/docs/guide/properties/listall#baseURI
Thanks, links are fixed now but there are still issues:

Config is now:
>> <VirtualHost helma.test.home:80>
>>   ServerName helma.test.home
>>   ...
>>
>>   <Location /helma>
>>      ProxyPass http://localhost:8080/ #thats jetty's http listener
>>   </Location>

reference installation accesses helma directly over
http://localhost:8080, the only difference wrt server.properties is
"baseURI = /helma" for the "behind apache" version.

Problems with "behind apache" and baseURI = /helma:

- links for static content are incorrect, e.g. /static/helmaheader.png
is not found.

- accessing /manage over http://helma.test.home/manage doesn't work, I'm
 just getting the welcome-page no matter what URL the browser asks for.
Haven't tested other apps for now.


So either there are still some knobs and levers I haven't touched (to
many over here ;)) or this setup simply doesn't work and you need one
<VirtualHost> for each helma instance, thats basically what I need to know.

We had some stability issues with mod_jk in the past, but I'm certainly
willing to try it again if it solves the "need one vhost per helma
instance" problem. On a sidenode, mod_jk doesn't seem to be available
for apache-2.2 (used here) and my tests with mod_proxy_ajp and
helma-1.5.2 showed some protocol incompatibilities wrt AJP13, so this is
a no-go ATM...

thanks
 Paul