0

I have created a web api, with asp.net "Inidividual User Accounts" authentication. It is working fine on my local host and I am able register with the registration endpoint.

http://localhost/api/Account/Register

But the same web-api when deployed to azure(as cloud service) is timing out, and I get the below response.

Abort / timeout

The request has been aborted manually or because of the connection timeout. There were no response from the server but the connection wasn't closed.

You can adjust timeout in settings.

Try to:

add "Connection: close" header which should be used by the server to close the connection after it finish generating response

What could be the issue, and how can I increase the timeout.

KhanS
  • 1,167
  • 2
  • 12
  • 27
  • if not already do check these posts http://stackoverflow.com/questions/24403832/timeout-a-web-api-request http://stackoverflow.com/questions/23630984/configure-request-timeout-for-webapi-controllers – Aravind Jul 25 '16 at 06:21

2 Answers2

0

I figure it out myself. I had to increase the timeout in the web.config as below

<httpRuntime targetFramework="4.5" executionTimeout="3600" />
KhanS
  • 1,167
  • 2
  • 12
  • 27
0

I had the same issue occuring while using ARC (Advanced Rest Client) Chrome plugin. The answer for me was to toggle on the 'Use XHR' button on. see https://marcustalcott.com/2016/11/03/error-making-a-rest-call/?iframe=true&theme_preview=true

Marcus Talcott
  • 321
  • 2
  • 4