The executionTimeout is measured in seconds and defaults to 110 seconds. The figure you mention seems rather large to me as do you really want someone (or a process) to wait that long before being told it has failed.
As for best practice... personally I would stick to the default unless you know you have so long running process occurring on your site which you would expect to take longer than the 110
maxRequestLength and executionTimeout in web.config
Hi,
I want to understand what best practice values should be for maxRequestLength and executionTimeout.
Someone mentioned maxRequestLength="204800" executionTimeout="99999".
But what are there data values measured in?
I assume you would not want to set the limit to large?
What is the advice here?
Thanks a lot!
The executionTimeout is measured in seconds and defaults to 110 seconds. The figure you mention seems rather large to me as do you really want someone (or a process) to wait that long before being told it has failed.
As for best practice... personally I would stick to the default unless you know you have so long running process occurring on your site which you would expect to take longer than the 110
As for maxRequestLength the default is 4mb ( defined as 4096).
It all depends if your site is uploading files etc. If you expect to receive uploads > 4mb you will need to scale this figure accordingly
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.