0

It is valid behavior that an http(tcp) request can get lost without the listeners get informed. see here for the discussion on that: C# httpClient (block for async call) deadlock

Problem We are using HttpClient.PostAsJsonAsync to upload a Json File to a server. However in worst case scenarios this upload can take several hours. That's why just using HttpClient.Timeout is not working for us. This is an hard timeout and we need to have it huge.

So what do we do when the tcp connection is gone and the client does not detect that. With our huge timeout we are stuck for a long time. So is there any other Timeout we can use in such cases? Any other ideas or best practices? I was also looking into tcp sockets keep alive, but that doesn't seem to be an option.

Community
  • 1
  • 1
DanielG
  • 1,217
  • 1
  • 16
  • 37

1 Answers1

0

After some research, I finally found an article which describes the issue and provides a workaround: http://www.thomaslevesque.com/2014/01/14/tackling-timeout-issues-when-uploading-large-files-with-httpwebrequest/

According to this article, there is a design flaw in HttpWebRequest which I was able to reproduce. Seems ridiculous that the timeout also effects the upload.

However, I can live with the provided workaround (WebRequestExtensions) since our code is synchronous anyway.

DanielG
  • 1,217
  • 1
  • 16
  • 37