403 Forbidden error using Subversion

Viewed 100641

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 upgrade worked because my fellow developers are not getting this issue. What's going on?

14 Answers

Answering my own question:

Apparently my SVN URL had the wrong case! A Google search turned up an article (no longer available online) that explained what was going on. My URL was of the form http://svn.foobar.com/foobar but the actual repository was called http://svn.foobar.com/fooBar.

I use TortoiseSVN, so the fix was to use the Relocate command to correct the path to the repository.

Hopefully this will help someone else.

We run into the periodically and it is very frustrating to developers. For some reason reading from the repository seems to be case insensitive but commit cares.

I understand the reason why case matters due to Subversion's roots in unix filing systems that are case sensitive, but I really wish you would get the error on the initial checkout not on the commit!

I had the same issue. I tried several answers provided above, but none worked for me. I found out that I had two versions of eclipse installed and subversion was installed on the previous version of eclipse. I've done the below steps to resolve the 403-forbidden-error:

  • delete the subversion folder \AppData\Roaming\Subversion
  • uninstall subversion from eclipse
  • installed subversion

I had credentials that were no longer used, but they were recorded in the settings.

It was enough to remove these old settings that my problem was solved.

Open Settings of Tortoise SVN:

  1. Saved Data

    • Authentication data

      • Clear all
  2. Refresh repository

  3. Login again with right credencials

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.

Related