HTTP 400 errors observed in Jira server when integrated with IIS

Still need help?

The Atlassian Community is here for you.

Ask the community

This article requires fixes

This article has been Flagged for fixing. Use caution when using it and fix it if you have Publisher rights.

Problem

When attempting certain actions within JIRA, such as removing a status in the Workflow Designer screen, it fails with the response of a HTTP 400. This can occur with all sorts of different functionality within JIRA. Depending upon the Web Server being used, the error may be something like the below (this is IIS):

Diagnosis

Environment

  • Microsoft IIS is being used.

Cause

Microsoft IIS may be blocking PUT and DELETE web methods (or HTTP verbs). These are required by JIRA for the REST APIs to work, without them a large amount of functionality will fail. Alternatively you may be affected by  JRA-44424 - Getting issue details... STATUS .

Workaround

There are several workarounds to this case, however it is recommended to enable PUT and DELETE on the web server. Some of the workarounds:

  1. Add a secondary HTTP connector in server.xml and use that to connect to the instance - for example we describe this in Integrating JIRA with Apache in the configure Tomcat section.
  2. Have another proxy used for JIRA, for example nginx or Apache, as this does not block them by default.
  3. Serve JIRA on port 80 and connect directly to it, rather than IIS. This requires root on Linux and is not recommended, however is suitable for Windows.

Resolution

Enable PUT and DELETE on the IIS reverse proxy. There's several guides for doing so below:

Last modified on Sep 25, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.