Thanks very much.
That's similar to what I was trying (although I was setting the timeout for
the backendReply callback only since it should be the first thing to be
called on reply if I understand rightly).
I get the same behaviour with your code.
Say I request a backend URL that takes 10 seconds to reply, and the proxy
timeout is 5 seconds...
I see the following:
1. URL requested in browser.
2. Browser starts to spin waiting for reply
<after 5 seconds>
3. I see the timeout being logged in the proxy and the 504 write is
performed.
4. No change in browser continues to spin waiting for a reply
<after another 5 seconds>
5. The browser receives a 504 and completes the request.
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.
--
David
------------------------------------------------------------------------------
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
