Hi Arjan,
Usually the trick is to configure the cms on localhost (in sites.xconf
and cocoon/WEB-INF/configurations/localhost/Domains.xml) and use apache
or another webserver as reverse proxy in front of the CMS for virtual
hosting.
Regards,
Bart
Arjan Duijs wrote:
So its either setting the external ip, or the internal ip meaning i have
to exclude 1 group of users.
(local network users can not access the external ip addres and vice
versa)
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeroen
Reijn
Sent: woensdag 4 juni 2008 11:47
To: Hippo CMS development public mailinglist; Hippo CMS development
public mailinglist
Subject: RE: [HippoCMS-dev] localhost/inernal ip/external ip
You are correct. Thanks Ard.
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Ard
Schrijvers
Sent: Wed 6/4/2008 11:42 AM
To: Hippo CMS development public mailinglist
Subject: RE: [HippoCMS-dev] localhost/inernal ip/external ip
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.
No, it does not work (we experienced it some time ago as well, because
we tried the regexp domain matcher you can configure in sites.xconf,
which works just fine for sites). You'll get workflow issues.
Furthermore, the cms has 2 files where its domain is stored, not only in
sites.xconf.
-Ard
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
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
--
Hippo B.V. - Amsterdam
Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466
Hippo USA Inc. - San Francisco
101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646
-----------------------------------------------------------------
http://www.onehippo.com - [EMAIL PROTECTED]
-----------------------------------------------------------------
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
