<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [Seaside] Starting a site</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Does 2.0 support wildcard IPs to listen on all interfaces?<BR>
<BR>
Cheers!<BR>
<BR>
-Boris<BR>
(Sent from a BlackBerry)<BR>
<BR>
----- Original Message -----<BR>
From: seaside-bounces@lists.squeakfoundation.org <seaside-bounces@lists.squeakfoundation.org><BR>
To: The Squeak Enterprise Aubergines Server - general discussion. <seaside@lists.squeakfoundation.org><BR>
Sent: Wed Aug 22 07:23:07 2007<BR>
Subject: Re: [Seaside] Starting a site<BR>
<BR>
Hi Andrés,<BR>
<BR>
Andres Fortier wrote:<BR>
> thanks Janko, it works like a charm. Now, have a doubt: if I try<BR>
> accessing the site in the old way (<A HREF="http://localhost:8001/">http://localhost:8001/</A>...) it doesn't<BR>
> work anymore; is there a way to configure the site (or the server) to<BR>
> listen to both the ip and localhost?<BR>
<BR>
Yes, you can add one or more aliasese to the Swazoo Site. And not only<BR>
hostname aliases but a whole host:ip:port combination. And that's what<BR>
you need to do in your case:<BR>
<BR>
1. SwazooServer stop<BR>
2. inspect your Site<BR>
3. yourSite addAlias:<BR>
(SiteIdentifier host:'localhost' ip:'127.0.0.1' port: 8001)<BR>
4. SwazooServer start<BR>
<BR>
If you inspect now a SwazooServer singleton servers, you'll now see two<BR>
HTTPServers serving on two ip:port combinations but for the same Site!<BR>
<BR>
Best regards<BR>
Janko<BR>
<BR>
<BR>
><BR>
> Thanks again,<BR>
> andreś<BR>
><BR>
> Janko Mivšek escribió:<BR>
>> Hi Andrés,<BR>
>><BR>
>><BR>
>> Andres Fortier wrote:<BR>
>>> Hi list,<BR>
>>> First of all I must say that my knowledge in networks is very<BR>
>>> limited, so maybe this is well-known in the community.<BR>
>>><BR>
>>> I've finally finished my simple site, put it in the server and tested<BR>
>>> it via <A HREF="http://localhost:8001/">http://localhost:8001/</A>...<BR>
>>><BR>
>>> Now, the strange thing is that if I try to access it by using the<BR>
>>> server ip (<A HREF="http://xxx.yyy.zzz.www:8001/">http://xxx.yyy.zzz.www:8001/</A>...) it doesn't work. I've<BR>
>>> been told by the guys in tech suport that the server was only hearing<BR>
>>> in the localhost interface and that I should set it up to listen in<BR>
>>> all the other interfaces. Any ideas how to solve this? I'm using<BR>
>>> Seaside with Swazoo on VW.<BR>
>><BR>
>> Try to do something like this:<BR>
>><BR>
>> 1. SwazooServer stop.<BR>
>> 2. Inspect SwazooServer singleton sites and in your site inspect<BR>
>> uriPattern.<BR>
>> 3. set host:ip:port: combination accordingly. For instance:<BR>
>> host: 'www.mysite.com'<BR>
>> ip: 'xxx.yyy.zzz.www'<BR>
>> port: 8001<BR>
>> 4. if necessary put in hosts file on your computer:<BR>
>> xxx.yyy.zzz.www www.mysite.com<BR>
>><BR>
>><BR>
>> I hope that helps<BR>
>><BR>
>> Best regards<BR>
>> Janko<BR>
>><BR>
><BR>
<BR>
--<BR>
Janko Mivšek<BR>
AIDA/Web<BR>
Smalltalk Web Application Server<BR>
<A HREF="http://www.aidaweb.si">http://www.aidaweb.si</A><BR>
_______________________________________________<BR>
Seaside mailing list<BR>
Seaside@lists.squeakfoundation.org<BR>
<A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
</FONT>
</P>
</BODY>
</HTML>