Re: Error "mod_dav_svn close_stream: error closing write stream" using a write-through proxy

Guten Tag Nico Kadel-Garcia,
am Samstag, 15. August 2015 um 18:14 schrieben Sie:

> Why don't you just use svn+ssh, and stay out of using HTTPS at all?

I've considered that and in fact some of our customers already use SSH
inbound to our private server and access via svnserve and it works for
some, but not very well for others. All that SSH settings and key
stuff and dealing with company proxys and saving things user specific
in case of different admins and some use terminal servers with generic
users and some not and such is something I would like to avoid in the
future. I primary want transport security and there are some other
reasons to use mod_dav_svn as well:

* I want a read only mirror independently of our private server, which
  is sufficient for most customers
* Some customers want write access, though
* I don't want to give various people access to our internal network
  just to retrieve updates anymore
* I always liked the idea of browsing the repo using a browser and
  WebSVN e.g. is not maintained anymore, so I try other ways

svnserve using SASL looks like a better option to get transport
security for me, but doesn't provide the master-slave setup like
mod_dav_svn does. At least not that I know of...

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail: Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow