Skip to main content

Error: HTTPS 413: The page was not displayed because the request entity is too large.

Users will encounter a problem of 'HTTPS 413: The page was not displayed because the request entity is too large'. If we implement https (secured socket layer) in our website, this will cause the error to occur mainly because of two reasons:

1. Data is transmitted every time whenever the re-negotiation occurs between client and server.
2. Files uploaded by the users are of large size.

The problem is because of the SSL. Whenever we implement SSL on the web site, every time the client re-negotiates with the server, data is sent again and again, which exceeds the limit of the uploadreadaheadSize, a variable to handle the data sent in the post back or reloading of the pages. In order to avoid the problem, the following command can be given at the command prompt:

cscript adsutil.vbs set w3svc/3/uploadreadaheadsize 204800
(where the last 204800 is the size in bytes which we want. The default size is 48 KB. Also 3 is the index of the website to which we want to apply. We can check the index of websites from applicationhost.config file)

And after that just restart the web site and the problem is resolved.

I hope this will help users.

Comments

Lakhwinder Ghuman said…
Very meaningful & knowledgeable post...
October 11, 2010 at 9:11 PM
Unknown said…
sir ji, why restart, we have something called reload in Linux and that will re read all the configuration files in apache.Site will never go down even for single minute.hehe ;)

=Deep
December 18, 2010 at 4:07 PM
Post a Comment

Popular posts from this blog

Connecting Nodejs to SQL Server with Knex ORM - Part 1

Normally we connect Nodejs to the databases like SQLite, MongoDB, Postgres etc . In this multiple part post, I am going to show you, how we can connect Nodejs with Microsoft's SQL Server using Knex and run CRUD operations. 1. Installation of required packages In order to connect Nodejs to SQL Server with Knex, we will need following node packages installation: i. npm install knex ii. npm install mssql Once the packages are installed, we can write the following code to connect: //Code to KNEX connection settings. var knex = require('knex')({ client: 'mssql', connection: { user: 'sa', password: 'pwd', server: 'localhost', database: 'Test' } }); //Code to query the Table DEPT knex.select("*").from("dept") .then(function (depts){ depts.forEach((dept)=>{ //use of Arrow Function console.log({...dept}); }); }).catch(function(err) { ...
Post a Comment
Read more

SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

If we encounter this error "SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)" in SQL Server in which the job fails because of the user account related problem, then we need to take the following steps to make it work: a. Go to SQL Server Agent. b. Then select the job which is giving error and not running successfully. c. Then choose properties and in the General Tab, change the owner to "SA" or any account that has the administrative privileges. The problem will be resolved.
1 comment
Read more

MAX pool size reached in ASP.NET

If you are handling large databases and big application(s) that are running on servers in a cluster, then probably this error might have occurred. In an ASP.NET app, we can use connection pooling that helps to share the connection between multiple request(s) rather than creating more connections. The settings relating to connection pool are defined in web.config file. Max pool size reached error in ASP.NET occurs, when the number of connections go beyond the maximum defined limit in Web.config file. Following are the various settings of the Connection Pooling: Name Default Description Connection Lifetime 0 When a connection is returned to the pool, its creation time is compared with the current time, and the connection is destroyed if that time span (in seconds) exceeds the value specified by  Connection Lifetime . This is useful in clustered configurations to force load balancing between a runnin...
Post a Comment
Read more