Dear David
I haven't tested connection creation timeouts. Only the situation where the backend accepts the connection but takes a long time to respond.
(My testcase is a backend URL which just does "ns_sleep 100000")
It is an https backend. Running naviserver 4.99.16d4. Debian 8.6 with kernel 3.16.39-1+deb8u2.
i've committed an improved version handling timeouts to bitbucket. The "-timeout" value goes straight to Ns_SockCallbackEx() and is a actually a timeout for the next poll on the underlying socket. Returning a proper HTTP return code works only, when the backhand has sent not data back on this connection.

The change works well for me. Please, check, if this works for you (tested with Mac OS X and http) or if i need a linux-box for further testing.

all the best
-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

Reply via email to