Increase max response body size for SVN+HTTP requests?

OrangyTang

I am infrequently seeing 413 / Request Entity Too Large when doing requests to our svn repository. This seems to be a problem when there's a lot of file changes and goes over some internal Apache limit (manually splitting up the requests into several smaller requests does fix things temporarily).

Some googling suggests I need to add some Apache directives to raise the limits, eg:

LimitXMLRequestBody 8000000
LimitRequestBody 0

However after adding an .htaccess file with this in, I'm not seeing any difference. My guess is either I've put it in the wrong place (currently next to the passwd and authz files) or there's something I need to do to get Apache to reload the configuration it uses.

Any suggestions appreciated, thanks.

nick

OrangyTang Hello, as far as I can see, those directives will not function in a .htaccess file and need to be applied directly to the Apache configuration httpd.conf file. This is not usually done on shared servers. Aside from setting up your own Apache instance for your site that would give you access to your own httpd.conf file to edit as you see fit, maybe you could either break up larger commits or if your SVN client supports it, use chunked uploads.

OrangyTang

nick Thanks for the info.

Annoyingly, it's not actually commits that are too large - it's actually the update operation. So if I have a user that doesn't update for a while, the list of changed files gets too big and the whole update bails.

I'm not particularly keen on migrating to our own apache instance right now, but I am going to investigate if I can use the svn+ssh protocol as an alternative.

nick

OrangyTang I forgot to mention that our NGINX frontend proxy is also probably a contributing factor for this. We generally recommend svn+ssh by default, so that is a good plan forward.

NOTE: if your SVN client supports ra_serf you can try enabling http-chunked-requests to see if that improves things.