400 (Bad Request) Running JIRA through IIS7

Chris Sweeney August 22, 2012

I'm running JIRA through IIS7 following the instructions found here https://confluence.atlassian.com/display/JIRA051/Integrating+JIRA+with+IIS

Every time I do something in JIRA that would return a JIRA error message such as "Field is required" I instead get a 400 (Bad Request) back from IIS.

For example, when I try to create an issue and skip a required field when I click the "Create" button nothing happens, I get no message saying that the field is required. But when I look in the console in Chrome (This happens in all broswers btw) I see the following:

POST https://myjiradomain.com/issues/secure/QuickCreateIssue.jspa?decorator=none 400 (Bad Request)

If I fill out the issue fields fully I'm able to create the issue with no problems. The only difference between the two requests is that the content type of the request where the fields are not filled out is text/html and the request where the fields are filled out is application/json. I'm not sure if this is significant but I thought I'd mention it.

Any insight on this issue would be greatly appreciated.

1 answer

1 accepted

3 votes
Answer accepted
Chris Sweeney August 22, 2012

I found the solution to this issue here http://stackoverflow.com/questions/8346836/cannot-return-custom-http-error-details-remotely.

As the solution on stackoverflow mentions all I needed to do was add errorMode="Detailed" to the web.config (see below) that's in the folder you setup in IIS for JIRA.

<system.webServer>
    <httpErrors errorMode="Detailed" />
</system.webServer>

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events