Re: [naviserver-devel] ns_conn status

2020-09-10 Thread David Osborne
Thank you very much Gustaf On Tue, 8 Sep 2020 at 19:12, Gustaf Neumann wrote: > Dear David, > > You assumption is right, ... AFIKT there is no problem with the case, > when "ns_conn status" is called without additional argument in a trace. > i have added code to bitbucket handle the case with

Re: [naviserver-devel] ns_conn status

2020-09-08 Thread Gustaf Neumann
Dear David, You assumption is right, ... AFIKT there is no problem with the case, when  "ns_conn status" is called without additional argument in a trace. i have added code to  bitbucket handle the case with and without arguments differently. all the best -g On 07.09.20 17:53, David Osborn

[naviserver-devel] ns_conn status

2020-09-07 Thread David Osborne
Hi, I notice that "ns_conn status" is flagged in conn.c as requiring an active connection (NS_CONN_REQUIRE_CONNECTED rather than NS_CONN_REQUIRE_CONFIGURED). The http status code is useful to be able to query in a trace after the connection is closed. Obviously that use-case is now incompatible gi