JiraLockedError page returns a HTTP 200, when it should be a 500 class error

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: High
    • Component/s: None

      NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.

      This was affecting two instances that monitoring marked as OK because the HTTP status code was returning OK.

      See attached screenshot. Frontpage has errors, HTTP status code is 200.

      This affects 107.10 atleast. It probably also affects 114.2 (although we haven't seen any instances exhibit this behaviour on 114.2 as it's very intermittant).

        1. oh-no-its-a-200.png
          138 kB
          metapoint
        2. jira-locked-error-not-500.png
          145 kB
          metapoint

              Assignee:
              Unassigned
              Reporter:
              Michael Rose (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: