Reimplement "latest" artifact URLs as 302 redirects, rather than client-side refreshes

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Fixed
    • 2.2
    • Component/s: Artifacts
    • None

      It is possible to navigate to an artifact from the latest build using a URL of the form:

      [base URL]/download/[project key]-[plan key]/artifacts/latest/[artifact name]

      At present, this is implemented by generating a static HTML file containing a client-side refresh.

      This has at least a couple of disadvantages:

      1. It does not work well with tools such as wget and curl, that do not make use of the client-side refresh; and
      2. It breaks if an artifact is subsequently deleted.

      We should instead dynamically generate a 302 Found response.

              Assignee:
              Unassigned
              Reporter:
              Adrian Hempel [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 12h
                  12h
                  Remaining:
                  Remaining Estimate - 12h
                  12h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified