kfogel@collab.net wrote:
>Andy Helten <andy.helten@dot21rts.com> writes:
>
>
>>Any other suggestions, other than going back to CVS (which is becoming
>>my only alternative)? Should I upgrade to subversion 1.0.6 on the
>>server?
>>
>>
>
>Some random-but-not-completely-random ideas:
>
> 1. Turn off http-compression in ~/.subversion/servers
>
Assuming I did this correctly (set 'http-compression = no' in the
'[global]' section), this made no difference -- it failed exactly as
before in exactly the same place.
>
> 2. I can't remember, did you try svn:// access with svnserve instead?
>
I did not try this before. I just tried it and it worked fine. This is
useful in that it seems to point the finger to the HTTPS functionality,
however, I would rather not use the svn:// access method because I don't
want to create system accounts for those accessing this repository.
Any other ideas of how to trouble shoot the HTTPS/SSL problem?
Thanks,
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 29 21:55:36 2004