Closed ghost closed 1 year ago
@alekstovkach i will try to look into it :-) thanks for reporting
Hello and thank you for the amazing library. Have you had a chance to take a look at this issue?
Thanks
The client closes the TCP connection after 30 seconds (even if I send a request every second). Can this be fixed? Opening a new TCP connection every time is an extra resource consumption =)
i am facing the same issue.
Every 30 seconds i receive response with read tcp : i/o timeout
error (even if I send a request every second).
it will run smooth for 30 seconds, hit this error then continue to run smooth again and so on.
Strangely if i change "timeoutSeconds": 30,
to "timeoutSeconds": 45,
then every 45 seconds i receive response with read tcp : i/o timeout
error. seems it closes the TCP connection based on the timeout you have set?
im using the tls-client-windows-64-1.3.8.dll. With proxies & following the python examples
@alekstovkach @fpena06 @Jamucy special thanks to all of you for the patience and the information.
I think/hope i solved that in the latest release: https://github.com/bogdanfinn/tls-client/releases/tag/v1.3.9
Please give me feedback 🤞
@alekstovkach @fpena06 @Jamucy special thanks to all of you for the patience and the information.
I think/hope i solved that in the latest release: https://github.com/bogdanfinn/tls-client/releases/tag/v1.3.9
Please give me feedback 🤞
yes from my (small) test the issue now seems to be fixed :)
thank you!
The client closes the TCP connection after 30 seconds (even if I send a request every second). Can this be fixed? Opening a new TCP connection every time is an extra resource consumption =)