The warning is gone now.
Happy new year!
Wolfgang
Am 01.01.20 um 08:33 schrieb Gustaf Neumann:
This is probably still not perfect. i've made one more change to make
the handling of closed connection inside filters more general. If this
is still shows the warning, we have to get into more deta
This is probably still not perfect. i've made one more change to make
the handling of closed connection inside filters more general. If this
is still shows the warning, we have to get into more details.
Please test the updated version if possible.
Happy new year!
all the best
-g
On 31.12.19
Dear Gustaf!
NaviServer does not crash anymore, we get a "connection socket is
detached" warning.
Thanks for the fix and a happy new year,
Wolfgang
Am 30.12.19 um 20:50 schrieb Gustaf Neumann:
> ... To use "filter_break" in this situation is an error on our side ...
Dear Wolfgang,
I could
> ... To use "filter_break" in this situation is an error on our side ...
Dear Wolfgang,
I could reproduce the problem with a filter returning "filter_break", when
the filter has already closed the connection to the client. In such cases,
no further replies are possible to this client.
i've add
This is good news!
At the current tip version we encountered a signal 11 error. It happens
in a filter, when we raise an error and return "filter_break". With
"filter_return", there is no problem. To use "filter_break" in this
situation is an error on our side but maybe the crash can happen in
