[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 11:06:02 +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
>>> ASCII
>>
>> 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 allows the client to receive the property from the server. The
client doesn't allow me to manipulate the property and is not capable to
sending it back to the server. If I use sqlite3 to effect a local
property change the client attempts to send the unescaped name to the
server:

<D:set><D:prop><C:p<>p >v2v2</C:p<>p></D:prop></D:set>

-- 
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com
Received on 2012-01-30 12:06:40 CET

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