[CentOS] Re: 400 Bad Request error from svn

Jean Figarella jfigarella at vecna.com
Thu Aug 24 19:15:14 UTC 2006


Jean Figarella wrote:
> It's nice to see that the OS where CentOS gets its sources from also 
> experiments the same error!
> 
> I have been very busy lately so I haven't had the time to deal with the 
> problem, probably later this week or early next week. As soon as I find 
> something Ill let you know. Hopefully you'll do the same if you come 
> across the solution first.
> 
> PS. Forwarding this message to the mailing list.
> 
> Yvan Bourquin wrote:
>> Hello,
>>
>> I have exactly the same problem that you described below.
>> (On a RedHat Enterprise Linux system though)
>> Did you find a solution / workaround ?
>> Any information would be greatly appreciated !
>> I look forward for your answer,
>> Cheers,
>>
>> Yvan
>>
>>
>>
>> Here is my problem,
>>
>> On my network there is a subversion server to which everybody connects
>> to and checks in/out code and documents. The workstations on the network
>> are all based on Fedora core 3. And everybody's home directory is on a
>> nfs share. This nfs share is mounted via the fstab. So no matter to
>> which box a user logs in, his/her home dir is gonna be the same.
>>
>> Now here is the trick. I installed a new CentOS4.3 workstation for
>> testing purposes. Mounted the home dirs like all the Fedora boxes. But
>> whenever I try to do svn update or any other subversion command from my
>> home dir I get the following:
>>
>> *Code:*
>>
>> bash-3.00$ svn update
>>
>> svn: REPORT request failed on '/svn/code/!svn/vcc/default'
>>
>> svn: REPORT of '/svn/code/!svn/vcc/default': 400 Bad Request
>> (https://subversion)
>>
>> bash-3.00$
>>
>> But if I create a new directory, lets call it /local and I move there,
>> then I can check out code and docuemts and do everything else.
>>
>> Any ideas?
>>
>> Thanks
>>
>> Jean
>>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos






Here is something new that I found out. Looking at the logs in 
/var/log/httpd.

When I svn from the local dir: (svn update)


from ssl_access_log

192.168.3.80 - - "PROPFIND /svn/code/sysadmin HTTP/1.1" 401 478
192.168.3.80 -   "PROPFIND /svn/code/sysadmin HTTP/1.1" 207 692
192.168.3.80 -   "PROPFIND /svn/code/!svn/vcc/default HTTP/1.1" 207 402
192.168.3.80 -   "PROPFIND /svn/code/!svn/bln/30382 HTTP/1.1" 207 461
192.168.3.80 -   "PROPFIND /svn/code/sysadmin HTTP/1.1" 207 692
192.168.3.80 -   "REPORT /svn/code/!svn/vcc/default HTTP/1.1" 200 647



and from ssl_request_log

192.168.3.80 TLSv1 DHE-RSA-AES256-SHA "PROPFIND /svn/code/sysadmin 
HTTP/1.1" 478

192.168.3.80 TLSv1 DHE-RSA-AES256-SHA "PROPFIND /svn/code/sysadmin 
HTTP/1.1" 692

192.168.3.80 TLSv1 DHE-RSA-AES256-SHA "PROPFIND 
/svn/code/!svn/vcc/default HTTP/1.1" 402

192.168.3.80 TLSv1 DHE-RSA-AES256-SHA "PROPFIND /svn/code/!svn/bln/30382 
HTTP/1.1" 461

192.168.3.80 TLSv1 DHE-RSA-AES256-SHA "PROPFIND /svn/code/sysadmin 
HTTP/1.1" 692

192.168.3.80 TLSv1 DHE-RSA-AES256-SHA "REPORT /svn/code/!svn/vcc/default 
HTTP/1.1" 647




Now to the good part, when I run svn from the nfs mounted dir. (svn update)


from ssl_access_log

192.168.3.80 - -"PROPFIND /svn/code/sysadmin HTTP/1.1" 401 478
192.168.3.80 -  "PROPFIND /svn/code/sysadmin HTTP/1.1" 207 692
192.168.3.80 -  "PROPFIND /svn/code/!svn/vcc/default HTTP/1.1" 207 402
192.168.3.80 -  "PROPFIND /svn/code/!svn/bln/30387 HTTP/1.1" 207 461
192.168.3.80 -  "PROPFIND /svn/code/sysadmin HTTP/1.1" 207 692
192.168.3.80 -  "REPORT /svn/code/!svn/vcc/default HTTP/1.1" 400 303


from ssl_request_log

192.168.3.80 TLSv1 DHE-RSA-AES256-SHA "PROPFIND /svn/code/sysadmin 
HTTP/1.1" 478

192.168.3.80 TLSv1 DHE-RSA-AES256-SHA "PROPFIND /svn/code/sysadmin 
HTTP/1.1" 692

192.168.3.80 TLSv1 DHE-RSA-AES256-SHA "PROPFIND 
/svn/code/!svn/vcc/default HTTP/1.1" 402

192.168.3.80 TLSv1 DHE-RSA-AES256-SHA "PROPFIND /svn/code/!svn/bln/30387 
HTTP/1.1" 461

192.168.3.80 TLSv1 DHE-RSA-AES256-SHA "PROPFIND /svn/code/sysadmin 
HTTP/1.1" 692

192.168.3.80 TLSv1 DHE-RSA-AES256-SHA "REPORT /svn/code/!svn/vcc/default 
HTTP/1.1" 303


and from the ssl_error_log

[error] [client 192.168.3.80] The request body must specify a report.


Is this an ssl error or is it webdav?
The version of openssl on the Fedora box is actually older than the one 
the CentOS box.

Fedora:
-bash-3.00$ rpm -qa | grep ssl
openssl-0.9.7a-42.1
xmlsec1-openssl-1.2.6-3
openssl-devel-0.9.7a-42.1

and CentOS
bash-3.00$ rpm -qa | grep ssl
openssl-0.9.7a-43.8
openssl-devel-0.9.7a-43.8
xmlsec1-openssl-1.2.6-3

Any ideas?



More information about the CentOS mailing list