What causes svn 413 error. Request an entity too large?

Question

Sometimes I get the error "413 Request Entity Too Large" when updating the svn repository. As soon as I get this error, it continues every time I try to update a local working copy. A new check will solve the problem, but it is very inconvenient. The project is over 30 GB and the SVN repository is hosted externally.

This has happened in the past on several different computers, including the Windows development machines and our Linux build server.

Most of what I found on this issue is related to large individual files (over 2 GB). This is not the point here, since the largest files are approx. 50-60 MB.

Has anyone else come across this before and / or knew a reason / solution?

Answer 1

Try adding the following configuration directives to your Apache configuration file:

LimitXMLRequestBody 8000000 LimitRequestBody 0 

Answer 2

I do not have access to my repo server (IT Managed and its on the weekend). So, I found that I could work around this problem by updating svn on subdirs until you work. Then I went down to this directory until I stopped getting error 413. Then I could do the update at higher levels. May not work for everyone, but may help get through emergency assistance.

Answer 3

I had this problem recently with any file over 10 MB. Turns out I forgot that the svn / apache proxy is with nginx. Changing client_max_body_size in nginx.conf fixed the problem. I left LimitXMLRequestBody and LimitRequestBody on the Apache server by default.

Answer 4

Made a short bash script to scroll through the subdirectories, for each mdh answer:

 for dir in *; do [[ -e $dir ]] || continue echo "Updating $dir" svn up $dir done svn up 

Answer 5

Also, if you run mod_security, try checking the SecRequestBodyLimit setting. The shaft was set too low and caused a problem.

Answer 6

See also: RequestReadTimeout, which limits reading time for headers and body http://httpd.apache.org/docs/2.2/mod/mod_reqtimeout.html