It seems like that the webclient dat will always disconnect after 60 seconds, even when the timeout parameter is set to a value way above the 60000 (btw would be nice if the docs mentioned that these are miliseconds.)
Requests below 60 seconds will come trhough nicely but at point 60 seconds we get a “disconnect” callback.
I tested this with the TD-Internal Webserver and the aiohttp package.
Example attached
SwallowedResponse.zip (1.8 MB)
Hi @plusplusone,
thanks for reporting this, can reproduce and we are having a look.
Wiki is updated to include reference to millisecond unit of the timeout parameter.
cheers
Markus
This is because the webclientDAT.request method doesn’t use parameter values when it has arg/kwd counterparts, and the timeout kwd defaults to 60000. The parameter values such as Timeout are used when pulsing the Request parameter, which may not be intuitive, but it is an entirely different workflow from the python request method. Now, perhaps for the case of timeout we can change the default kwd value to be the value of the Timeout parameter.
Hi Eric,
thanks for the info! I was not even aware of the fact that there is a timeout keyword.
I implemented the according change and suppose with that the issue is resolved!
