Dear David,
I could reproduce the behavior. The problem was due to a change about a
year ago, which reduced code duplication in cases, where no section for
nsproxy was provided in the configuration file. In reported case, it was
looking for "ns/server/default/module/nsproxy". This explains as well,
while this was not noted earlier.
The version on bitbucket has this problem now fixed. I have extended the
API slightly to reduce complexity.
All the best and many thanks for the report.
-gn
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
