DMXzone Server Connect Support Product Page

Solved

maximum request length exceeded

Reported 19 Mar 2020 01:44:41
1
has this problem
19 Mar 2020 01:44:41 Steve Manatt posted:
Can't get files over 16k to upload. Getting the "maximum request length exceeded" error despite configuring the web.config file to be the following for the site:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.web>
<httpRuntime targetFramework="4.5" maxRequestLength="1048576" executionTimeout="3600" />
</system.web>
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="1048576000" />
</requestFiltering>
</security>
<directoryBrowse enabled="true" />
</system.webServer>
</configuration>

Exact Error: {"type":"Error","fileName":"dmxConnect.asp","errorNumber":-2147467259,"message":"maximum request length exceeded","stack":[]}

Any help. Running Windows Server 2019 - brand new install on AWS. I've read the default should be well above 600kb and it failed without the web.config file in place too.

The test file is HERE (dev.mydisc.info/files/anode.jpg)

Replies

Replied 22 Mar 2020 09:17:51
22 Mar 2020 09:17:51 Teodor Kuduschiev replied:
Hello Steve,
Please check the solution to this here: stackoverflow.com/questions/3853767/maximum-request-length-exceeded

Replied 23 Mar 2020 23:26:20
23 Mar 2020 23:26:20 Steve Manatt replied:
Doesn't my web.config file in the post look EXACTLY like the one in the article you mention? I've done this and it doesn't work. There's nothing more you can do to assist - no expertise you can offer beyond what the Internet says?
Replied 24 Mar 2020 09:20:36
24 Mar 2020 09:20:36 Teodor Kuduschiev replied:
Hello Steve,
The error is not related to any of our extensions. We don't set limits for any of the tools, all the limits are set in your server configuration.
Please contact your hosting support/server admins so they can check what's wrong with the limits and why the web.config changes you made don't make any difference.
Replied 03 Apr 2020 01:37:16
03 Apr 2020 01:37:16 Steve Manatt replied:
This was related to editing the ASP Limits Properties and none of the web.config items listed in the referred support article made any difference.

Reply to this topic