颠覆E160013：'！/ SVN / XXX / SVN /我“找不到路径*错误 [英] Subversion E160013: '/svn/xxx/!svn/me' path not found* error
问题描述
我最近在我们的服务器和重新配置后升级 bitnami TRAC栈（从0.12.2-5至0.12.3）所有的脚本和存储库都显得很好。我能够登录并查看源$ C $ c和使用浏览存储库 Trac的。我测试检查出来的源$ C $ C，我可以同时通过的VisualSVN和乌龟浏览存储库。
I recently upgraded the bitnami trac stack (from 0.12.2-5 to 0.12.3) on our server and after reconfiguring all the scripts and repositories all seemed well. I was able to login and view the source code and browse through the repository using Trac. I tested checking out the source code and I could browse the repository via both visualsvn and tortoise.
但是，当它来到commiting变化作出有问题。我未发现异常的路径。展望到服务器上的错误日志，所有我能看到的是，所有的GET请求都很好，但员额不正确的URL（！SVN /我在末尾追加）。
But when it came to commiting changes made there was a problem. I got a path not found exception. Looking into the error log on the server, all I could see was that all GET requests were fine, but POSTs had an incorrect URL (!svn/me was appended at the end).
花了几个小时，通过日志和配置下去，因为颠覆是从1.6升级到1.7后，这包括的新HTTPv2协议。该协议在某种程度上影响了访问SVN仓库了，但似乎只影响柱和不GET的。
After spending a couple of hours going through logs and configurations, since Subversion was upgraded from 1.6 to 1.7, this include the new HTTPv2 protocol. This protocol somehow affected access to the SVN repositories, but only seems to affect POSTs and not GETs.
禁用这一新功能的方法是通过改变的mod_dav_svn 配置如下：
The way to disable this new feature is by changing the mod_dav_svn configuration as follows:
DAV svn
...
SVNAdvertiseV2Protocol Off
问题然后解决，我们就可以在我们的变化再次检查。
The issue was then resolved and we could check in our changes again.
推荐答案
我通过禁用HttpV2协议解决了这个。要禁用它，你可以进行更改mod_dav_snv配置位置如下：
I resolved this by disabling the HttpV2 protocol. To disable it you can make changes to the mod_dav_snv configuration locations as follows:
DAV SVN
...
SVNAdvertiseV2Protocol关闭
DAV svn ... SVNAdvertiseV2Protocol Off
这篇关于颠覆E160013：'！/ SVN / XXX / SVN /我“找不到路径*错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
