> > > I was hoping someone had experimented with some Apache options to limit
> > > transaction size. (Yet another thing on my todo list that I hope
> someone
> > > else has more experience with...) Possibly something like
> > > LimitRequestBody 4194304 ????
> > >
> >
> > In that scenario, consider that Subversion only transfers differences
> > across the wire. So how would you handle a situation where a user
> > commits at 2MB file, then appends 3MB to it and commits that? Their
> > individual commits were both under 4MB, but the resulting file is now
> > 5MB.
> >
>
> I am using https and dav module and I am OK with the drawbacks of this
> solution. Limiting only the amount an user commits at one time is OK.
>
> I added
> LimitRequestBody 4194304
> in various places in my apache2.conf (server config, virtual host,
> location), but none of them seem to make a difference when I upload a file
> of 5Mb.
The request body is likely smaller than 4 MB when you commit a
compressable file of 5 MB. Try committing a file of 10, 15 or even
20MB when the request body is set to 4MB: Subversion compresses files
it sends to the repository.
> I also tried the use the XML version of the argument, that is
> LimitXMLRequestBody
> but the results are the same.
>
> If I lower the limit, things start to happen. I get a "413 Request Entity
> Too Large" error when I use:
> LimitRequestBody 437
> LimitXMLRequestBody 437
That would mean an extreme compression rate. Did you try to commit
something which compresses badly, like a TIFF or JPG file?
> Anything higher that that will work just fine. One thing to notice is that
> I use https.
>
> I appreciate any suggestions on how to track this down.
HTH,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-12 08:16:42 CEST