Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-11686

Tunnel HTTP pushes to mirror through mirror instead of redirecting

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • UIS:
      47
    • Feedback Policy:
      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

      Pushing via a Smart Mirror over SSH vs HTTP has very different behaviour:

      • SSH pushes are tunnelled through the mirror to the upstream server
      • HTTP pushes redirect the client directly to the upstream server
        Customers may find the behaviour of SSH pushes desirable in all circumstances: it enables the upstream server to be firewalled off externally, so that developers outside of the VPN cannot access it but can still perform git operations; and in cases where the mirror and upstream server have high bandwidth direct links (e.g. if both are hosted on different AWS regions) pushing via a mirror can be faster than pushing directly

      Suggested Solution

      Instead of issuing a redirect for HTTP pushes to mirrors, tunnel them through the mirror similarly to how SSH is handled

      Workaround

      Use SSH only

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            dchevell Dave Chevell
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated: