Re: [naviserver-devel] ns_param location - change of behaviour for ns_returnredirect

2021-01-25 Thread Gustaf Neumann
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 Dav

Re: [naviserver-devel] ns_proxy segmentation fault under Debian Stretch

2021-01-25 Thread David Osborne
Thank you - working perfectly now. On Sun, 24 Jan 2021 at 18:23, Gustaf Neumann wrote: > Dear all, > > The 4.99 branch (bug-fix branch for the 4.99 family) is now updated > with the change of David. Additionally, i have added basic test cases via > introducing a new command "nscp users". > > al

[naviserver-devel] ns_param location - change of behaviour for ns_returnredirect

2021-01-25 Thread David Osborne
Hi again, We're also having issues with the use of the "location" param to specify the location for ns_returnredirect in the latest version of naviserver. We used to be able to have something like: ns_section ns/server/default/module/nssock ns_param location https://domain:port ... And a "ns