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

How to use QueryExtenderControl in ASP.NET with LINQ

Queryextender control is a control that helps in doing actions like filtration, searching, sorting etc. on the LINQ Data source with few steps. In fact we don’t have to write any code with this. Screenshot given below is just an example that can easily be achieved through this control. In the above screenshot, we can see that there is a GridView Control that has been binded to a LINQData Source Control. And we have a DropDownlistBox that is also binded to another LINQData Source Control and displaying only grouped jobs. The GridView display all the employees who are matching the Job Parameter. This is done through QueryExtender Control. Also we can search for any name in the employee name's through Query Extender control. The code in the HTML goes like: < form id ="form1" runat ="server">     < div >         Select Job: < asp : DropDownList ID ="Job" runat ="server" DataSourceID ="LinqDataSource2...
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

How to Delete Record through Knex.

This post is all about of deleting records through KNEX ORM in Nodejs. The following code shows how to achieve this: knex("depts").where("deptno","50").del() .then(function (count) {     console.log(count); }) .finally(function () {     knex.destroy(); }); The above code deletes a record from a table "Depts" where Deptno = 50. It has a "then" Promise attached that will show how many records were deleted with this command. Also "finally" is the method that will always execute and will close the KNEX connection. Happy Coding !!!
Post a Comment
Read more