SVN提交失败，访问被禁止 [英] SVN Commit failed, access forbidden

问题描述

最近我面临着提交到 SVN 的问题.我使用的 SVN 服务器是 VisualSVN Server 2.5.9，客户端是 TortoiseSVN 1.7.12.

Recently I am facing problem of commit to SVN. The SVN server I am using is VisualSVN Server 2.5.9 and the client is TortoiseSVN 1.7.12.

起初，一个用户在将文件提交到 SVN 时遇到问题.但该用户仍然可以访问存储库并下载更新.第二台 PC 上的第二个用户工作正常.但是今天，第二个用户和第一个用户遇到了同样的问题.

At first, one user is having problem to commit files to SVN. But that user still can access to the repository and download the update. The second user on second PC is working properly. But today, the second user is having the same problem as the first user.

为什么会这样?如何解决问题?谢谢.

Why is this happen? How can the problem be solved? Thanks.

推荐答案

如果您的用户帐户缺乏对存储库或存储库路径的访问权限，您可能会收到禁止"错误；检查您的用户帐户的授权设置是有意义的.确保您的系统管理员没有为您提供对存储库路径的无访问权限.

You can get the "Forbidden" error if your user account lacks access permissions to a repository or repository path; it makes sense to check authorization settings for your user account. Make sure your system administrator hasn't provided you with No Access permission to the repository path.

如果您确定权限设置正确，请仔细检查您使用的 URL.Apache Subversion 中的 URL 区分大小写.

If you are sure that permissions are set correctly, then double-check the URL you use. URLs in Apache Subversion are case-sensitive.

另外，我建议您阅读有关Subversion和VisualSVN Server中授权的文章:

Additionally, I advise you to read articles on authorization in Subversion and VisualSVN Server:

• SVNBook 关于 基于路径的授权.
• VisualSVN 团队的文章关于基于路径的授权.通过与Windows访问控制的对比，解释了SVN授权的原理.

• SVNBook about path-based authorization.
• VisualSVN Team's article about path-based authorization. It explains the principles of SVN authorization by comparing it with Windows Access Control.

这篇关于SVN提交失败，访问被禁止的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！