Hello,
Original-Nachricht
> What kind of trouble did you have with apache in the reverse-proxy
> mode? I've had that working and I think the only issue was that the
> relative path had to be the same as the actual target. That is you
> can't proxy http:/realhost/svn as http://
Hello,
first of all: I'm really sorry for the missing subject-line.
original message
> Will it stay with access on the repositories only or is it will your
> external devs need access to test infrastructure, documentation or
> whatever, too? In the latter case I would prefer set
Hello,
we run a subversion-server with apache and access it through https. Now we want
to grant also external developers access to our repositories.
As subversion-client we use subclipse via JavaHL under Windows. The https-Port
on the server is not reachable from any external network.
I've now
I think the reason is somewhere at the connection-specific configuration of
apache in interaction with the behaviour of the subversion-client (which may
has also connection-options...?).
I suspect the KeepAlive-Handing... it seems that the subversion-client closes
its connection between checkin
Hello,
we are using heavily "svn:externals" on our repositories.
A full checkout of a typical repository takes 20 Minutes. If I configure a
HTTP-Proxy in my subversion-client it takes only 13 Minutes...
We are accessing our repository over an apache via https - due to the
https-Connection no ca
