Are there any dangers in increasing the execution of the Timeout and maxRequestLength of an ASP.NET site?

I have a user who is trying to upload a 150 megabyte file using an ASP.NET site. They get an HttpException:

System.Web.HttpException: Maximum request length exceeded.

I believe that I can solve this problem by increasing the execution of Timeout to 300 seconds (5 minutes) and maxRequestLength to 204800 kilobytes (200 megabytes). But are there any potential negative consequences or dangers from this?

+4
source share
1 answer

I would recommend setting only those large values โ€‹โ€‹of the page that they need, and not the site as a whole; both can be set programmatically for the page. Otherwise, I do not see a problem with increased latency and file size. You should probably include a warning that loading may take up to 5 minutes so that users do not click buttons (i.e. ajax progress bar).

System.Web.Configuration.HttpRuntimeSection.MaxRequestLength and Server.ScriptTimeout

+4
source

Source: https://habr.com/ru/post/1343309/


All Articles