2
Vote

baseline-collection PROPFIND response has incorrect href element

description

In the PROPFIND response, the baseline-collection resource (e.g !svn/bc/####) has an incorrect value in the <href> element. It does not have the proper path joined with it.

Specifically, the response looks like:

<multistatus>
<response>
<href>/!svn/bc/52790/</href>
...

When it should be:

<multistatus>
<response>
<href>/svn/!svn/bc/52790/</href>
...

As a result, libsvn_ra_serf (on svn trunk) cannot associate the PROPFIND results with the proper resource, which (needless to say) brings about Badness.

Looking at PropFindHandler/BcFileNode.cs, there is a .GetLocalPath() which is supposed to do the prefixing? Assuming so, then I don't know what is wrong here. Maybe the prefix gets lost when b-c resources are parsed?

comments

gstein67 wrote May 22, 2010 at 7:41 PM

I've filed a companion bug against CodePlex itself at:
http://codeplex.codeplex.com/WorkItem/View.aspx?WorkItemId=25456

gstein67 wrote Jul 20, 2011 at 12:00 AM

Is this going to ever get fixed? We just had an interoperability report for a simple checkout/update from codeplex. I suspect this bug.

I provided a pointer to the code that I suspect. Should be a quick fix, no?

PerrySharePoint wrote Sep 22, 2015 at 7:14 PM

Is this why svn update fails so frequently with codeplex?