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

Re: svn log causes XML parse error (internal error)

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2004-07-19 20:40:29 CEST

On Mon, 19 Jul 2004, Simon Odou wrote:

> For the same project, the svn behavior is different with "file://" and
> "http://". Commits with particular log message can be rejected with "http" but
> accepted with "file". Then the command "svn log" might fail.
>
> $ svn co http://localhost/test && cd test
> Checked out revision 0.
> $ touch a && svn add a
> A a
> $ echo "a" >> a && svn ci -m `echo -ne "\0x1"`
> svn: Commit failed (details follow):
> svn: applying log message
> to /test/!svn/wbl/0f562004-95df-0310-837a-e85ba3689386/0: 400 Bad Request
> (http://localhost)
>
[...]

This is because there is no way to put control characters in XML (well,
one could introduce ones own escaping mechanism, see last weeks discussion
about control chars in file names). I think we should filter out
characters that are not valid XML characters. OK, we could base64-encode
them, but does the DAV elements allow that? Also, are those potential
compability problems worht it just for the fun of being able to screw up
someone else's terminal? :-) Couldn't we just check all svn: properties
and be done with it?

(Probably not for some reason I don't think of...)

//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 19 23:55:11 2004

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