J=E9r=F4me Desquilbet wrote:
>I guess it is a very basic question, but I am not familiar with the
>settings of concurrent web servers, reverse proxies, etc.
>My system runs Yaws and I am happy with it, but I would need to run
>Apache as well. I can set Apache to listen to 8000 (for example)
>instead of 80, i.e. to have
> http://www.firstdomain.org/ run by Yaws
>and http://www.seconddomain.org:8000/ run by Apache.
>But I would prefer to get rid of the :8000. My understanding is that I
>could use Yaws as a primary server and let it forward the requests for
>www.seconddomain.org to Apache.
>But I don't understand how to practically implement this. Would
>somebody be kind enough to spend some time writing down the piece of
>yaws.conf needed to run this example (and any other useful
Yaws has a reverse proxy implementation which is kindof working.
I'm running it in my house in exactly the same setup you have above:
port =3D 80
listen =3D 0.0.0.0
docroot =3D /tmp
revproxy =3D / http://silver
On the internet, silver.hyber.org exists, but all request to that
server are proxied to http://silver which is another host internally
Another alternative is to setup a simple redir, thus some domain
has a index.yaws file which only contains a redir to the other domain
(Downside here is that bookmarked urls look bad, i.e will contain the :80=