On Thu, Aug 15, 2013 at 10:30 AM, Lieven Govaerts
> On Wed, Aug 14, 2013 at 11:30 PM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
>> On Wed, Aug 14, 2013 at 12:05 PM, Felipe Alvarez
>> <felipe.alvarez_at_gmail.com> wrote:
>>> How do I enabled debugging in .subversion/config or .subversion/servers? It
>>> used to be something like "neon-debug" but that's no longer available since
>>> 1.8.1 (or 1.8)
>> As of 1.8 SVN only uses the serf library for http communication, and
>> no longer the neon library (before 1.8, both were part of svn, but
>> neon was the default library).
>> Unfortunately there is no runtime-switch (yet) to enable debug output
>> with svn+serf. There is already an open enhancement request for this
>> You can enable debug logging with serf by rebuilding (see ).
> A FYI to Johan: note that there are two levels of abstraction here:
> - serf: the http library that's now used instead of neon: implements
> the http protocol and sends/receives bytes over the network
> - ra_serf: the subversion ra module that uses serf to communicate with
> a mod_dav_svn module in an apache server via XML request/reply
> If there's an issue that looks like missing or corrupted data,
> connection or authentication problems then we look to the serf
> library. The logging you refer to is then a good way to start
> gathering info on what's going wrong.
> However in this case it seems that the communication itself is ok, but
> there's a potential issue in how ra_serf drives the communication
> (i.e. the content of the xml requests). Serf logging will not help
> here as it's a level too deep. A simple wireshark trace can help, once
> the exact reproduction recipe is known.
> (serf can also log request and reply output, even with https, but it's
> easier to use wireshark)
Ah yes, thanks. I will keep that in mind.
Received on 2013-08-15 20:58:06 CEST