The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to use filter

Slavka Petrova
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 3, 2018

Hello,

We experience several problems with the filters in Jira 6.3.1. When we open some filter the filter field is missing. Also we are not able to save a new filter.

The end points

/rest/api/2/filter/favourite?expand=subscriptions[-5:]&_=1533276806440
/rest/api/2/filter/29509?expand=subscriptions[-5:]&_=1533276806673

return 400 without response body. On the server side there are not any errors.

This is the screenshot with the problem:

search.PNG

 

Could you advise how to fix the issue?

Thank you,

Slavka Petrova

 

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Slavka Petrova
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 6, 2018

Hello,

After the investigation we have found that the issue appears because of new Tomcat version :

 

The new behavior of Tomcat is an intentional fix for https://bz.apache.org/bugzilla/show_bug.cgi?id=62273 . With this they make Tomcat completely compliant with RFC7230 (https://tools.ietf.org/html/rfc7230) – The HTTP 1.1 spec and RFC3986 (https://tools.ietf.org/html/rfc3986) – the URL syntax spec. Previously Tomcat had some of the requirements of these specifications relaxed.

 With the new change Tomcat expects all of the characters, which should be url-encoded according to the specifications, actually to be url-encoded.

 

Question now is if there the JIRA version where such Tomcat behavior  is fixed?

Thank you,

Slavka Petrova

Andreas Stenius
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 28, 2018

In the tomcat configuration for the connector, there should be support for a relaxedQueryChars configuration option, as described here http://tomcat.apache.org/tomcat-8.5-doc/config/http.html#Standard_Implementation that you can add.

Originating from this issue (which I found from your link: https://bz.apache.org/bugzilla/show_bug.cgi?id=62273#c20 )

Andreas Stenius
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 28, 2018

Workaround detailed in the jira ticket: https://jira.atlassian.com/browse/JRASERVER-67974