HowTo - Handle '413. Request Entity Too Large' error in installations with SSL/HTTPS setup

HowTo - Handle '413. Request Entity Too Large' error in installations with SSL/HTTPS setup

This error may occur in certain installations with SSL / HTTPS setup, in cases when clients send significant amount of data to server, more than the default limit of 49'152 bytes in IIS.

That is because the entire request entity body must be preloaded during negotiation and, additionally, SSL will use the value of the UploadReadAheadSize metabase property to validate the request size.

Solution

UploadReadAheadSize value of IIS must be increased to a higher limit (we recommend ~4Mb). You can run the following command with ADMIN rights:

C:\Windows\System32\inetsrv\appcmd.exe set config "Default Web Site/BACore" -section:system.webServer/serverRuntime /uploadReadAheadSize:"4915200"  /commit:apphost

IIS screenshot to verify if the value is increased:


    • Related Articles

    • HowTo - Handle 'Soap http error - Cannot connect to host'

      BioManager may report " Soap http error - Cannot connect to host" after installation/upgrade. This is an error indicating that BioManager application cannot connect successfully to the Core web services. It can happen due to couple of reasons: either ...

    • FAQ - WebEdition server installation troubleshooting

      Question What are the most frequent problems when installing WebEdition server, and how can I solve them? Answer Installing all WebEdition server components is not a click-and-go experience. It requires several installation steps and skipping or ...

    • HowTo - Handle 'Processing...' error

      BioManager may report 'Processing...' error endlessly after installation/upgrade. This is a generic error indicating an internal component was not installed or configured properly. No standard solution can be given, hence more information is required ...

    • HowTo - Handle 'Database operation error' issues

      The Database operation error issue is one of the most common problems detected after a WebEdition installation. It is a general error which is basically saying that connection to the database server (default, SQL Server) could not be established. ...

    • HowTo - Handle 'Access denied' error with WebEdition R10

      To increase system security, from WebEdition version R10 web service authentication is enabled by default. This leads to problems with integrations that do not support security token on web service interface and results in 'Access denied' error. ...