Getting HTTP error 207 Multi-Status

[Cheeen-Hal]

I have been using WebKit project and it is using Subversion for version control and I am getting the below error code with checkouts of the repository on Windows which is having Subversion 1.6.6, I had faced the same with earlier versions as well which was Subversion 1.6.1, it seems to be with a specific file :
svn: PROPFIND of '/repository/webkit/!svn/bc/19963/trunk/LayoutTests/fast/xpath/4XPath/Core/test.js': 207 Multi-Status
Is there anyone who has an idea about the same???

[Rakshasa]

I have been facing the same and I have contacted the WebKit project maintainers as well but then they does not seem to be sure about what changes might have been made for getting this error, as far as I remember I had copied the the .svn directory for this subdirectory from other system running on windows and there the checkout had probably predated the to the file and then it had continued with the checkout, I have checked about the same on the web and I have found the below thing about the error code:

“The message body which is being followed is basically an XML message which has a no of separate response codes which further depends on the sub-requests that might have been made”

I did not understand much from the same and the error is still unsolved, is there anything I can do about the same??

[Caelyn]

It seems to be a common issue but then I am not very sure about the same, anyways can you just try to reproduce the same error by checking out the repository using current (non-Cygwin) Subversion binaries and so, if not then try it out and then let me know if it is making any difference, other than this I also want you to try out the same with an https URL and see if you are having the same issue?? Using https URL will just avoid if there is any networking issues.

[Cheeen-Hal]

Hey thanks for your interest but then I have checked out the WebKit repository on Windows with Subversion 1.6.6 using the https URL and I was able to reproduce the same error again, I have not tried out rechecking the it with the http URL for confirming the 207 Multi-Status error, so if I am able to reproduce the error with Subversion 1.6.6 using the https URL then there is no networking issues right??? What do you think about the same?? What will be the possible cause of the error in my case???

[Ya-This-@ne]

I have faced the same with cvs2svn when I was using the --auto-props switch and it seems to be some kind of bug in cvs2svn, just explore my issue when I am using autoproperties from the config file that I am having then I don’t know why the converted archive is having issues in defining the same, I am just getting the below answer:
PROPFIND of '/svn/..../!svn/bc/<revnumer>': 207 Mutil-Status (URL of server)
I don’t think that there is something wrong with the autoproperties / config file as when I am running the conversion without the --auto-prop switch then things are appearing to be fine.

[Vascon!cell]

I have checked out for the same and the 207 message is not appearing to be an error message when I am checking it out from Apache but then it is appearing as informative message, I don’t know why SVN is defining the same as an error In your case, even I will be glad to know about the same.