REST connector not sending cookie header

[JMohlmann]

Hi all,

One of the application that I have build for my company makes use of a REST connector to an internal server to get data. Validation of the user on that server is done by logging in using a username and password. The server creates for that session a cookie which can be used for all next GET request authentication.

Since the company updated to the June 2020 patch 2 still connector is not getting any data anymore. The validation with the session cookie fails. I can see that the part of collecting the cookie works. I can use that cookie in postman to reach the exact same endpoints and still get data. 

Next was to try and see what headers are posted to the endpoint. Using webhooks I posted one request from Qlik and 1 from Postman. The Qlik REST connector fails to post the 'Cookie' header. I have absolutely no idea why this fails. A ticket is already submitted to our own qlik support team but they also have no idea why the connector fails to post the cookie header since the update.

So, anyone an idea on why the cookie header is not posted? Other headers are posted.

Code example:

SQL SELECT
"Name"
FROM JSON (wrap on) "root"
WITH CONNECTION (
Url "https://webhook.site/testwebhook",
 HTTPHEADER "cookie" "$(sessionid)",  // Does NOT work
HTTPHEADER "Cookie2" "tst", // Does work
HTTPHEADER "DNT" "1" // Does work
);

[JMohlmann]

Apparently this might have something to do with  QB-1890, which only seems to focus on connecting to NPrinting but does affect everything that uses cookie headers in POSTS

[blaise]

any new on this @JMohlmann ? Have you been in contact with Qlik Support?

[blaise]

i just created my own api listener using node and express and can verity that Qlik Rest Connector June2020 (QS Desktop june2020 path3) does NOT send a request header if its called "cookie".

[JMohlmann]

There has been some contact with Qlik by the helpdesk of my company, but without any solution. 

I still need to explain the exact issue each time to new people (NOT sending request header with the name 'cookie'). So still no progress since the issue arose within my project 6 weeks ago.

[blaise]

I have filed a ticket to Qlik Support. Will update you on the progress @JMohlmann 

[JMohlmann]

Thank you, I will also update you if there is any progress on my side.

[blaise · Accepted solution]

confirmed as a bug by Qlik Support. Solved in QS Sep2020 @JMohlmann 

[JMohlmann]

Thank you very much Blaise, you are my hero. My company is working with Qlik on this for two month and we did not get any further than weekly being asked to explain the issue and show the logs. For the 6th time now..

Again thank you for understanding and examing the issues with only 1 post describing the issue.

[JMohlmann]

Blaise, do you have a support/ticket ID? This will help in aligning our internal efforts with this issue.