blocks|key|5712364|text|我也遇到了同样的问题，因为它是一个大结账，但没有权限延长服务器超时时间，所以通过执行以下命令解决了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5712365|$+svn+cleanup
$+svn+up|code-block|syntax|javascript|5712366|每次我都会收到这个错误(直到结账完成)。|5712367|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had the same issue and since it is a big checkout but don't have access to extend the server timeout, solved it by issuing:

<pre><code>$ svn cleanup
$ svn up
</code></pre>

Each time I got this error (until the checkout was complete).

blocks|key|5712406|text|这是与超时有关的apache服务器问题(SVN客户端不工作，因为它需要大量的大文件)。在httpd.conf上重启httpd，问题就解决了，以后不需要清理和更新：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5712407|Timeout+12000
KeepAlive+On
MaxKeepAliveRequests+100
KeepAliveTimeout+15|code-block|syntax|javascript|5712408|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is apache server problem related to timeout (SVN client dont work as it's needed with huge number of big files). Put here on httpd.conf and do a restart of httpd, and problem will be resolved, without future needs to do cleanup and update:

<pre><code>Timeout 12000
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 15
</code></pre>

blocks|key|2182765|text|这是我的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2182766|1-使用清理或sudo清理|2182767|svn+cleanup|code-block|syntax|javascript|2182768|2-使用update或sudo+update|2182769|svn+update|2182770|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

this is my solution:

1 - use cleanup or sudo cleanup

<pre><code>svn cleanup
</code></pre>

2- use update or sudo update

<pre><code>svn update
</code></pre>

blocks|key|4295145|text|尝试将http-timeout客户端参数设置为较大的值，如下所示：https://mail-archives.apache.org/mod_mbox/subversion-users/201410.mbox/%253CF98FEACF1869AF4497A996B6F32D22600A91CA@NHL-SVEX01.WSD.L-3Com.com%253E|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4295146|~/.subversion/servers：|4295147|[global]
http-timeout+=+6000|code-block|syntax|javascript|4295148|http://www.hostingezpublish.com/FAQ/Solving-checkout-problems-with-svn-repositories|4295149|entityMap|0|LINK|mutability|MUTABLE|url|https://mail-archives.apache.org/mod_mbox/subversion-users/201410.mbox/%253CF98FEACF1869AF4497A996B6F32D22600A91CA@NHL-SVEX01.WSD.L-3Com.com%253E|1^0|X|3X|0|0|0|0|0|2B|1|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|10|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|M|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]|U|$5|P|Q|R|C|$S|L]]]]

Try setting http-timeout client parameter to a large value as explained here:
<a href="https://mail-archives.apache.org/mod_mbox/subversion-users/201410.mbox/%3CF98FEACF1869AF4497A996B6F32D22600A91CA@NHL-SVEX01.WSD.L-3Com.com%3E" rel="nofollow noreferrer">https://mail-archives.apache.org/mod_mbox/subversion-users/201410.mbox/%3CF98FEACF1869AF4497A996B6F32D22600A91CA@NHL-SVEX01.WSD.L-3Com.com%3E</a>

~/.subversion/servers:

<pre><code>[global]
http-timeout = 6000
</code></pre>

<a href="http://www.hostingezpublish.com/FAQ/Solving-checkout-problems-with-svn-repositories" rel="nofollow noreferrer">http://www.hostingezpublish.com/FAQ/Solving-checkout-problems-with-svn-repositories</a>

blocks|key|4294963|text|HTTPSVN1.8包括一个新的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4294964|客户端库(Serf)。|blockquote|4294965|4294966|4294967|我认为这应该对此负责。我已经安装了TortoiseSVN-1.8.6.25419-x64-svn-1.8.8.msi，执行svn+merge时也出现了同样的错误。最初，我认为这是svn服务器超时的问题，但同样的合并操作也适用于1.6。所以我猜问题出在SVN版本1.8和更高版本上。请将您的svn客户端版本恢复到1.7或1.6，然后重试！|offset|length|style|CODE|BOLD|4294968|entityMap^0|0|0|0|0|H|15|1P|9|35|3|3W|S|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Q|8|@]|9|@]|A|$]]|$1|E|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|T|8|@$I|U|J|V|K|L]|$I|W|J|X|K|L]|$I|Y|J|Z|K|L]|$I|10|J|11|K|M]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|O|$]]

<blockquote>
 SVN 1.8 includes a new HTTP client library (Serf). 
</blockquote>

which I think is responsible for this. I had installed <code>TortoiseSVN-1.8.6.25419-x64-svn-1.8.8.msi</code> and performing <code>svn merge</code> gave same error. Initially I though it is problem with svn server timeouts but same merge operation worked with <code>1.6</code>. So I guess problem is with SVN version 1.8 and above. Please revert your svn client version to 1.7 or 1.6 and try!

