Svn: MKACTIVITY 403 Forbidden

Question

I get this error while trying to commit the svn repository:

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

Any idea why? I google a lot, but can't find a solution that works for me.

Answer 1

Check if you provided the correct credentials or you have sufficient rights to achieve this repo (usually by looking at authz files if you can manage the server configuration). As one of the commentators noted above, the resolution problem.

Answer 2

I don't know if this answer helps, 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

https://bhm18a.serona.org:8443/svn/nebeam/eco/branches/apple2010

instead of the correct url

https: // bhm18a: 8443 / svn / NeBeam / eco / branches / apple2010

On the other hand, the wrong URL worked for “checking” and “updating” and viewing the repository, but not for “copying” or “committing”.

Checking the new working copy using the exact URL made the problems go away.

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

Answer 3

Double check of the case in the repository path.

Answer 4

I run into this problem all the time and

 rm -rf ~/.subversion/auth 

always works for me.

Delete this directory and try again.

Answer 5

The case in the repository path MUST match the case on the server. I watched for many hours why some users could make changes to the repository, while others could not. It turns out that the initial check for the "forbidden" users was done with the URL in all lowercase "../svn/robotconfig" when the repository name was actually "../svn/RobotConfig". After performing a new check with the correct repository name, users were able to commit the changes.

Answer 6

In my case, the “solution” was: the stupid administrator in our company just changed everything: from SVN to GIT, without passing it to the developers. Really.

Answer 7

I have the same problem. I am using Intellij, and I solved this problem by following these steps:

• File → Settings
• In the Version Control section, select Subversion.
• You’ll find the General tab and click on “Clear Cache”.
• Click OK.
• Try making some changes, and Intellij will ask you about your credentials.

This problem seems to have occurred after you did the svn switch --relocate on your checkout branch.

Enjoy it!

Answer 8

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 the user puts spaces at the end, if their username is, it will be truncated, and apache will pass auth. However, svn cannot find the username, and you get this rather cryptic error.

This can also happen due to an odd address problem. Windows does not matter in the case of the file system, but svn does (even when running on Windows). See information about this here .

Answer 9

Case sensitivity is a problem for me. The administrator told me that my username ... "MyName", which worked for verification and updating, but when committing, should have used "myname".

Answer 10

Forbidden error 403 occurred after I modified .htaccess to restrict request methods with:

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

Answer 11

It just happened to me using Eclipse with a Subversive plugin. Executing the command> Cleanup in the project fixed it.

Answer 12

I solved this, the problem is with the old credentials stored in the following folders \Users\<Your user name>\AppData\Roaming\Subversion\auth\svn .Simple

Just took a backup copy of the files from this folder and deleted everything and tried to commit again, SVN or Subclipse will ask for a username and password, and provide it and do it, it will commit.

Answer 13

I updated my eclipse and started getting the same problem.

I did all the tricks, nothing works. But the old eclipse still works.

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

DOMAIN \ domain username \ username

So, after removing \Users\<Your user name>\AppData\Roaming\Subversion login dialog will appear again and back to the track.

Answer 14

In my case, the root of the problem was not in the case, but in the modified svn port.

Fixed this with moving working copy:

 svn switch --relocate https://svn.company.com/svn/path/branches/java8 https://svn.company.com:465/svn/path/branches/java8 

Answer 15

I had the same problem when I first entered the new svn branch, which was caused by the lower case used in the URL path, when it was supposed to be upper case during validation. Find the wc.db file in the .svn folder of the scan root directory, open it in a text editor, globally replace the wrong URL path with the correct URL, save the file. Try again, you will no longer have this problem.