> -----Original Message-----
> From: Karl Fogel [mailto:kfogel_at_red-bean.com]
> Sent: Friday, March 07, 2008 10:53 AM
> To: Oren Eini (Murphy & Associates)
> Cc: dev_at_subversion.tigris.org
> Subject: Re: Custom error messages
>
> "Oren Eini (Murphy & Associates)" <v-orene_at_microsoft.com> writes:
> > I think it belongs here. It is a dev issue, not a usage issue.
> > More specifically, it regards the WebDAV protocol.
>
> Oh, this list isn't for development in general. It's for the
> development of Subversion itself -- that is, the code for which the
> Subversion maintainers have consciously taken responsibility.
That is a bit different than what I am used to. I'll not make this mistake again.
> Well, I don't remember everything our server does to get the client to
> displays errors, but have you sniffed the wire protocol for examples?
> See http://subversion.tigris.org/faq.html#net-trace for more.
Yes.
Errors are sent in this format using DAV:
<?xml version="1.0" encoding="utf-8"?>
<D:error xmlns:D="DAV:" xmlns:m="http://apache.org/dav/xmlns" xmlns:C="svn:">
<C:error/>
<m:human-readable errcode="160024">
The version resource does not correspond to the resource within the transaction. Either the requested version resource is out of date (needs to be updated), or the requested version resource is newer than the transaction root (restart the commit).
</m:human-readable>
</D:error>
errcode match the standard SVN error codes, and on some cases 16006 (revision doesn't exist), the client will display the message from the server. In other cases, it appears to use just the errcode number and internal resource for that.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-07 19:56:58 CET