Menu
On occasion I receive an error "413 Request Entity Too Large" while updating an svn repository. Once I receive this error, it continues every time I attempt to update the local working copy. A new checkout will solve the problem, but is very inconvenient. The project is over 30 GB, and the SVN repository is hosted externally.
This has occurred in the past on several different computers, including Windows development machines, and our Linux build server.
Most of what I have found regarding this issue relates to large individual files (over 2GB). This is not the case here, as the largest files are approx. 50-60 MB.
Has anyone else ran into this before and/or know the cause/solution to this?
276
The HTTP 413 Payload Too Large response status code indicates that the request entity is larger than limits defined by server; the server might close the connection or return a Retry-After header field.
Occasionally when navigating your account, you might see an error message that reads "Request Entity Too Large." When this happens, it means that your Constant Contact cookies have built up and need to be cleared.
The HTTP error 413 in Google Chrome occurs due to incorrect server configuration or browser issue. Clearing your browsing data is a great way to fix to fix this issue. In some instances, you can solve this problem by resetting your network configuration.
Try to add the following configuration directives to your Apache configuration file:
LimitXMLRequestBody 8000000 LimitRequestBody 0 I don't have access to my repo server (IT Managed, and its over the weekend). So what I found was that I could work around this issue by doing an svn update on subdirs until one wouldn't work. Then I descended into this dir until I stopped getting the 413 error. Then I could do an update at higher levels. Might not work for everyone but could help get through in an emergency
21
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
