title: Azure VM 408 Request Timeout when making large http requests
body: <p>I’m currently building an app using Azure Linux VMs with .Net Core and I’m facing an issue when sending http requests from an Azure VM to a remote server.</p>
  
  <p>When making a http request from an Azure Linux OR Windows VM (CURL and .NET Core) to a remote server (Debian Linux NOT in Azure) the request fails with 408 Request Timeout and the message “Server timeout waiting for the HTTP request from the client.”. When executing this same request locally using CURL, Postman or from .Net Core it succeeds. This requests also works fine when executed within a Linux VM in AWS and GCP. It even works in Azure Functions…</p>
  
  <p>Here is my test setup:</p>
  
  <p><strong>Request 1 (Small)</strong></p>
  
  <p>HTTP Post with a request body that has a content length of 306<br>
  Average response time is 4s on my local machine with a response size of 20mb</p>
  
  <p><strong>Request 2 (Large)</strong></p>
  
  <p>HTTP Post with a request body that has a content length of 5962<br>
  Average response time is 5s on my local machine with a response size of 14mb</p>
  
  <p>Locally both requests work fine.<br>
  In AWS and GCP Linux VMs both request work fine.<br>
  In Azure Linux VM (Standard B2s) the small consistently works and the large one consistently fails with 408<br>
  In Azure Windows VM (Standard DS1 v2) both consistently fail with 408<br>
  In Azure Functions both consistently work</p>
  
  <p>All test machines as well as the remote endpoint that gets called are located in Europe.</p>
  
  <p>This is why I currently suspect there must be something going on (or a misconfiguration on my side) in Azure VM or Azure Networking that causes this behavior. I already tried raising the Timeout of my HttpRequest in .Net Core without success (as expected as it also fails in CURL using SSH).</p>
  
  <p>Is there anyone that can help me work around this or point me towards documentation? Is this a known issue?</p>