SVN - Unexpected HTTP status 502 'Bad Gateway'

csd

I am trying to make a branch on my Apache SVN repo and keep encountering:

svn: Commit failed (details follow):
svn: Unexpected HTTP status 502 'Bad Gateway' on '/repo/!svn/rvr/10022/trunk'

I believe this is due to SVN being behind a reverse proxy (ref)

If you are using Apache 2.0 or 2.2 for your subversion server, you need to backport mod_headers from the HEAD revision of Apache. Fortunately this is not very difficult for this particular module.

Subversion behind an Apache Reverse Proxy (includes instructions to resolve issue and a mod_rewrite workaround which looks promising)

sean

csd we're not using Apache 2.0 or 2.2, and we're not using Apache as a reverse proxy.

Your SVN repos are served via Apache 2.4 running behind a Nginx reverse proxy.

I've tested branching on my own test repo and had no problem, eg:

svn copy http://svn.domain.com/repo/trunk \
    http://svn.domain.com/repo/branches/newbranch \
    -m "new branch"

If this issue is ongoing for you then please email support@opalstack.com with all of the details so that we can look into it.

csd

I noticed that you used an HTTP URL for the copy. I encountered the error w/ an HTTPS copy, I tried again from an HTTP URL and it copied without issue. Specifics of this issue are linked below.

svn COPY 502 bad gateway over HTTPS

sean

csd Ok, I've reproduced this issue on HTTPS and it does appear to be the problem mentioned that the link you shared.

At this time we don't have a solution to make this work over HTTPS but I'll post an update here when we do.

If you need to use svn copy securely then you'll need to do that via svn+ssh, eg:

svn copy svn+ssh://user@opalN.opalstack.com:/home/user/apps/svn/repo/trunk \
    svn+ssh://user@opalN.opalstack.com:/home/user/apps/svn/repo/branches/newbranch \
    -m "new branch"

You could also do this locally on the server as the SVN app's shell user using file:/// URLs:

svn copy file:///home/user/apps/svn/repo/trunk \
    file:///home/user/apps/svn/repo/branches/newbranch \
    -m "new branch"

Note that you can do this without affecting your working copy since you can run svn copy outside of your wc. You'll still want to do svn up within the wc to pick up the new branch.

Hope this helps!