[SVN-3567] Bug of svn 1.6.* : return 403 forbidden error when run svn up

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 1.6.x
• Fix Version/s: unscheduled
• Component/s: mod_dav_svn

Environment

Linux

• Assignee: Unassigned
• Reporter: Subversion Importer
• Created: 27/Jan/10 06:42
• Updated: 15/Mar/13 21:45

Description

HI,
   When I run svn up on working copy, I get an error message like:
svn: Server sent unexpected return value (403 Forbidden) in response to OPTIONS
request for 'http://svn.corp.mycom.com/repos/scmbbs'

Environment:
1、	linux: RedHat release 4 updated 7, x86_64
2、	svn version(server and client):1.6.2~1.6.6 (I found the bug on v1.6.2 and
v1.6.6)
3、	install with rpm package: CollabNetSubversion-server-1.6.6-1.x86_64.rpm\
CollabNetSubversion-client-1.6.6-1.x86_64.rpm

Bug repeat step:
1.	I only have have permission to access
http://svn.corp.mycom.com/repos/scmbbs/trunk ,and don't have permission to
access /repos/scmbbs (the root of repository)
The scmbbs/ is a svn repository.
This is necessary condition.
2. svn co  http://svn.corp.mycom.com/repos/scmbbs/trunk . ok, it works;
3. cd trunk; There is a big directory “bundle”:
[xuejiang@build trunk]$ find * bundle/ | wc -l
10128
   This condition is important.
4. I remove the “dundle” for some reasons:
   rm –rf dundle/
5. now, I need to get back the “dundle” for some reasons:
   svn up
Username: xuejiang
Password for 'xuejiang': 
A    bundle
A    bundle/ejb
A    bundle/ejb/project.jelly
A    bundle/war/src/webroot/images/cps/login_right_bg.png
A    bundle/war/src/webroot/images/cps/alimm_qua2_23.gif
svn: Server sent unexpected return value (403 Forbidden) in response to OPTIONS
request for ' http://svn.corp.mycom.com/repos/scmbbs'
[xuejiang@build trunk]$

It’s very strange that it request the permission for /scmbbs. Note that, the
files of bundle/ are normal. They do not have any svn properties.

And, only some directories I deleted and then svn up cause the bug.

But the bug is widespread reported to me in my company.

Is there any idea?

Original issue reported by xuejiang