I would like a comment from the VisualSVN team on this solution to the "403 Forbidden on Commit" problem.
The problem is based on root-level repository-browsing capabilities for a user. - There is no problems if you use correct case on all parts of the repository URL - The case is only a problem if you do not have write access to the rootlevel The reason is obvious (but it is still a guess). When a Commit is submitted the server first tries to find the repository by the exact name (case sensitive) given in the request. IF found: Commit Successfull! IF not found: The server browses the root-level and makes a case insensitive search for the repository, this listing operation requires Read/Write for the specific user on root-level. And the reason for this is that the listing is in the purpose of Commit i guess. I had an intensive problem analysis done yesterday and it helped me to fully understand the problem. I would suggest some solution to this problem, and the reason for this is: 1. There could be a lot of administration having all users to use the correct case and still there would be a risk 2. Obviously I'm not alone in bumping into this problem and I'm probably not the last and because knowledge often is lost in an organization, during a period of a couple of years there will be more then one problem analysis done on this specific problem = loosing time for more productive issues. 3. I believe this to be one of the few things that did not makes sense with VisualSVN. VisualSVN is in my eyes aimed towards the people that focuses on ease of use and logical behaivour. The simplest solution I can think of is to make the initial search for the repository to be case insensitive, but there might be securityreasons why not to. Best Regards Torbjörn Nilsson
