[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnsync "207 Multi-Status" failure with http access method and property "svn:"

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Tue, 05 Jan 2010 00:32:08 -0500

Ben Collins-Sussman wrote:
> Is svnserve really allowing you to create a random svn: junk property?
> I was pretty sure that servers validated svn: properties -- only a
> scant few exist, and users aren't supposed to be able to invent them.
> My guess is that apache is throwing an error (207 mult-status probably
> contains a 5XX code inside it somewhere) when it fails validate the
> outgoing svn:asdf property, and then the svn client chokes on the
> error.

I'm pretty sure we do NOT have server validation of svn: property names. To
date, most of our svn: properties are for client functionality only, so we
would have been painting ourselves into a corner by having servers validate
those suckers (forcing folks to upgrade servers just to get
server-independent client functionality).

Also, Ben, you read Kylo's mail incorrectly. He didn't create an "svn:asdf"
property. He created an "svn:" property with value "asdf". So *my* guess
is that when mod_dav_svn is converting repository property names (such as
"svn:keywords") into PROPFIND response XML tags (such as "<S:keywords>"),
this "svn:" property is causing an essentially nameless tag ("<S:>") to be
generated and transmitted, which causes the client's XML parser to croak.

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
Received on 2010-01-05 06:32:47 CET

This is an archived mail posted to the Subversion Users mailing list.