Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-1646

Implement rules to determine whether an artifact is to be downloaded or viewed in the browser

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 1.2.3
    • Artifacts
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      As a consequence of BAM-402, when a user clicks on a build artifact, it will always be downloaded, rather than displayed in the browser.

      This is not appropriate for all artifact types.

      We should set the Content-Disposition header to "inline" for text, image, audio & video Content-Types, so that they are displayed in the browser, when possible.

            [BAM-1646] Implement rules to determine whether an artifact is to be downloaded or viewed in the browser

            AjayA added a comment -

            Hi Geoffrey,

            Sorry for the confusion, with Bamboo 1.2.3 we set the content-disposition to the default browser behavior - as per BAM-1646

            In doing this we discovered that, in some browsers (Firefox), the artifacts were not displayed inline due to the default browser behavior.

            We have now remedied this in Bamboo 1.2.4 - where we set the known common mime types to be displayed inline - please upgrade to the latest version of Bamboo for a fix.

            Regards,
            Ajay.

            AjayA added a comment - Hi Geoffrey, Sorry for the confusion, with Bamboo 1.2.3 we set the content-disposition to the default browser behavior - as per BAM-1646 In doing this we discovered that, in some browsers (Firefox), the artifacts were not displayed inline due to the default browser behavior. We have now remedied this in Bamboo 1.2.4 - where we set the known common mime types to be displayed inline - please upgrade to the latest version of Bamboo for a fix. Regards, Ajay.

            Geoffrey added a comment -

            Is this really fixed in 1.2.3? I see that BAM-1642 implies it affects 1.2.3, which matches our experience (we have 1.2.3 installed, and this is bugging us immensely).

            Geoffrey added a comment - Is this really fixed in 1.2.3? I see that BAM-1642 implies it affects 1.2.3, which matches our experience (we have 1.2.3 installed, and this is bugging us immensely).

            bmccoy added a comment -

            Hi,

            I have set the content-disposition header to use the default browser settings for any text or image types as well as application/xml types.

            Cheers,
            Brydie

            bmccoy added a comment - Hi, I have set the content-disposition header to use the default browser settings for any text or image types as well as application/xml types. Cheers, Brydie

              bmccoy bmccoy
              ahempel Adrian Hempel [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

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