From: Gustaf N. <ne...@wu...> - 2017-04-07 15:01:22
|
Hi David, thanks for testing! I think, i have fixed the problem with: https://bitbucket.org/naviserver/naviserver/commits/221d0c8f629bb29235e156a781ca5599284c3e9d The bug was a problem in nsssl triggered by "ns_connchan close". The same verison of revproxy should work. all the best -g Am 06.04.17 um 12:21 schrieb David Osborne: > 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 <ne...@wu... > <mailto:ne...@wu...>> 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 > |