‘Error 400 Bad Request’ returned for URL with spec... - Qlik Community

Jamie_Gregory · ‎2020-07-31

Hello Qlik Users!

It has been reported that URLs with specific characters are returning Error 400 Bad Request with ticket authentication and windows authentication (a type of ticket authentication). This issue is affecting the Qlik Sense April 2020 release starting with Patch 1 and the June 2020 track and is currently being investigated by R&D.

Currently, two scenarios have been identified to show the issue:

Using filters with the QRS API, for example:
GET /qrs/user?filter=(name+eq+%27user2%27)

This includes the REST connector or calling the API directly.
Using the Single Integration API with some spaces in the selection values, for example:

In this case, the %20 is provoking the error 400.

There is a work around that can alleviate the 400 error. If the user first logs in to a URL that doe not have those URL parameters and obtains a valid session on the Qlik Proxy service, then they will be able to access the problematic URL.

I will keep you all informed on the issues as R&D progresses through the investigation.

For more information, please see Qlik Sense: URL with specific characters return Error 400 with ticket authentication in June 2020.

Please let us know if you have any questions. If you found this blog useful, please give it a like! Also, subscribe to the Qlik Support Updates Blog by clicking the green Subscribe button.

Kind regards,

Qlik Digital Support

balaecquariaqli · ‎2020-08-12

Is solution found for this, facing same while accessing QvAjaxZfc/QvsViewClient.aspx.

High Priority Issue... Please update

ToniKautto · ‎2020-08-12

@balaecquariaqli this post refers to Qlik Sense uses cases where QRS API is used with filtering.

'400 Bad Request' in QlikView or other Qlik Sense use cases are not covered by this post, please look for other posts matching your issue or raise a ticket with Qlik Support.

Damien_Villaret · ‎2020-09-15

The fix has been released in the following version last week: June 2020 Patch 5 It will also be released in the following versions in a near future: April 2020 Patch 7 September 2020 Patch 1

Damien_Villaret · ‎2020-09-15

The fix has been released in the following version last week: June 2020 Patch 5 It will also be released in the following versions in a near future: April 2020 Patch 7 September 2020 Patch 1

qlikcorpmil · ‎2020-10-12

Hi,

This issue continues to occur in the September 20.

There is a workaround solution as https://support.qlik.com/articles/000098524 but it we still experienced this issue. Is there any alternative solution?

Damien_Villaret · ‎2020-10-12

Hello @qlikcorpmil

This issue is fixed in September 2020 Patch 1.

Did you install Patch 1 ?

The workaround in the article mentioned does not apply to this problem. Although the error message (Error 400) in the user interface is the same, the root cause is different.

Error 400 can happen for different kinds of reasons. If Patch 1 does not help solving the issue, then you could check the Proxy Audit logs (C:\program data\qlik\sense\log\proxy\trace\servername_audit_proxy.txt) which should show an error message when you get the error 400 in your browser.

Based on the error you find in there, you can leverage our support knowledge base and Qlik Community to find a solution to your problem.

If that doesn't help, please open a support case for further investigation on our support portal, as it may be a new issue.

qlikcorpmil · ‎2020-10-14

Hi Damien,

Thank you for response.

We completed to install patch as Patch2 today and saw it resolved.

‘Error 400 Bad Request’ returned for URL with specific characters in Qlik Sense June 2020