CODEWITHSUNDEEP
delphiindy
user7415109
user7415109

Reputation:

Delphi TIdHttp with proxy sometimes no timeout and a GET does not return

I use Delphi 10.2 Tokyo with Indy (the integrated version).

Scenario: I do http GET requests (TIdHttp) in threads, and use proxies. Sometimes, a proxy seems to cause Indy not to timeout, and not to return from a GET. I also assign the onWork event handler to react to an Abort button and call within this handler the idHttp.Disconnect function. When the GET seems to be frozen, the abort also does not work, possible that in this case the onWork event is not triggered, I have no idea.

The main thread is idle and only create lets say 50 threads, each does a GET via its instance of TIdHttp. Ans sometiumes, as I mentioend, a proxy cause of GET not to return which result then in a "hanging" thread.

My question is: How can I force Indy to abort, from an external thread? Is there anything what can be done via code when the GET refuse to return?

Upvotes: 0

Views: 499

Answers (1)

user7415109
user7415109

Reputation:

I solved my issues by using a background thread to disconnect sockets and implement a timeout, which seems to work even socket are "frozen" and the onWork is not triggered. I do this by adding the TIdHttp instances I create to an array, together with the time the instance was created. If the GET return normal, the array entry will be removed. In a background thread, I check if the user clicked Abort, and then loop through the array and call disconnect on each instance. I also check in the same thread if a timeout period was reached, and also call disconnect. Might not be the perfect solution, but it works for me.

Upvotes: 0

Related Questions