• Register
0 votes
1.9k views

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

Please log in or register to answer this question.

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.

Dependency:

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.

Nagix:

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;

    ...

}

Apache:

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 2
3,890 points

Related questions

0 votes
1 answer 36 views
36 views
Problem: I am facing below listed very strange error: “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?
asked Mar 14 Wafa Abu Yousef 6.1k points
0 votes
1 answer 7 views
7 views
Problem: Please assist me in resolving this issue: 400. that’s an error.your client has issued a malformed or illegal request. that’s all we know
asked Apr 5 tuhin1 48.9k points
0 votes
1 answer 2 views
2 views
Problem: How to fix this error > Your client has issued a malformed or illegal request. that’s all we know.
asked 3 days ago ummeshani 8.8k points
0 votes
1 answer 3 views
3 views
Problem: I have a function which returns the coordinates of an address using CURL and the Google Maps API.The code works fine for me and 99% of the web servers I use it on - but for around 1% of servers Google returns the error message. Can anyone think of any other things which could be causing Google to return this message?
asked 4 days ago Moumita Bhowmick 12.4k points
0 votes
1 answer 4 views
4 views
Problem: I've implemented Google SignIn on my React Native app using react-native-firebase and react-native-google-signin. It's working as it should on iOS Simulator on my MacBook. However, when I submitted to the AppStore, the Apple Review Team rejected it saying that the ... bug. It logs in perfectly fine on my device. Any idea on what's causing the issue on the Apple Review team's device?
asked Apr 25 sumaiya simi 43.9k points
0 votes
1 answer 7 views
7 views
Problem: google_cloud_run_service.skills-online: Creating... Error: Error creating Service: googleapi: got HTTP response code 404 with body: <title>Error 404 (Not Found)!!1</title> <style> *{margin:0;padding:0}html,code{font:15px/22px arial,sans- ... traffic { percent = 100 latest_revision = true } } terraform.tf file Affected Resource(s) google_cloud_run_service Debug Output file gist.github.co
asked Apr 25 sumaiya simi 43.9k points
0 votes
1 answer 13 views
13 views
Problem: I've implemented Google SignIn on my React Native app using react-native-firebase and react-native-google-signin. It's working as it should on iOS Simulator on my MacBook. However, when I submitted to the AppStore, the Apple Review Team rejected it saying that the ... bug. It logs in perfectly fine on my device. Any idea on what's causing the issue on the Apple Review team's device?
asked Apr 24 anika11 32k points
0 votes
1 answer 5 views
5 views
Problem: What are my options for dealing with this issue? 404. that&rsquo;s an error. the requested url was not found on this server. that&rsquo;s all we know.
asked Apr 7 rakib1 51.5k points
1 vote
1 answer 3 views
3 views
Problem: How to remove this error? The requested URL / was not found on this server. that&rsquo;s all we know.
asked Mar 30 PkGuy 23.5k points
0 votes
0 answers 2 views
2 views
Problem: Although I am by no means an expert on Ubuntu, I have had two servers running for a couple of years with no problems. Last night, when attempting to access a local website on one of them I got the error: **Bad Request** Your browser sent a ... Request error was encountered while trying to use an ErrorDocument to handle the request.I'm about out of ideas, and looking for any suggestions.
asked 4 days ago Moumita Bhowmick 12.4k points