It should close only when post limit exceeds, other requests should not
be affected. It looks like broke something
Stephen Deasey wrote:
On 3/9/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
Stephen Deasey wrote:
I'm getting a lot (123) of what looks like bogus test failures on a
fresh checkout. Are the recent changes to the nstest_http proc OK?
Yes, i noticed this as well, this is because server now can close
connection during client sending the body and i tried to put catch
around close in all places but still it complains on close.
This is new behaviour? Why would the server close the connection
while the client is sending data?
I'm getting in failures in e.g. test/url2file.test:url2file-2.1 which
looks like:
test url2file-2.1 {ns_url2file} -setup {
ns_register_proc GET /url2file {ns_return 200 text/plain
[ns_url2file /foo] ;#}
} -body {
nstest_http -getbody 1 GET /url2file
} -cleanup {
ns_unregister_proc GET /url2file
} -result [list 200 [ns_pagepath foo]]
This is just a simple GET request, no body. Test error is:
---- Test generated error; Return code was: 1
---- Return code should have been one of: 0 2
---- errorInfo: can not find channel named "sock24"
while executing
"close $wfd"
invoked from within
"nstest_http -getbody 1 GET /url2file"
("uplevel" body line 2)
invoked from within
"uplevel 1 $script"
---- errorCode: NONE
==== url2file-2.1 FAILED
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
_______________________________________________
naviserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
