ASP.NET MVC and httpRuntime executionTimeout

Question

I would like to increase the httpRuntime executionTimeout for a subsection of an ASP.NET MVC application.

In a regular Web App, you could use:

<configuration>
  <location path="UploadPage.aspx">
    <httpRuntime executionTimeout="600"/>
  </location>
</configuration>

However there really is not the idea of "Folders" in ASP.NET MVC, so how would I go about doing this?

Lets assume the ASP.NET MVC path is /Images/Upload with an ImagesController and Upload Action.

i tried this solution and it work fine stackoverflow.com/questions/76474157/… — Giacinto Bruno
– Giacinto Bruno, Commented Jun 15, 2023 at 9:01
i tried this solution and it work fine stackoverflow.com/questions/76474157/… — Giacinto Bruno
– Giacinto Bruno, Commented Jun 15, 2023 at 9:02

Chris Hynes · Accepted Answer · 2009-03-11 22:19:34Z

52

You can include the whole MVC path (controller and action) in the <location> tag's path attribute. Something like this should work:

<location path="Images/Upload">
    <system.web>
        <httpRuntime executionTimeout="600" />
    </system.web>
</location>

answered Mar 11, 2009 at 22:19

Chris Hynes

10.3k2 gold badges47 silver badges55 bronze badges

Sign up to request clarification or add additional context in comments.

8 Comments

E Rolnicki Over a year ago

I'm still having issues making this work... for clarification: the path is relative to the root of the site, or the app? Also, if there are any values being passed in the url would this fail? (ex: Images/Upload/1)

Chris Hynes Over a year ago

It's relative to the root of the site, but I think you may be out of luck with the additional values on the url. ASP.NET interprets the path strictly and doesn't allow wildcards. 2 ideas: (a) Use QueryString.

Chris Hynes Over a year ago

(b) Create an actual Images/Upload folder, and put a web.config inside it. Set path="" to apply to the whole folder. Not sure if ASP.NET will interpret this correctly for MVC apps, but it definitely works for normal ASP.NET apps.

Nick van Esch Over a year ago

please note this is ignored completed if debug mode is on msdn.microsoft.com/en-us/library/vstudio/… executionTimeout Optional Int32 attribute. Specifies the maximum number of seconds that a request is allowed to execute before being automatically shut down by ASP.NET. This time-out applies only if the debug attribute in the compilation element is False. Therefore, if the debug attribute is True, you do not have to set this attribute to a large value in order to avoid application shutdown while you are debugging.

Chris Hynes Over a year ago

Good point. This is a big gotcha because everything works fine in debug mode. Then you go to deploy and it blows up for an unknown reason with poor error messaging.

|

Community · Accepted Answer · 2017-05-23 12:32:11Z

8

Chris Hynes solution works! Just be sure to not include ~/ in your path.

This answer details another way - simply set the ScriptTimeout within your action code:

public ActionResult NoTimeout()
{
    HttpContext.Server.ScriptTimeout = 60 * 10; // Ten minutes..
    System.Threading.Thread.Sleep(1000 * 60 * 5); // Five minutes..
    return Content("NoTimeout complete", "text/plain"); // This will return..
}

edited May 23, 2017 at 12:32

CommunityBot

11 silver badge

answered Mar 14, 2009 at 5:33

Jarrod Dixon

15.8k9 gold badges62 silver badges72 bronze badges

4 Comments

Jeff Atwood Over a year ago

I don't think the Server.ScriptTimeout way works. I distinctly remember trying that and not getting it to work.

Jarrod Dixon Over a year ago

Ah, it was what was checked into our test tier and working before moving back to the web.config version, boss :)

Jarrod Dixon Over a year ago

It seems that when using ~/, ASP.NET maps it to a physical path. This doesn't happen when using "controller/action"; it's mapped from the app root. Yeah, don't ask me why - I even dug into Reflector to try and figure it out, but it's a pain following config stuff.

Johnny Oshika Over a year ago

This technique doesn't work for me. I need to set the executionTimeout in web.config instead.

KevinUK · Accepted Answer · 2009-06-16 12:48:05Z

1

If the action is in the default controller then home/upload does not work, you just put the action name.

edited Jun 16, 2009 at 12:48

answered Apr 20, 2009 at 20:00

KevinUK

5,1735 gold badges35 silver badges51 bronze badges

Comments

jeroen.verhoest · Accepted Answer · 2011-12-15 08:25:02Z

1

Take a look a AsyncController, if you use this, you will have the possibility to set a AsyncTimeout attribute on an action method, so you will be able to timeout a request.

Links that helped me: http://forums.asp.net/p/1564303/3922462.aspx http://dariosantarelli.wordpress.com/2010/10/16/asp-net-mvc-2-handling-timeouts-in-asynchronous-controllers/

answered Dec 15, 2011 at 8:25

jeroen.verhoest

5,1933 gold badges29 silver badges27 bronze badges

2 Comments

Erik Philips Over a year ago

This won't Increase the timeout as the OP wanted. The runtime will timeout before the async timeout happens.

Chris Nevill Over a year ago

Now a broken link

oglester · Accepted Answer · 2012-07-19 13:37:31Z

1

I notice that you are specifically trying to increase the timeout on an upload page. I have had some success with a "chunking" uploader called plupload. A relatively simple MVC actions can be setup to receive the upload's chunks, appending each chunk as it is received. With the small chunks, you will not need to increase the timeout. Of course there might be some browser limitations, but n

http://plupload.com/

answered Jul 19, 2012 at 13:37

oglester

6,6378 gold badges45 silver badges65 bronze badges

Collectives™ on Stack Overflow

ASP.NET MVC and httpRuntime executionTimeout

5 Answers 5

8 Comments

4 Comments

Comments

2 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

8 Comments

4 Comments

Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related