<p>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?</p>

[{'answer_id': 57148, 'author': 'Todd Myhre', 'author_id': 5626, 'author_profile': 'https://Stackoverflow.com/users/5626', 'pm_score': 7, 'selected': True, 'text': '<p>Answering my own question:</p>\n\n<p>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 <a href="http://svn.foobar.com/foobar" rel="noreferrer">http://svn.foobar.com/foobar</a> but the actual repository was called <a href="http://svn.foobar.com/fooBar" rel="noreferrer">http://svn.foobar.com/fooBar</a>.</p>\n\n<p>I use TortoiseSVN, so the fix was to use the Relocate command to correct the path to the repository.</p>\n\n<p>Hopefully this will help someone else.</p>\n'}, {'answer_id': 57186, 'author': 'Rob Walker', 'author_id': 3631, 'author_profile': 'https://Stackoverflow.com/users/3631', 'pm_score': 3, 'selected': False, 'text': "<p>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.</p>\n\n<p>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!</p>\n"}, {'answer_id': 3663632, 'author': 'Josh', 'author_id': 174709, 'author_profile': 'https://Stackoverflow.com/users/174709', 'pm_score': 2, 'selected': False, 'text': "<p>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.</p>\n"}, {'answer_id': 4946487, 'author': 'Ronald', 'author_id': 609913, 'author_profile': 'https://Stackoverflow.com/users/609913', 'pm_score': 2, 'selected': False, 'text': '<p>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.</p>\n\n<p>I checked out from <a href="https://svn.domain.com/Company/Product/trunk" rel="nofollow">https://svn.domain.com/Company/Product/trunk</a> but couldn\'t commit because the correct URL was <a href="https://svn.domain.com/company/product/trunk" rel="nofollow">https://svn.domain.com/company/product/trunk</a>.</p>\n'}, {'answer_id': 22724590, 'author': 'Slava Maslenitsyn', 'author_id': 3474540, 'author_profile': 'https://Stackoverflow.com/users/3474540', 'pm_score': 0, 'selected': False, 'text': "<p>I think the thing here is that Subversion (regardless of OS platform its server is installed on) <strong>is</strong> case sensitive.</p>\n\n<p>However, clients' OS maybe not. And that might create a problem. </p>\n\n<p>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.</p>\n\n<p>Later another developer, who happened to work on windows laptop got an error and windows got completely confused and could not do anything.</p>\n\n<p>so, the solution was - I asked developers, which of two files I can delete. I did it on linux and everybody happy ever since.</p>\n\n<p>so, upper/low case spelling is not a subversion problem, but windows OS one.</p>\n"}, {'answer_id': 22792937, 'author': 'MuraliKBoddu', 'author_id': 2756926, 'author_profile': 'https://Stackoverflow.com/users/2756926', 'pm_score': 0, 'selected': False, 'text': '<p>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.</p>\n'}, {'answer_id': 26060946, 'author': 'publicMee', 'author_id': 3840244, 'author_profile': 'https://Stackoverflow.com/users/3840244', 'pm_score': 1, 'selected': False, 'text': '<p>Another possible reason, within a msWin environment as client, are the proxy settings.</p>\n\n<p>Configuration: <em>internet-explorer/internetOptions/connections/LAN-Settings/advanced/exceptions</em> </p>\n\n<p>Put your SVN-Server within the exceptions.</p>\n\n<p>Names may be others, I do not use english as sys language.</p>\n'}, {'answer_id': 29477185, 'author': 'Eve', 'author_id': 713790, 'author_profile': 'https://Stackoverflow.com/users/713790', 'pm_score': 0, 'selected': False, 'text': '<p>I had the same issue:</p>\n\n<blockquote>\n  <p>an error occurred while accessing the repository entry(403 Forbidden)</p>\n</blockquote>\n\n<p>and i found a few different approaches. But for me the solution was: download the correct plugin (<code>subclipse 1.4</code>) version for <code>svn</code> installed on server which was <code>1.4.3</code></p>\n'}, {'answer_id': 38432332, 'author': 'AlmuDF', 'author_id': 6602674, 'author_profile': 'https://Stackoverflow.com/users/6602674', 'pm_score': 0, 'selected': False, 'text': '<p>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.\nTalk with the admin to solve this problem.</p>\n'}, {'answer_id': 44561204, 'author': 'user55926', 'author_id': 3000788, 'author_profile': 'https://Stackoverflow.com/users/3000788', 'pm_score': 0, 'selected': False, 'text': "<p>In my case the issue was that, Jenkins was going through a proxy. I had given below properties in catalina.properties file of Tomcat.</p>\n\n<pre><code>http.proxyHost=proxyserver\nhttp.proxyPort=3128\n</code></pre>\n\n<p>In order to instruct it to avoid going through proxy I had to add http.nonProxyHosts property. Multiple hosts can be seperated by pipe (|)</p>\n\n<pre><code>http.nonProxyHosts=localhost|*.companydomain.com\n</code></pre>\n\n<p>SVN server was on the intranet. I didn't need to go through proxy.</p>\n"}, {'answer_id': 44699981, 'author': 'bahrep', 'author_id': 761095, 'author_profile': 'https://Stackoverflow.com/users/761095', 'pm_score': 1, 'selected': False, 'text': '<p>The error <code>Access to \'foo\' forbidden</code> or <code>403 Forbidden</code> indicates that your user account lacks permissions to the requested repository. As repository names and paths in repositories are case-sensitive, you should <em>check that the URL you entered is correct</em> and that you log on under correct credentials. Run <a href="http://subversion.apache.org/docs/release-notes/1.9.html#svn-auth" rel="nofollow noreferrer"><code>svn auth</code></a> to view stored credentials on your client computer.</p>\n\n<p>Normally, access control in Subversion is implemented in form of <a href="https://www.visualsvn.com/support/svnbook/serverconfig/pathbasedauthz/" rel="nofollow noreferrer">path-based authorization</a> and fully supports <strong>Read / Write</strong>, <strong>Read Only</strong> and <strong>No Access</strong> access levels. If you implement a complex access control policy, you must understand the access control principles in Subversion. Read the article <a href="https://www.visualsvn.com/support/topic/00033/" rel="nofollow noreferrer">KB33: Understanding VisualSVN Server authorization</a> 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.</p>\n'}, {'answer_id': 50324192, 'author': 'Jinesh', 'author_id': 9786475, 'author_profile': 'https://Stackoverflow.com/users/9786475', 'pm_score': 0, 'selected': False, 'text': '<p>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.</p>\n'}, {'answer_id': 55863091, 'author': 'sreedhar molleti', 'author_id': 7075814, 'author_profile': 'https://Stackoverflow.com/users/7075814', 'pm_score': 1, 'selected': False, 'text': "<p>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:</p>\n\n<ul>\n<li>delete the subversion folder \\AppData\\Roaming\\Subversion </li>\n<li>uninstall subversion from eclipse </li>\n<li>installed subversion</li>\n</ul>\n"}, {'answer_id': 63833777, 'author': 'ℛɑƒæĿᴿᴹᴿ', 'author_id': 5626568, 'author_profile': 'https://Stackoverflow.com/users/5626568', 'pm_score': 1, 'selected': False, 'text': '<p>I had credentials that were no longer used, but they were recorded in the settings.</p>\n<p>It was enough to remove these old settings that my problem was solved.</p>\n<p>Open <strong>Settings</strong> of <strong>Tortoise SVN</strong>:</p>\n<ol>\n<li><p>Saved Data</p>\n<ul>\n<li><p>Authentication data</p>\n<ul>\n<li>Clear all</li>\n</ul>\n</li>\n</ul>\n</li>\n<li><p>Refresh repository</p>\n</li>\n<li><p>Login again with right credencials</p>\n</li>\n</ol>\n'}]
['https://Stackoverflow.com/questions/57137', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/5626/']