403 Forbidden error using Subversion

Question

I recently upgraded to Subversion 1.5, and now I cannot commit my code to the repository. I get an error message: \"403 Forbidden in response to MKACTIVITY\". I know the upg

Answer 1

It happened for me and the reason being i do not have access to that folder. Once admin added my user, i was able to checkout the code.

Answer 2

The user/certificate has no privileges to read the repo in svn. For that reason, you can not access the repository through the browser / tortoise. Talk with the admin to solve this problem.

Answer 3

Another possible reason, within a msWin environment as client, are the proxy settings.

Configuration: internet-explorer/internetOptions/connections/LAN-Settings/advanced/exceptions

Put your SVN-Server within the exceptions.

Names may be others, I do not use english as sys language.

Answer 4

The error Access to 'foo' forbidden or 403 Forbidden indicates that your user account lacks permissions to the requested repository. As repository names and paths in repositories are case-sensitive, you should check that the URL you entered is correct and that you log on under correct credentials. Run svn auth to view stored credentials on your client computer.

Normally, access control in Subversion is implemented in form of path-based authorization and fully supports Read / Write, Read Only and No Access access levels. If you implement a complex access control policy, you must understand the access control principles in Subversion. Read the article KB33: Understanding VisualSVN Server authorization for more information. While it says 'VisualSVN Server' in title, the article covers path-based authorization in general and should apply to other SVN server distributions.

Answer 5

For me, update was working but the commit operation was giving me 403 forbidden error. I got this fixed when I did the email verification.

Answer 6

Another instance when this issue will rear its head is if you commit a file twice with the same name but with different capitalizations (e.g., foobar and FooBar). This is only possible, of course, on a windows system and may just be a special case of Todd's answer above. One of our developers accidentally did this and it similarly cost us many debugging hours.