Hi Brian,
The proper solution is not to skip the error message, but to skip the
full connection output operations in error situations. Since this
involves many commands (from ns_return*, ns_write, ns_cookie* ...) this
is a larger change. I will look into this in the next days. Should be
Hi Gustaf
my apologies, I hadn't realised that silencing the log would lead to different
behaviour. If this is a bigger job than expected, please feel free to revert
back to previous version. It's a nice-to-have feature for us.
The attached script reproduces the issue when the parameter is set
Hi Brian,
as stated several times, the right action is to fix your script (as you
did) rather than "silencing" NaviServer. I am not surprised, that
attempts to write on detached connections can lead to error conditions
on several occasions (generating errors avoids this).
But since we
Hi Gustaf
I just built and ran some tests on the "rejectalreadyclosedconn" parameter to
see how it handles code that triggers the "connection socket is detached" error.
If I set "rejectalreadyclosedconn" to false, and browse to a page that
triggers the "connection socket is detached" error,