blocks|key|2182696|text|出现此错误的原因是在服务器上打开其中一个内部SVN文件失败。这是服务器问题，但不是bug。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2182697|如果您的SVN服务器软件是Linux上的apache+WebDAV扩展：|offset|length|style|BOLD|2182698|您需要转到服务器上的位置，apache在此存储存储库数据库。使用sudo+chown+-R+www-data:www-data+folder_name更改文件夹所有者。客户端提交的问题将会消失。|CODE|2182699|这就是我所知道的关于这个错误的全部。|2182700|entityMap^0|0|0|10|0|W|17|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|S|8|@$D|T|E|U|F|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|V|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|N|$]]

Reason of this error is that opening one of internal SVN files on server fails. This is server issue, but not bug.

If your SVN server software is apache WebDAV extension on Linux:

You need to go to location on server, where apache stores the repository database. Use <code>sudo chown -R www-data:www-data folder_name</code> to change the folder owner. Problem with commits from clients will disappear.

That's all i know about this error.

blocks|key|1709165|text|当您通过svn+webdav提供代码时，在大签出或大合并期间可能会发生这种情况。通常，延长服务器超时时间会有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1709166|http://httpd.apache.org/docs/2.2/mod/core.html#timeout|offset|length|1709167|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1I|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

This can happen during big checkouts or big merges when you serve code via svn webdav. Usually extending server timeout will help.

<a href="http://httpd.apache.org/docs/2.2/mod/core.html#timeout" rel="nofollow">http://httpd.apache.org/docs/2.2/mod/core.html#timeout</a>

blocks|key|1711501|text|今天，我遇到了同样的问题，我使用SVN+1.9.9并通过SVN命令行从apache+SVN服务器收集了一些“diff”数据。来自'Kompjuteras‘的建议将apache配置参数设置为如下==以增加超时时间|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1711502|“超时12000|1711503|KeepAlive打开|1711504|MaxKeepAliveRequests+100|1711505|KeepAliveTimeout+15“|1711506|已经解决了这个问题(而不是超时12000，我将其设置为3600+==+1h)。此外，上面还有一个来自“Ethan+Field”的关于参数含义的问题。它们在这里有很好的解释：http://httpd.apache.org/docs/2.4/mod/directives.html|offset|length|1711507|我认为这里描述的问题是由在SVN+apache服务器上配置的太短的“超时”引起的。(从2.4版本开始，默认值仅为60+==+1分钟！)|1711508|祝你好运&非常感谢！|1711509|entityMap|0|LINK|mutability|MUTABLE|url|http://httpd.apache.org/docs/2.4/mod/directives.html^0|0|0|0|0|0|2E|1G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@$L|15|M|16|1|17]]|A|$]]|$1|N|3|O|5|6|7|18|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|19|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

today I have faced the same issue by using SVN 1.9.9 and gathering some 'diff' data by SVN command line from an apache SVN server. Well the suggestion from 'Kompjuteras' to set the apache configuration parameters as follows [== to increase especially the timeout]:

"Timeout 12000 
KeepAlive On 
MaxKeepAliveRequests 100 
KeepAliveTimeout 15" 

has solved the problem (instead of Timeout 12000 I have set it just to 3600 [== 1h]). Furthermore there was a question above from 'Ethan Field' about the meaning of the parameters. They are explained very well here: <a href="http://httpd.apache.org/docs/2.4/mod/directives.html" rel="nofollow noreferrer">http://httpd.apache.org/docs/2.4/mod/directives.html</a>

Well I think the issue described here is caused by a too short 'Timeout' configured at the SVN apache server. (Default is just 60 == 1MIN since version 2.4!!!!!)

Good luck &amp; Thanks a lot!

blocks|key|1711522|text|可能有点晚了，但是如果你正在疯狂地搜索这个问题，并且你的Subversion服务器最近更新到了Debian+Buster，你可能想在你的Apache的Subversion存储库vhost中试试这个选项：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1711523|SVNAllowBulkUpdates+prefer|code-block|syntax|javascript|1711524|将其放在SVNParentPath指令之后，执行sudo+service+apache2+reload，然后再次尝试结帐。|offset|length|style|CODE|1711525|来源：https://audeuro.com/node/44|1711526|此设置的作用(引用自subversion+manual)：|1711527|1711528|切换对更新样式报告请求的包罗万象响应的支持。Subversion客户端使用报告请求从mod_dav_svn获取有关目录树签出和更新的信息。它们可以请求服务器以两种方式之一发送该信息:在一个大规模响应中发送整个树的信息，或者使用skelta+(树增量的骨架表示)，它包含的信息恰好足以让客户端知道要向服务器请求哪些额外数据。当此指令包含值Off时，mod_dav_svn将仅使用skelta响应来响应这些报告请求，而不考虑客户端请求的响应类型。|blockquote|1711529|1711530|大多数人根本不需要使用这个指令。它主要为那些出于安全或审计原因希望强制Subversion客户端单独获取更新和签出所需的所有文件和目录的管理员而存在，从而在Apache的日志中留下GET和PROPFIND请求的审计跟踪。此指令的默认值为On。|1711531|1711532|这听起来有点过时。我怀疑，如果您有一个相当大的存储库，那么一个包罗万象的报告的大小对于传输来说可能太大了，所以“大多数人根本不需要使用这个指令”的评论不再适用。|1711533|entityMap|0|LINK|mutability|MUTABLE|url|https://audeuro.com/node/44|1|http://svnbook.red-bean.com/en/1.7/svn.ref.mod_dav_svn.conf.html^0|0|0|4|D|O|R|0|3|R|0|0|A|H|1|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1C|8|@$I|1D|J|1E|K|L]|$I|1F|J|1G|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1H|8|@]|9|@$I|1I|J|1J|1|1K]]|A|$]]|$1|O|3|P|5|6|7|1L|8|@]|9|@$I|1M|J|1N|1|1O]]|A|$]]|$1|Q|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|R|3|S|5|T|7|1Q|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1S|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1U|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]|18|$5|13|14|15|A|$16|19]]]]

