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 10")
It is an https backend. Running naviserver 4.99.16d4. Debian 8.6 with
kernel
These changes are now in the repository at bitbucket and running on
OpenACS.org.
I've as well committed the changes for Coockie-Encoding RFC 6265 (HTTP State
Management Mechanism, 2011) (together with new calls for
Ns_Cookie[En|De]code()),
such we have now a well defined state based on the actu
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 second
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 linu
