Hi, lately we started proxying our Jira instance using Apache and we noticed an error, when trying to create a new sprint. It says "error bad request". Here is a screenshot from chrome And here is Tomcat config .eu" proxyPort="443"/> I tried adding a certificate to jre cacerts - not helping. Do you have any idea how to fix it? Google says nothing relevant and I've been fighting with this problem for 2 days straight now.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

400 Bad Request when creating new sprint

Bartek Żółkiewski

Hi,

lately we started proxying our Jira instance using Apache and we noticed an error, when trying to create a new sprint. It says "error bad request".

575709037f

Here is a screenshot from chrome

6df4e33c18

And here is Tomcat config

<Connector port="8181" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" scheme="http"
proxyName="<ourdomain>.eu" proxyPort="443"/>

I tried adding a certificate to jre cacerts - not helping.
Do you have any idea how to fix it? Google says nothing relevant and I've been fighting with this problem for 2 days straight now.

Accepted answers

Andy Heinzer

Well your scheme parameter in Jira's server.xml should be https not http since that connector is clearly being used to allow traffic in from a proxy using SSL on port 443 to reach the Jira site.

If changing that and restarting Jira does not help, please try to recreate the problem and then click into the Response tab in the browser console. I'd be interested to see more details about why this request is failing, and that response might tell us more.

Also I'm interested to learn the full request URL, the Origin, and referer. Depending on the values listed in each of these might be able to tell us more about this problem.

Did you follow the steps in Integrating Jira with Apache using SSL?

All comments

Andy Heinzer

Well your scheme parameter in Jira's server.xml should be https not http since that connector is clearly being used to allow traffic in from a proxy using SSL on port 443 to reach the Jira site.

Also I'm interested to learn the full request URL, the Origin, and referer. Depending on the values listed in each of these might be able to tell us more about this problem.

Did you follow the steps in Integrating Jira with Apache using SSL?

Bartek Żółkiewski

Hi,

first of all - thank you for a quick response.
I changed the scheme in server.xml as you said to https, but unfortunately, it didn't help.
I also double-checked my configuration with the tutorial you linked - it seems like everything should work fine. Here are two screenshots you asked for - with a Response, Request URL, Origin, and Referer.

When accessing through the second connector, everything works like a charm.

Andy Heinzer

So those look good. I was afraid that the referer and origin URLs were different. In which case, you could encounter a cross site scripting protection explained in https://confluence.atlassian.com/kb/cross-site-request-forgery-csrf-protection-changes-in-atlassian-rest-779294918.html

But I don't think you are actually seeing that problem with the information I can see so far. Instead I want to know more about your Apache configuration here. I would expect that you followed the steps in Integrating Jira with Apache using SSL in regards to how Apache is configured to act like a proxy for jira. This guide explains how we expect both Jira and Apache to be configured in order to work together in this configuration.

The fact that everything works though another connector in Jira that likely bypasses this proxy makes me think the problem is in regards to the way that apache is configured.

Bartek Żółkiewski

Here is an http to https configuration and here is the proxy configuration.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

developer

apache

sprint

error