Dear David,
The i could reproduce the problems, which showed up only for
configurations with local network drivers (loading the driver
in the server specific section, not in the global section).
In general, the definition over the global section is recommended,
since it supports virtual hosting. Nevertheless, also the "old style"
local definitions should continue to work. The computation is
somewhat complex, since one cannot trust the content of the
host header field blindly, and since a single driver can listen
on many IP addresses and ports and connect to multiple virtual
servers.
The updated version in the public repository computes now the value
of [ns_conn location] (and the redirect target) is computed by
the following rules.
Globally defined network driver (recommended installation, supports
virtual hosting)
a) Use content of host header field, when the value is configured as an
accepted host for one of the servers.
b) If the host value is different, fall back to the default server
(a default server has to be configured).
c) If the request has no host header field, fall back to the default server.
Per-server network driver:
a) Use content of host header field, when the valued is configured as an
accepted host for the server.
b) If the host value is different or missing (allowed in HTTP/1.0),
fall back to the value as configured in the driver parameter "location".
c) If the driver parameter "location" is not given, use the actual
local IP address and port for determining the location.
Please check whether this works as well with your configurations.
all the best
-gn
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
