One other solution might be adding another domain in the sites.xconf file that 
contains the DNS name configuration.
As far as I know this was never tested for the CMS, but theoretically it should 
work.

Regards,

Jeroen


-----Original Message-----
From: [EMAIL PROTECTED] on behalf of toolman
Sent: Wed 6/4/2008 11:26 AM
To: Hippo CMS development public mailinglist
Subject: Re: [HippoCMS-dev] localhost/inernal ip/external ip
 
The cocoon CMS looks at the incoming server name and compares it against
the value set in build.properites (maven.cocoon.site.domain=example.nl).
To make it work in both internal and external, you need to have a
correct DNS setup so that example.nl gotes to the correct place both
internally and externally.  

If you are on linux you can cheat by adding the dns entry to
your /etc/hosts file - useful for dev work sometimes :).

Hope this helps,


-  
Tim Taylor
JTeam


On Wed, 2008-06-04 at 11:15 +0200, Arjan Duijs wrote:
> I am having trouble to reach our CMS through an external IP addres that
> is routed to an internal IP.
> 
>  
> 
> And external ip address is configured to forward all http traffic to an
> internal ip address
> 
>  
> 
> When Domain set to Localhost I am unable to reach it through the
> internal AND external IP address.  Getting the apache cocoon welcome
> page.
> 
>  
> 
> When domain set to the internal ip adsress, still getting the cocoon
> welcome page through the external request.
> 
>  
> 
> But when setting <domain> to the external ip address I am able to reach
> it from the outside web, but through the local network I am getting the
> cocoon welcome page.
> 
>  
> 
> Is there any solution for this to work on both internal and external ip
> address?
> 
>  
> 
> Thanks in advance
> 
>  
> 
> arjan
> 
> ********************************************
> Hippocms-dev: Hippo CMS development public mailinglist
> 
********************************************
Hippocms-dev: Hippo CMS development public mailinglist

********************************************
Hippocms-dev: Hippo CMS development public mailinglist

Reply via email to