I should have mentioned that to duplicate this, you use
ns_getform first on the connection, then use ns_conn form.
After looking at the code, my theory is that ns_getform
doesn't set the state variables that [ns_conn form] is
looking for, so the call to [ns_conn form] calls
Ns_ConnGetQuery and eventually tries to read the POST data
from the connection. But it has already been read by
ns_getform, so after a 30 second socket timeout, it
returns.
Suggested fixes might be to put ns_getform in conn.c or put
helper functions in conn.c that ns_getform can call to set
state vars.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=291997
I should have mentioned that to duplicate this, you use
ns_getform first on the connection, then use ns_conn form.
After looking at the code, my theory is that ns_getform
doesn't set the state variables that [ns_conn form] is
looking for, so the call to [ns_conn form] calls
Ns_ConnGetQuery and eventually tries to read the POST data
from the connection. But it has already been read by
ns_getform, so after a 30 second socket timeout, it
returns.
Suggested fixes might be to put ns_getform in conn.c or put
helper functions in conn.c that ns_getform can call to set
state vars.
Logged In: YES
user_id=20624
New connection I/O model in 4.0 isn't subject to this
read-ahead problem. Would be difficult to work around
problem in 3.x.