durusmail: qp: specifying host for scgi, durus, etc.
specifying host for scgi, durus, etc.
2006-03-30
2006-03-30
Re: specifying host for scgi, durus, etc.
2006-03-31
2006-03-31
2006-03-31
2006-03-31
2006-03-31
2006-03-31
2006-04-01
2006-04-01
2006-04-01
2006-04-01
2006-04-01
2006-04-01
2006-04-01
2006-04-02
specifying host for scgi, durus, etc.
David Binger
2006-03-30
On Mar 30, 2006, at 4:24 PM, mario ruggier wrote:

> In the various examples of how hosts are specified, for durus,
> scgi, etc, for a QP site, I see the following 3 values used
> seemingly interchangeably to specify the same local host:
>
>   ''
>   'localhost'
>   '127.0.0.1'
>
> Is there an effective difference between these 3? What is it?
>
> I was under the impression that specifying 127.* implies an
> internal local network, and should not be seen from the outside,
> but it seems to be anyway (at least on the freebsd machine I am
> testing this on).

If "" is used as the host, I hope the server is visible
on all interfaces.

I hope that binding a server to 127.0.0.1 or localhost does
not really also bind it to other interfaces.

The host in the https_address in the QP configuration is not really used
for binding.  It is there for the purpose of constructing the url that
should be used when there is a redirect from the http to https address.
The binding of that listener is controlled by stunnel (if you are using
stunnel), so the https server might be visible from outside even
if the host of the qp site's https_address is localhost or 127.0.0.1.
I hope that's what is causing the confusion here.



reply