On Fri, Feb 18, 2022 at 5:52 PM William Muriithi <william.murii...@gmail.com> wrote: > > Hello, > > I have this setup: > - httpd-2.4.37-43 > - subversion-1.14.1-1 > - mod_dav_svn-1.14.1-1 > - openssl-1.1.1k-5 > > The svn on Rocky Linux that is accessible only over https (Apache) and > everything works fine with exemption of "svn mv" command. Below is a > series of commands on how to trigger the error. > > svn mv xyz.txt abc.txt > svn ci -m 'Renaming a dummy file for changes" > Adding abc.txt > svn: E175002: Commit failed (details follow): > svn: E175002: Unexpected HTTP status 502 'Bad Gateway' on > '/svn/pro/!svn/rvr/4748/abc.txt' > > However, a new file abc.txt will get committed without any problem. > > The problem seems to match a problem reported here. > https://community.opalstack.com/d/608-svn-unexpected-http-status-502-bad-gateway/3
That is a very common problem. It happens when the server is sitting behind some kind of load balancer or proxy that is terminating the SSL connection. The issue is that the svn copy and move commands use WebDAV HTTP methods. These include the HTTP "Destination" header and it needs to be rewritten by the proxy to change the https to http. Here is one example: https://stackoverflow.com/questions/2479346/502-bad-gateway-with-nginx-apache-subversion-ssl-svn-copy The answer will depend on the Proxy being used. Mark