Possibly a bit late but if you're frantically Googling this problem and your Subversion server has recently updated to Debian Buster you may want to try your luck with this option in your Apache's Subversion repository vhost:

<pre><code>SVNAllowBulkUpdates prefer
</code></pre>

Put that after the <code>SVNParentPath</code> directive, do <code>sudo service apache2 reload</code>, and try a checkout again.

Source: <a href="https://audeuro.com/node/44" rel="nofollow noreferrer">https://audeuro.com/node/44</a>

What this setting does (quoting from the <a href="http://svnbook.red-bean.com/en/1.7/svn.ref.mod_dav_svn.conf.html" rel="nofollow noreferrer">subversion manual</a>):

<blockquote>
 Toggles support for all-inclusive responses to update-style REPORT
 requests. Subversion clients use REPORT requests to get information
 about directory tree checkouts and updates from mod_dav_svn. They can
 ask the server to send that information in one of two ways: with the
 entirety of the tree's information in one massive response, or with a
 skelta (a skeletal representation of a tree delta) which contains just
 enough information for the client to know what additional data to
 request from the server. When this directive is included with a value
 of Off, mod_dav_svn will only ever respond to these REPORT requests
 with skelta responses, regardless of the type of responses requested
 by the client.
 
 Most folks won't need to use this directive at all. It primarily
 exists for administrators who wish—for security or auditing reasons—to
 force Subversion clients to fetch individually all the files and
 directories needed for updates and checkouts, thus leaving an audit
 trail of GET and PROPFIND requests in Apache's logs. The default value
 of this directive is On.
</blockquote>

This sounds a bit out of date. I suspect that if you have a fairly large repository the size of an all-inclusive report may simply be too large for transit, so the "most folks won't need to use this directive at all" comment no longer applies.

blocks|key|2182901|text|在我的情况下，这是由SVN服务器和我的工作站之间的某种“透明”基础设施造成的。我怀疑它是一个代理(websense+/+mcafee+/+forcepoint)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2182902|大多数提交都是正常的，但它无法流式传输一个特别大的提交的内容，可能是内容太大，导致代理崩溃/丢弃连接。|2182903|我能够通过绕过这个基础设施来解决这个问题。在我的例子中，我能够在我的.git/config中设置一个替代代理，它可以绕过有问题的基础设施。|2182904|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In my situation this was being caused by some "transparent" infrastructure between the SVN server and my workstation. I suspect it was a proxy (websense / mcafee / forcepoint).

Most of the commits were fine, but it was failing to stream the content of one particularly large commit, presumably the content was too large and was causing the proxy to crash / drop the connection.

I was able to resolve by bypassing this infrastructure. In my case, i was able to set an alternative proxy in my .git/config which bypasses the problematic infra.

blocks|key|2182618|text|您没有写入您的SVN服务器的版本。当您将客户端降级到1.7时，您的问题可能会得到解决-由于1.8和1.7版本之间的不兼容，您将不得不删除本地存储库并再次同步它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2182619|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You did not write what version is your SVN server. Probably your issue will be solved when you downgrade your client to 1.7 - you will have to delete the local repository and synchronize it again because of incompatibility between versions 1.8 and 1.7.

I am using svn 1.8.9 and while checking out trunk code I am getting following error

svn: E120106: ra_serf: The server sent a truncated HTTP response body.

Because of above error I am not able to check out entire trunk code. Please suggest approach for resolving this. 

Thanks

Why do I get “svn: E120106: ra_serf: The server sent a truncated HTTP response body” error?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在使用svn 1.8.9，在检查主干代码时，我得到了以下错误svn: E120106: ra_serf:服务器发送截断的HTTP响应正文。由于上面的错误，我不能检出整个主干代码。请建议解决此问题的方法。谢谢

问为什么会出现“svn: E120106: ra_serf:服务器发送了截断的HTTP响应正文”错误？
EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么会出现“svn: E120106: ra_serf:服务器发送了截断的HTTP响应正文”错误？EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么会出现“svn: E120106: ra_serf:服务器发送了截断的HTTP响应正文”错误？
EN