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 This is dated and I am not sure it's still valid. Has anyone seen this problem on a fairly recent svn server? Is there any way of resolving it if its still a problem with current svn? Regards, William
