On Sun, Dec 07, 2003 at 01:31:33AM -0500, Eric Jonas wrote:
>
> I'm sending this query to users instead of dev first, per the text
> suggesting what to do before adding it to the Issue Tracker.
>
> I wanted to set up a specific box to be my svn server for my project, and
> had an old alpha (!) lying around that seemed appropriate for the task. A
> fresh install of debian stable, and then I compiled svn (0.34), apache
> (2.0.48), and berkeleydb (4.0.14), and got everything set up.
>
> I then imported by repository, went though the ssl certificate dance, and
> then tried to connect from my client. http works just fine, but https
> (using both the debian 0.33 client and a custom-compiled 0.34 client, both
> on x86) chokes on some sections of the tree with :
>
> svn: RA layer request failed
> svn: REPORT request failed on '/soma/!svn/vcc/default'
> svn: REPORT of '/soma/!svn/vcc/default': Could not read response body:
> SSL error: illegal padding (https://soma.mit.edu)
>
> It's always on a certain file in the repository, and both http and file://
> methods can access it from either platform without problem.
Are there any errors in the server error_log?
Can you get a tcpdump/ethereal trace of the minimal checkout which
reproduces this, and make that available? e.g.
# tcpdump -s0 -w /tmp/trace.tcp port 443
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 7 18:34:37 2003