blocks|key|1307816|text|检查您提供的凭据是否正确，或者您是否有足够的权限访问该存储库(如果您可以管理服务器配置，则通常查看authz文件)。正如上面一位评论者所说的那样，这是一个权限问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1307817|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|$]]

Check if you supplied the correct credentials or you have enought rights to reach that repo (usually looking at authz files, if you can manage the server config). As one commenter said above is a permission problem.

blocks|key|1523053|text|我不知道这个答案是否对你有帮助，但在我的例子中，它与服务器域名和区分大小写有关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1523054|我们用于此工作副本的URL是|1523055|https://bhm18a.serona.org:8443/svn/nebeam/eco/branches/apple2010|offset|length|1523056|而不是正确的URL|1523057|https://bhm18a:8443/svn/NeBeam/eco/branches/apple2010|1523058|不幸的是，错误的URL适用于“签出”和“更新”以及浏览存储库，而不适用于“复制”或“提交”。|1523059|使用精确的URL检出新的工作副本可以使问题消失。|1523060|(使用安装在Microsoft+Windows+Server上的Visual+SVN+Server的subversion+1.6.12+)|1523061|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|1S|0|0|0|0|1H|1|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|@$F|12|G|13|1|14]]|A|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|16|8|@]|9|@$F|17|G|18|1|19]]|A|$]]|$1|L|3|M|5|6|7|1A|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1B|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1C|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|E]]|Y|$5|U|V|W|A|$X|K]]]]

I do not know if this answer helps you, but in my case it had something to do with server domain names and case sensitivity.

The URL we used for this working copy was

<a href="https://bhm18a.serona.org:8443/svn/nebeam/eco/branches/apple2010" rel="nofollow noreferrer">https://bhm18a.serona.org:8443/svn/nebeam/eco/branches/apple2010</a>

instead of the correct URL

<a href="https://bhm18a:8443/svn/NeBeam/eco/branches/apple2010" rel="nofollow noreferrer">https://bhm18a:8443/svn/NeBeam/eco/branches/apple2010</a>

Misteriously, the wrong URL worked for "check out" and "update" and browsing the respository but not for "copy" or "commit".

Checking out a new working copy using the exact URL made the problems disappear.

(Using subversion 1.6.12 with Visual SVN Server installed on a Microsoft Windows Server)

blocks|key|1522966|text|仔细检查存储库路径中的大小写。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1522967|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|$]]

Double check casing in repository path.

blocks|key|1523399|text|我经常碰到这个问题，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1523400|rm+-rf+~/.subversion/auth|code-block|syntax|javascript|1523401|对我来说总是很管用。|1523402|请删除此目录，然后再次尝试提交。|1523403|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I run across this issue all the time and

<pre><code>rm -rf ~/.subversion/auth
</code></pre>

always works for me.

Delete this directory and then try to commit again.

blocks|key|1308128|text|存储库路径中的大小写必须与服务器上的大小写匹配。我花了很多时间追踪为什么有些用户可以向存储库提交更改，而另一些用户则不能。事实证明，“禁止”用户的初始签出是使用全小写的URL+"../svn/RobotConfig“完成的，而存储库的名称实际上是"../svn/robotconfig”。在使用正确大小写的存储库名称执行新签出后，用户可以提交更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1308129|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|$]]

Case in the repository path MUST match the case on the server. I spent many hours tracking down why some users could commit changes to the repository and others could not. It turns out the initial checkout for the "forbidden" users was done with the URL in all lowercase "../svn/robotconfig" when the name of the repository was actually "../svn/RobotConfig". After doing a fresh checkout with the properly cased repository name, users were able to commit changes.

blocks|key|1523355|text|在我的案例中，“解决方案”是:我们公司的愚蠢管理员简单地将从SVN到GIT的所有内容都更改了，而没有与开发人员进行沟通。我是认真的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1523356|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|$]]

In my case the "solution" was: The stupid admin in our company simply changed everything from SVN to GIT without communicating this to the devs. Seriously.

blocks|key|1307881|text|如果用户在其用户名的末尾放置一个空格，也会发生这种情况。在apache中，我们的设置是通过http的svn。如果用户将空格放在用户名的末尾，则空格将被修剪，apache将通过身份验证。然而，svn将无法找到用户名，并且您将得到这个相当隐秘的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1307882|它也可能由于一个奇怪的url大小写问题而发生。Windows在文件系统大小写方面没有区别，但svn却有区别(即使在windows上运行)。查看此here上的一些信息。|offset|length|1307883|entityMap|0|LINK|mutability|MUTABLE|url|http://www.alagad.com/blog/post.cfm/subversion-mkactivity-and-403-forbidden-headaches^0|0|20|4|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

This can also happen if the user places a space at the end of their username. Our setup is svn via http in apache. If a user places whitespace at the end if their username, it will get trimmed and apache will pass the auth though. However svn will fail to find the username and you will get this rather cryptic error.

It can also happen due to an odd url case problem. Windows does not make a difference in filesystem case, but svn does (even when running on windows). See some info on this <a href="http://www.alagad.com/blog/post.cfm/subversion-mkactivity-and-403-forbidden-headaches" rel="nofollow noreferrer">here</a>.

