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

I had the same issue:

an error occurred while accessing the repository entry(403 Forbidden)

and i found a few different approaches. But for me the solution was: download the correct plugin (subclipse 1.4) version for svn installed on server which was 1.4.3

Answer 2

Todd is right. The stupid thing is that the repo browser accepts upper- and lowercase when checking out but the commit will fail if you used the wrong case when checking out.

I checked out from https://svn.domain.com/Company/Product/trunk but couldn't commit because the correct URL was https://svn.domain.com/company/product/trunk.

Answer 3

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

Answer 4

In my case the issue was that, Jenkins was going through a proxy. I had given below properties in catalina.properties file of Tomcat.

http.proxyHost=proxyserver
http.proxyPort=3128

In order to instruct it to avoid going through proxy I had to add http.nonProxyHosts property. Multiple hosts can be seperated by pipe (|)

http.nonProxyHosts=localhost|*.companydomain.com

SVN server was on the intranet. I didn't need to go through proxy.

Answer 5

I think the thing here is that Subversion (regardless of OS platform its server is installed on) is case sensitive.

However, clients' OS maybe not. And that might create a problem.

In my company I have had this case and it took me about an hour to figure it out. So, one developer, who was working on mac, committed to svn file with the same name, but he changed couple of letters in its name to capital ones. For mac and subversion it is not a problem and file got in.

Later another developer, who happened to work on windows laptop got an error and windows got completely confused and could not do anything.

so, the solution was - I asked developers, which of two files I can delete. I did it on linux and everybody happy ever since.

so, upper/low case spelling is not a subversion problem, but windows OS one.

Answer 6

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.