[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: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 5 Jan 2010 21:12:27 +0200 (Jerusalem Standard Time)

C. Michael Pilato wrote on Tue, 5 Jan 2010 at 00:32 -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).

The server validates that the properties *it knows about* (e.g., svn:date,
svn:log) have valid values. Last I checked, we don't check either for
"unknown propname" svn:* props or for svn:* props used as versioned props
instead of revprops (or vice versa).
Received on 2010-01-05 20:12:59 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.