Hi Gustaf,
I can confirm that if I switch to using http (rather than https) then your
timeout modification works perfectly.
So looking like it's (at least) ssl specific,
On 5 April 2017 at 18:03, Gustaf Neumann <neum...@wu.ac.at> wrote:
> Am 05.04.17 um 18:45 schrieb David Osborne:
> > So although the timeout has occurred in the proxy code, the connection
> > appears to still have to wait for the backend to close the connection
> > before continuing.
> on my test setup, everything is closed correctly. this is either
> ssl-specific, or linux-specific. will check.
> -gn
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> naviserver-devel mailing list
> naviserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
