We welcome user feedback and feature requests!

Allow a request timeout of more then 3.8 minutes

Currently the infrastructure imposes a request timeout of 3.8 minutes. This is rather low for longer lasting requests such as for making reports.

23 votes
Vote
Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
You have left! (?) (thinking…)
Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

4 comments

Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
Submitting...
  • You don't know me commented  ·   ·  Flag as inappropriate

    Using Web App for Containers to run a containerized Third-Party application. We don't have any possibility to adapt the implementation of anything. Here it is really hurting us that we can't change the request timeout because when initially setting up the application it takes round about 5-10 minutes for it to complete. Azure should really add an option for the user to adapt request timeout instead of patronizing its users.

  • Anonymous commented  ·   ·  Flag as inappropriate

    As mentioned by the previous commenters, this value should be configurable by the application or development team. As an application gateway, it's important for this value to be flexible as it directly impacts the business logic and capability of an application.

    On production web servers such as Nginx, Apache, and even IIS, this is a configurable value. There's no reason to expect otherwise on the App Service.

  • Trevor commented  ·   ·  Flag as inappropriate

    It may be the default, and it may be undesirable in general to have an operation that lasts more than 3.8 minutes, but for many situations, having a long-running operation is inevitable and having the flexibility to extend the timeout is incredibly desirable. Oh, and locking the vote button so us customers can show you how much we want this feature, (and how wrong you are for making it non-configurable) is very unprofessional.

Feedback and Knowledge Base