• Register
0 votes

Problem :

I am facing below listed very strange error. I am using Apache Server.

“413. that’s an error. your client issued a request that was too large. that’s all we know.”

How can I fix this error?

8 4 2
2,300 points

2 Answers

1 vote
Best answer

Solution :

I had faced this issue while I was using the Apache server.

If you are using Apache web servers then there is a very handy directive called LimitRequestBody. This directive will give you the functionality very similar to client_max_body_size by the use of it you will be able to easily restrict the size of the HTTP request. Your LimitRequestBody directive must be defined in either your http.conf file or you can define it in your .htaccess file. The default value for this magical directive in the Apache is 0, but you can set the value to whatever bytes you like to the value must be represented in the bytes.

E.g., if you are trying to restrict the requests which are larger than the 100MB then you must use as below.

LimitRequestBody 104857600

If you are satisfied by your changes then you can save your configuration file and simply reload your Apache using a following command: service apache2 reload.

This will fix your issue.

5 2 1
4,980 points
0 votes

This error occurs when a request is made from a client that is too large to be processed by the webserver. If your web server is setting a particular HTTP request size limit, clients may come across a 413 Request Entity too large response.


It is dependent upon the type of web server you are using that will determine which directives you need to configure. Whether you want to restrict users from uploading overly large files to your web server or want to increase the upload size limit.

Fixing this error:

Depending on the server you are using, implement the necessary changes to configure your web servers maximum HTTP request size allowance. By doing so, you can set the threshold file size for which the client is allowed to upload and if the limit is passed, then the above error occurs.


For nagix users, the directive that determines what the allowable HTTP request size can be is client_max_body_size. This directive already defines and if not you can add by an HTTP, server, or location block then define the value;

server {

    client_max_body_size 100M;




For the Apache web server, a similar directive is called LimitRequestBody. This provides the same functionality as client_max_body_size.

For Example:

If you wanted to restrict requests larger than 100MB then use the following;

LimitRequestBody 104857600


11 5 1
3,890 points

Related questions

0 votes
1 answer 149 views
Problem : I am having trouble with my website. It has been slowed down a little in last couple of days. I have carefully looked into my error log & found a lots of following logs: [Sat Nov 30 00:09:53 2019] [error] [client] Request ... core.c(3126): [client] redirected from r->uri = /images/2019/02/600x376_0.076827001313237200_pixnaz_ir_1.jpg How to solve this issue?
asked Nov 30, 2019 alecxe 7.5k points
0 votes
1 answer 140 views
Problem : I want to install the Xampp win32-1.8.2 on Windows 8.1. But I get below message saying " Because an activated user account User Account on your system some functions of XAMPP are possibly restricted." I have already tried to change my user account control settings but ... . And my APACHE does not start. I have also disabled the IIS but still, it is not at all working. What can I do?
asked Feb 4 jwilliam 3.9k points
1 vote
1 answer 60 views
Problem : I am very new to Azure. Recently I have started experiencing the error if I try to connect my database which is currently in the VM Role it is the SQL VM Role from the Azure Website. I am experiencing following issue: SqlException (0x80131904): A connection ... : 0 - The certificate chain was issued by an authority that is not trusted.)] Can someone kindly help me in fixing above error.
asked Apr 2 morrisBson 3.2k points
0 votes
1 answer 1.2K views
Problem : I had to remove a +CompatEnvVars from following : SSLOptions +FakeBasicAuth +ExportCertData +CompatEnvVars +StrictRequire As it said it was an invalid command or something. So having removed that and following a instructions to a nail it get below error: ... maximum permissible length. (Error code: ssl_error_rx_record_too_long) I am very new to SSL, any advice on what is going wrong?
asked Jan 17 jwilliam 3.9k points
0 votes
1 answer 54 views
Problem : I have got the legacy code issue that requires that I support the random urls as if they were requests for a home page. Some of the URLs have the characters in them that generate the below error "A potentially dangerous Request.Path value was detected from ... />     </system.web> <configuration> I have also Added a ValidateInput attribute to my action that should be catching the urls.
asked Jan 25 jwilliam 3.9k points