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

RE: E175013 svn diff failure (access forbidden) with 1.8.5 (regression)

From: Bert Huijben <bert_at_qqmail.nl>
Date: Tue, 18 Feb 2014 13:32:21 +0100

> -----Original Message-----
> From: Vincent Lefevre [mailto:vincent-svn_at_vinc17.net]
> Sent: dinsdag 18 februari 2014 11:18
> To: dev_at_subversion.apache.org
> Subject: Re: E175013 svn diff failure (access forbidden) with 1.8.5
> On 2014-02-17 16:39:56 +0000, Philip Martin wrote:
> > You might be able to use socat to debug the traffic. Run a socat relay
> > on the client machine, something like:
> >
> > socat -v TCP-LISTEN:9630,reuseaddr,fork
> OPENSSL:svn.apache.org:443,verify=0
> >
> > then run the client command, something like:
> >
> > svn ls http://localhost:9630/repos/asf/subversion
> >
> > and socat should dump the decoded SSL traffic. You may have to use
> > TCP6-LISTEN if the client cannot connect. Disabling compression with
> >
> > --config-option servers:global:http-compression=no
> >
> > makes it easier to see the body of the response.
> I had to use TCP6-LISTEN. And it seems that compression was not used
> by default. I've attached what I obtain after hiding potentially
> private information.


I reproduced this issue with a test added in r156926.

This behavior change (read "regression") was introduced with the diff/merge
cleanups that were released in 1.8.

Before 1.8 we would always root the diff on the directory itself when asking
for a directory diff, but this made it impossible to show that the directory
itself was replaced. For 1.8 we changed the behavior to look at the
directory from one level higher to allow noticing this replacement.

I'm currently running tests on a fix that detects the case where the parent
directory is not readable, and in that case restores the old behavior (of
not being able to show the directory replacement) while keeping the improved
behavior when you do have the necessary rights.

Received on 2014-02-18 13:33:04 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.