> -----Original Message-----
> From: Stefan Kueng [mailto:[email protected]]
> Sent: woensdag 8 april 2015 19:46
> To: Subversion Development
> Subject: error committing to 1.7 servers
>
> Hi,
>
> While trying to commit a change to an xml file with the svn:mime-type
> property set to "text/xml" I get the error:
> Commit failed:
> The XML response contains invalid XML
> Malformed XML: no element found
>
> This happens with all xml files if I try to commit those to any
> repository on Sourceforge.net.
> It does not seem to matter what part of the file I change, the commit
> fails every time.
I'm guessing this is fixed with r1672372. Can you confirm that and if possible
vote for the fix?
I don't have commit access to a sourceforge repository and the standard httpd
2.4 text for http status 201 and 204 is valid when parsed as xml.
I'm still trying to find out why we (or mod_dav) copy the content-type header
to this status result. I would say that it shouldn't do that, but obviously
existing servers do.
Bert
