• Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Low Low
    • None
    • 1.0
    • None
    • None

      Hi all,

      If you are seeing an issue similar to this please refer to:
      http://confluence.atlassian.com/display/STASHKB/Wrong+git+Clone+URL+when+using+NGINX+Proxy

      as you are most likely not passing through the correct information from your proxy server to Stash.

      Cheers,

      Jason Hinch
      Stash Developer

            [BSERV-2535] Wrong git Clone URL when using a Proxy

            This is relevant, though. On the Tomcat connector in conf/server.xml, setting the scheme attribute to "https" and the proxyPort element to "443" successfully goads Stash into displaying the correct HTTPS URI.

            Mike Eldridge added a comment - This is relevant, though. On the Tomcat connector in conf/server.xml, setting the scheme attribute to "https" and the proxyPort element to "443" successfully goads Stash into displaying the correct HTTPS URI.

            This doesn't help when SSL terminates at the front-end proxy. I'm passing the X-Forwarded-Proto header to the backend, but Stash is still showing an HTTP clone URI. The hostname is correct. It is of note that the X-Forwarded-Proto header correctly sets the scheme to https with a Scalatra application we are developing behind this same proxy.

            Mike Eldridge added a comment - This doesn't help when SSL terminates at the front-end proxy. I'm passing the X-Forwarded-Proto header to the backend, but Stash is still showing an HTTP clone URI. The hostname is correct. It is of note that the X-Forwarded-Proto header correctly sets the scheme to https with a Scalatra application we are developing behind this same proxy.

              Unassigned Unassigned
              dfabretti Douglas Fabretti [Atlassian]
              Affected customers:
              1 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: