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

Enable uploadarchive.allowUnreachable, or allow configuring it to be enabled



    • Suggestion
    • Resolution: Unresolved
    • None
    • Git Hosting
    • None
    • 0
    • 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.


      When using git archive --remote to retrieve a repository archive via SSH, the default behavior only allows using SHAs to request commits that are at the current tip of an existing ref. Even if the requested commit is reachable from an existing ref, the request still fails. This is documented in git upload-archive:

      In order to protect the privacy of objects that have been removed from history but may not yet have been pruned, git-upload-archive avoids serving archives for commits and trees that are not reachable from the repository’s refs. However, because calculating object reachability is computationally expensive, git-upload-archive implements a stricter but easier-to-check set of rules:
      1. Clients may request a commit or tree that is pointed to directly by a ref. E.g., git archive --remote=origin v1.0.
      2. Clients may request a sub-tree within a commit or tree using the ref:path syntax. E.g., git archive --remote=origin v1.0:Documentation.
      3. Clients may not use other sha1 expressions, even if the end result is reachable. E.g., neither a relative commit like master^ nor a literal sha1 like abcd1234 is allowed, even if the result is reachable from the refs.
      Note that rule 3 disallows many cases that do not have any privacy implications. These rules are subject to change in future versions of git, and the server accessed by git archive --remote may or may not follow these exact rules.
      If the config option uploadArchive.allowUnreachable is true, these rules are ignored, and clients may use arbitrary sha1 expressions. This is useful if you do not care about the privacy of unreachable objects, or if your object database is already publicly available for access via non-smart-http.

      As documented, uploadarchive.allowUnreachable allows requesting unreachable commits, but it also allows requesting reachable non-tip commits. Unlike git upload-pack, which has separate allowReachableSHA1InWant and allowAnySHA1InWant settings, git upload-archive only allows tip commits (the default) or all commits.


        Issue Links



              Unassigned Unassigned
              xguan Xiao Di Guan (Inactive)
              3 Vote for this issue
              6 Start watching this issue