# Unexpected HTTP status 413 'Request Entity Too Large'

**URL:** <https://community.cloudogu.com/t/unexpected-http-status-413-request-entity-too-large/1314>\
**Category:** SCM-Manager (General)\
**Created:** [April 17, 2024, 5:00pm UTC](https://community.cloudogu.com/t/unexpected-http-status-413-request-entity-too-large/1314 "2024-04-17T17:00:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pierre](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/pierre/32/1394_2.png) [@pierre](https://community.cloudogu.com/u/pierre)\
**Post date:** [April 17, 2024, 5:00pm UTC](https://community.cloudogu.com/t/unexpected-http-status-413-request-entity-too-large/1314/1 "2024-04-17T17:00:19Z")

</div>

Hello,

I’m currently facing the following issue when I try to commit a large file with SVN:

```auto
svn: E175002: Unexpected HTTP status 413 'Request Entity Too Large' on '/scm/repo/scmadmin/test_repo/!svn/wrk/48e33bad-9bdb-4839-8de9-1c542c51c254/temp_232457158_file'
svn: E175002: Your commit message was left in a temporary file:
svn: E175002: '/Users/<path>/test_repo/svn-commit.tmp'

```

Based on my understanding, the solution would be to update `LimitXMLRequestBody` and `LimitRequestBody` parameters into Apache configuration file. However I don’t really get how I can override those parameters 😕  
If I got it right, I should update/add something into `server-config.xml`, but I don’t know what. Any help?

I’m running the docker version of SCM (`scmmanager/scm-manager:2.46.0`).

Thanks!

---

<div class="post-metadata">

**Author:** ![christoph.loose](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/christoph.loose/32/1400_2.png) [@christoph.loose](https://community.cloudogu.com/u/christoph.loose)\
**Post date:** [April 22, 2024, 1:10pm UTC](https://community.cloudogu.com/t/unexpected-http-status-413-request-entity-too-large/1314/2 "2024-04-22T13:10:44Z")

</div>

Hi @pierre

could you please check this issue? [Can't push big files · Issue #691 · scm-manager/scm-manager · GitHub](https://github.com/scm-manager/scm-manager/issues/691)  
Your resported issue is probably similar?
