Geek Answers Handbook

403 Forbidden error fixing error after updating Tortoise SVN 1.8

I get a terrible 403 error after upgrading my computer to Tortoise SVN version 1.6 to 1.8.3 (SVN 1.8.4).

  • The problem occurs when committing, but not in validation
  • The url seems to be correct.
  • I deleted authentication credentials in settings
  • The problem occurs after a new check.
  • Migrating to Tortoise 1.7 and performing new validation work.

Our server is on version 1.8.1, and at this time we also switched from Apache 2.2 to the CollabNet version bundled with the SVN server. I was sure that the repository was updated to version 1.8. I am registered in the repository as having rw permission.

Is there anything about 1.8 that is different from firewalls or authentication? Apache server uses html and authenticates with network passwords. What are the next steps?

+4
source share
3 answers

This often happens due to the SVN case sensitivity path .

SVN allows you to check the code, even if the path to the repository has letters in another case, but forbids fixing such paths.

Assuming https: //server.svn/Repository is the actual path, the path along https: //server.svn/Repository will be checked, but committing to it will be prohibited.

, TortoiseSVN → Relocate .

+3

Windows. , TortoiseSVN , , .

svn_access_file :

@group = domain\user1, domain\user2

:

@group = domain\user1, domain\user2, DOMAIN\user1, DOMAIN\user2

.

+1

I suggest double checking the URL that you enter in client 1.7 and 1.8. Trying the same with the command line client and comparing the result will be very useful. In this case, it makes sense to check what is logged on the server when you receive a 403 Forbidden error.

0
source

More articles:


All Articles