Skip to main content
Announcements
Global Transformation Awards! Applications are now open. Submit Entry
cancel
Showing results for 
Search instead for 
Did you mean: 
Red_O
Contributor II
Contributor II

400 "The http request header is incorrect" in dataconnections after upgrade to feb 2024

After upgrading from May 2023 patch 9 to February 2024 on our test environment, we can no longer access our data connections via the browser, but we can only access the data connections directly on the server. Our developers and users access qlik sense through a virtual proxy on the browser. It seems that the underlying URL to make a data connection no longer points to the virtual proxy, so we get 400 "The http request header is incorrect".

Our production environment does not have this problem (version may 2023 patch 9).

In the attachment I have added screenshots of the test environment and the production environment. In the developer tools of the browser you can see that the proxy reference is not there in the test environment, but it is in the production environment.

Is this a bug or could there be something else going on?

Labels (2)
1 Solution

Accepted Solutions
Red_O
Contributor II
Contributor II
Author

Issue was related to bug QB-25165 and is solved in Februari 2024 patch 3.

View solution in original post

4 Replies
Rajani_Patil11
Employee
Employee

Hello,
Could you please follow the suggestion mentioned in the below link:
https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-quot-Error-400-The-http-request-h...

Red_O
Contributor II
Contributor II
Author

Hi, 

Thanks but i think this is not the solution. Qlik Sense receives the head request otherwise Qlik wouldn't be reachable for us. It's seems to be only in dataconnections to a database or rest connection. The proxy configuration in our production and test environment are the same. Only when we upgraded our test environment to the februari release, this issue happend.

Ranganath_DR
Support
Support

Red_O
Contributor II
Contributor II
Author

Issue was related to bug QB-25165 and is solved in Februari 2024 patch 3.