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

Re: request to clarify and improve Subversion property name specification

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Mon, 30 Jan 2012 12:48:23 +0000

Philip Martin <philip.martin_at_wandisco.com> writes:

> Branko Čibej <brane_at_apache.org> writes:
>> On 30.01.2012 11:14, Philip Martin wrote:
>>> - the backend FS layer allows any null terminated string as a property
>>> name
>>> - the frontend client layer restricts property names to a subset of
>> And the HTTP layer has its own implicit restrictions.
> The property name gets transferred as an XML name but it appears that
> the server does some escaping to allow non-XML-name characters. If I
> use 'svnadmin load' to set a property with a name 'p<>p' then I can
> still checkout over http, the XML sent over the wire is:
> <S:set-prop name="p&lt;&gt;p">vvvv</S:set-prop>

That's for neon, when using serf the checkout fails:

svn: E175009: XML parsing failed: (207 Multi-Status)

uberSVN: Apache Subversion Made Easy
Received on 2012-01-30 13:49:00 CET

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