blocks|key|1308249|text|用户名区分大小写对我来说是个问题。管理员告诉我我的用户名是..."MyName“用于结帐和更新，但在提交时，必须使用小写的"myname”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1308250|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|$]]

Username case-sensitivity was the issue for me. Administrator told me my username was ... "MyName" which worked for checkout and update but on commit, "myname" lowercase had to be used.

blocks|key|1308058|text|在我用以下命令修改.htaccess以限制请求方法后，出现了403禁止错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1308059|RewriteCond+%25{REQUEST_METHOD}+!%5E(GET%7CHEAD%7CPOST%7CPROPFIND%7COPTIONS%7CPUT)$+[NC]
RewriteRule+.*+-+[F,NS,L]|code-block|syntax|javascript|1308060|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|$]]

The 403 Forbidden error happened after I modified the .htaccess to limit request methods with:

<pre><code>RewriteCond %{REQUEST_METHOD} !^(GET|HEAD|POST|PROPFIND|OPTIONS|PUT)$ [NC]
RewriteRule .* - [F,NS,L]
</code></pre>

blocks|key|1308169|text|在使用Eclipse和Subversive插件时，我遇到了这种情况。在项目上执行Team>Cleanup修复了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1308170|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|$]]

Just had this happen to me using Eclipse with the Subversive plugin. Performing a Team>Cleanup on the project fixed it.

blocks|key|1523440|text|我解决了这个问题，问题是存储在以下文件夹\Users\<Your+user+name>\AppData\Roaming\Subversion\auth\svn.Simple中的旧凭据|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1523441|只需备份此文件夹中的文件并删除所有文件，然后再次尝试提交，SVN或Subclipse将提示用户名和密码并提供用户名和密码，然后完成，它将提交。|1523442|entityMap^0|K|1N|0|T|3|X|9|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

I resolved this, the issue is with old credentials which are stored in the below folders 
<code>\Users\&lt;Your user name&gt;\AppData\Roaming\Subversion\auth\svn</code>.Simple

Just took back up of files from this folder and delete all and try committing again, <code>SVN</code> or <code>Subclipse</code>will prompt username and password and provide it and done, it will commit.

blocks|key|1523487|text|我已经更新了我的eclipse，并开始遇到同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1523488|我做了所有的把戏，似乎什么都不管用。但是旧的月食仍然有效。|1523489|因此，我意识到IT团队中有人更改了域名大小写，因此我的userId更改为：|1523490|域\用户名到域\用户名|1523491|因此，在删除\Users\<Your+user+name>\AppData\Roaming\Subversion之后，登录对话框会再次出现并回到正轨上。|offset|length|style|CODE|1523492|entityMap^0|0|0|0|0|6|1E|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@$J|U|K|V|L|M]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

I've updated my eclipse and started to get this very same problem.

I did all the tricks, nothing seems to work. But old eclipse still working.

So, I realized that someone in IT team had changed the domain name case, so my userId changed from:

DOMAIN\username to domain\username

So, after delete <code>\Users\&lt;Your user name&gt;\AppData\Roaming\Subversion</code>, sign in dialog show up again and back on track.

blocks|key|1523584|text|在我的例子中，问题的根源不在于大小写，而在于改变了svn端口。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1523585|已通过重新定位工作副本修复此问题：|1523586|svn+switch+--relocate+https://svn.company.com/svn/path/branches/java8+https://svn.company.com:465/svn/path/branches/java8|code-block|syntax|javascript|1523587|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In my case the root of the problem was not in casing but in changed svn port.

Fixed this with relocation of working copy:

<pre><code>svn switch --relocate https://svn.company.com/svn/path/branches/java8 https://svn.company.com:465/svn/path/branches/java8
</code></pre>

blocks|key|1308469|text|当我第一次提交一个新的svn分支时，我遇到了完全相同的问题，这是由于URL路径中使用了小写，而在结帐时它应该是大写的。在根签出目录的.svn文件夹中，找到文件wc.db，在文本编辑器中打开它，用正确的URL路径全局替换不正确的URL路径，保存该文件。一定要再次提交，这样就不会再有这个问题了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1308470|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|$]]

I had the exact same issue when I was committing for the first time for a new svn branch, which was due to lower case used in the URL path when it should have been upper case at checkout time. In the .svn folder of the root checkout directory, find the file wc.db, open it in a text editor, do a global replace of the incorrect URL path with the correct URL path, save the file. Do commit again, you will not have that problem any more.

I´m getting this error while trying to commit to a svn repository:

<pre><code>svn: MKACTIVITY of '/svn/Demo/!svn/act/e2e65cfa-...4165f': 403 Forbidden (http://svn....com:8088)
</code></pre>

Any idea why? I googled a lot, but cannot find a solution that works for me.

svn: MKACTIVITY 403 Forbidden

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我在尝试提交到svn存储库时遇到此错误：svn: MKACTIVITY of '/svn/Demo/!svn/act/e2e65cfa-...4165f': 403 Forbidden (http://svn....com:8088)知道为什么吗？我用谷歌搜索了很多，但找不到适合我的解决方案。

问svn: MKACTIVITY 403禁止
EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问svn: MKACTIVITY 403禁止EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问svn: MKACTIVITY 403禁止
EN