Attachment downloads return 200 success code on authentication failure

XMLWordPrintable

    • 3.13
    • Severity 2 - Major
    • Hide
      Atlassian Update – 04 December 2017

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.

      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 04 December 2017 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

      The attachment was not downloaded, yet a 200 status code was returned, and the resulting textual failure page was saved in place of the requested resource

      [root@atlassian18 lib]# wget -c "https://extranet.atlassian.com/jira/secure/attachment/19109/bamboo-labmanager-plugin-1.1-SNAPSHOT.jar"
--05:24:12--  https://extranet.atlassian.com/jira/secure/attachment/19109/bamboo-labmanager-plugin-1.1-SNAPSHOT.jar
Resolving extranet.atlassian.com... 63.246.22.47
Connecting to extranet.atlassian.com|63.246.22.47|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 927 [text/html]
--05:24:13--  (try: 2)  https://extranet.atlassian.com/jira/secure/attachment/19109/bamboo-labmanager-plugin-1.1-SNAPSHOT.jar
Reusing existing connection to extranet.atlassian.com:443.
HTTP request sent, awaiting response... 200 OK
Length: 927 [text/html]
Saving to: `bamboo-labmanager-plugin-1.1-SNAPSHOT.jar'

100%[=========================================================================>] 927         --.-K/s   in 0s     

05:24:13 (17.7 MB/s) - `bamboo-labmanager-plugin-1.1-SNAPSHOT.jar' saved [927/927]

            Assignee:
            Unassigned
            Reporter:
            David Cheney (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: