When creating a Reverse proxy environment with Apache and XOOPS i walk against some problems :

First the Reverse entry which is made on the Proxy Server:

#Xoops Portal Entry on 10.0.1.1 Server
#
ProxyPass /portal/http://10.0.1.10/portal
ProxyPassReverse /portal/http://10.0.1.10/portal

Second the configuration of mainfile.php on the .10
server:

define('XOOPS_URL', '/portal');



So if there is a GET request on 10.0.1.1 for "/portal"
it proxies all data coming fromhttp://10.0.1.10/portal

prob #1 - Images not displayed because of define('XOOPS_URL', '/portal'); ##can be solved

prob #2 - When loggin in XOOPS_URL gets duplicated and redirect goes wrong

i.e.http://10.0.1.1/portal/10.0.1.10/portal/modules/mydownloads


prob #3 - Administration of blocks is acting 'foo' it does not matter what action gets performed (deleting,adding,modifying) it will FAIL

prob #4 - Administration of module (updating,disactivating,uninstall) is acting foo to...
nothing will work

Is there any workaround for this ? or perhaps a FIX ?

It would be a waste to implement XOOPS as a dynamic system
when it aint possible to work in combination with mod_proxy ... cause if it won't work ..XOOPS aint that flexible as i stated before.

Please show me that it has the flexibility

does it work with the following:

define('XOOPS_URL', 'http://10.0.1.10/portal');

mod_proxy should work just fine. I'm guessing that the reverse proxy is handling internet users to reach an internal server?

You need to use the DNS name that is being used from the outside as the XOOPS configured URL:

define('XOOPS_URL', 'http://www.yourdomain.com/portal');


The proxy config might be (note trailing slash):

#Xoops Portal Entry on 10.0.1.1 Server
#
ProxyPass /portal/http://10.0.1.10/portal/
ProxyPassReverse /portal/http://10.0.1.10/portal/


This should work for outside users. For inside users you'll need to set-up DNS or a hosts file that points www.yourdomain.com to the internal IP (10.0.1.10) or to the proxy server if you prefer.

This assumes that your XOOPS site is indeed at /portal. If it is at the root / then a different config is needed if the outside IP also handles other sites (can use proxy config inside a NameVirtualHost config). Bottom line is that the browser URL needs to match the XOOPS config URL.

Thank you both, i was not able to use DNS but i fixed that

everything works well now; a DNS entry was the workaround


with kind regards,

Remy