On 25.01.21 17:42, David Osborne wrote:
This is part of the commit which seems to be changing the behaviour in our case in SockSetServer in driver.c.. sockPtr->location would have previously been set to drvPtr->location here and passed on to connPtr->location in NsQueueConn I think.
Dear David, i will look into the details the next days. In general, the "location" in the driver is a problematic field in case virtual hosting is involved (you do not want e.g. to redirect always to a fixed location with a fixed port), but this decision should be driven by the host header field. There is also some support (ns_locationproc) in NaviServer for providing custom location handlers, since the default behavior is known to be problematic. I will come back to you later this week after doing some investigations based on your provided configuration example. all the best -g https://naviserver.sourceforge.io/n/naviserver/files/ns_locationproc.html _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
