You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Lutz Dornbusch <sv...@yogasurftech.de> on 2008/09/05 05:13:39 UTC

Re: problems with svn1.5 write-through-proxy

Derek Lindner wrote:
> Hi Lutz,
> I saw your  recent emails on svn-users about problems with write-through 
> proxies.
> 
> I'm having exactly the same problem as you, with the same setup.
> 
> Did you ever resolve the "Could not execute PROPPATCH" problem you had?
> 
> And have you confirmed that lock events are handled locally, and not 
> propagated?
> 
>  
> 
> Any info you have would be greatly appreciated. I'll pass along any 
> solutions I find as well.
> 
> Derek

Hi Derek,
Thanks, for reply and no, I didn't found a solution, however on my linux 
box same configuration worked. As I used my windows box again as slave 
the PROPPATCH error again popped up. So I think it is a weird Apache 
Windows Problem. Also interesting to note is that I installed the same 
binaries(!) of apache and svn on a windows 2003 server on a client and 
there the whole proxy thing was running after correcting some small 
errors in the httpd.conf I made before.
However the LOCK functionality is even on my linux working example 
reverse: I receive locks on my client, not proxied to the master.
I resync now the locks directory on my servers. I do not know if this is 
a good solution, I was told this should avoid some difficulties with 
stealing/breaking locks issues. But I didn't dived into it.

Greetings,
Lutz



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org