Neat! I have been wondering how to do that. It is also useful if you want to
run multiple happstack applications on the same machine, but each on a
different IP address.
It would be awesome if this was wrapped up in a more obvious way. I imagine
we would extend the Conf type so that you could
Hello haskellers,
I want to host a simple happstack application behind a reverse proxy. So
ideally would be to bind it to localhost only.
According to
http://hackage.haskell.org/packages/archive/happstack-server/0.4.1/doc/html/Happstack-Server-HTTP-Types.html#t%3AConf
Conf datatyle has only
Hi Dmitry,
On Thu, Mar 11, 2010 at 11:38:44AM +0300, Dmitry V'yal wrote:
Hello haskellers,
I want to host a simple happstack application behind a reverse proxy. So
ideally would be to bind it to localhost only.
According to
You misunderstand his question. He's trying to setup happstack behind a
reverse proxy running on the same system, so he needs to be able to bind it
only to the loopback interface (127.0.0.1), as opposed to all the interfaces
on the system (thereby making it inaccessible from the network unless
On Thu, Mar 11, 2010 at 09:24:05AM -0500, Kyle Murphy wrote:
You misunderstand his question. He's trying to setup happstack behind a
reverse proxy running on the same system, so he needs to be able to bind it
only to the loopback interface (127.0.0.1), as opposed to all the interfaces
on the
Ah, I see, I was looking at the example code in the Happstack documentation
you linked. Looking at the documentation of Network.Socket I can see where
it provides an option to bind on a particular address. The example given in
the Happstack docs uses bindPort to get the socket which confused me as