Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-11966

Support mmproxy for Bitbucket DC

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Data Center
    • None
    • 1
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      Problem Definition

      When using any reverse proxy eg. HAProxy, the client IP address is not logged in the access logs and we have to make changes to the proxy config to get that working by following https://confluence.atlassian.com/bitbucketserverkb/log-the-original-ip-address-when-bitbucket-server-is-behind-a-load-balancer-779171715.html

      When deploying mmproxy especially the golang port of mmproxy with a staging instance we were able to successfully pass the origin address through to Bitbucket and have it clearly displayed in the access log.

      Attachments

        Activity

          People

            Unassigned Unassigned
            sraj3@atlassian.com Sujay
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: