On Friday 09 September 2005 10:58, R. Mattes wrote:
> After reading the initial bug report I checked with my upgraded SVN
> servers (no client certs involved). "Fresh" checkouts seem to work
> flawless but checkouts from user accounts that had allready checked
> out from the server hang. Doing a '
On Fri, 2005-09-09 at 10:37 +1000, Adam Conrad wrote:
> Andreas Jellinghaus wrote:
>
> >Package: apache2
> >Version: 2.0.54-5
> >Severity: critical
> >
> >After upgrading 2.0.54-4 to 2.0.54-5 svn+ssl is broken:
> >
> >subversion client (e.g. checkout):
> >svn: PROPFIND request failed on '/svn/test
Hi Adam,
> Could you try, for curiosity's sake, setting "SSLVerifyClient none" in
> the main VirtualHost, and keeping the rest the same, and seeing if that
> makes a difference for you at all?
Done, no change at all.
Thanks for looking into this issue.
Regards, Andreas
--
To UNSUBSCRIBE, em
Andreas Jellinghaus wrote:
>On Friday 09 September 2005 02:37, Adam Conrad wrote:
>
>
>>I would like a tarball of your /etc/apache2/
>>
>if there is anything else I can do to help, please let me know.
>
>
Meh. Yeah, this is actually a neon or svn (not sure who) bug, where it
can't do renogot
Andreas Jellinghaus wrote:
>Package: apache2
>Version: 2.0.54-5
>Severity: critical
>
>After upgrading 2.0.54-4 to 2.0.54-5 svn+ssl is broken:
>
>subversion client (e.g. checkout):
>svn: PROPFIND request failed on '/svn/test'
>svn: PROPFIND of '/svn/test': Could not read status line: SSL error: ss
Package: apache2
Version: 2.0.54-5
Severity: critical
After upgrading 2.0.54-4 to 2.0.54-5 svn+ssl is broken:
subversion client (e.g. checkout):
svn: PROPFIND request failed on '/svn/test'
svn: PROPFIND of '/svn/test': Could not read status line: SSL error: sslv3
alert unexpected message (https:
6 matches
Mail list logo
