Qlik Community

Qlik Connectors Discussions

Discussion Board for collaboration regarding Qlik Connectors.

Announcements
Uploads getting stuck in the virus scanner. We are investigating.
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Partner
Partner

Qlik Rest Connector - PUT towards QRS API

Hi

has anyone experience issues with PUT endpoints (QRS to be precise) and Qlik Rest Connector?

Im getting a 404 - not found for the qrs/app/{id}/replace endpoint even though i use a POST lib connection and a "with connection" including a HTTPHEADER "X-HTTP-Method-Override" "PUT".

The same statement works perfectly fine in Postman. I have previously used this Method-Override towards NP API but this was the first time i tried it against QRS.

Running QS Apr2019 and Rest Connector 2.11

10 Replies
Highlighted

Hi @blaise 

I have experienced the same with HTTPHEADER "X-HTTP-Method-Override" "PUT" or HTTPHEADER "X-HTTP-Method-Override" "DELETE". It just looks like HTTPHEADER "X-HTTP-Method-Override"  is not allowed towards QRS. It would be good to hear from R&D or support regarding this as there is nothing in help.qlik.com... 

@Eva_B - do you have any insights you could share or maybe pass this question to someone who may know the answer? 

So the question would be: Can we use rest connection in Qlik Sense script with PUT/DELETE methods on QRS endpoint. I am already succesfully using GET and POST methods with QRS to get tasks by name and trigger reload task...This is to exclude any configuration issues with get&post lib:// connections...

thanks and regards

Lech

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
Highlighted
Partner
Partner

Thanks @Lech_Miszkiewicz for your answer. I will contact Qlik Support

Highlighted
Support
Support

Hello @Lech_Miszkiewicz  / @blaise :

I apologize for my late response.

I can check on the question, however, have you tried the workaround described in the following Knowledge Article:

 
"When using Qlik Sense REST connector to connect to NPrinting APIs, the connector may show error “Failed to connect to server” or “HTTP protocol error 403 (Forbidden): The server refused to fulfill the request” , although the same API call works in web browsers or Postman.

According to NPrinting reference page at http://help.qlik.com/en-US/nprinting/June2017/APIs/NP%20API/, API users need to call method GET /login/ntlm to authenticate themselves first. This will create a cookie for subsequent calls in the same session. However, unlike web browsers or API tools like Postman, Qlik Sense REST connector does not save this session cookie automatically for subsequent calls.

A work-around is to manually save the cookie after the first authentication call, then add the cookie as a query header in the REST Connector configuration."
 
Please let me know if this is helpful as I used this article this week while working with a customer and we were able to successfully pull data.

Regards,
Eva
Highlighted
Partner
Partner

Hi @Eva_B 

Thanks for replying but your workaround concerns NP API, im having problems with QRS API.

Highlighted
Support
Support

Hello @blaise -

I apologize. Which version of Qlik Sense are you using?

I found a Defect in the Qlik Sense September 2018 release that is fixed with Qlik Sense April 2019.

There is a degrade on the X-HTTP-Method_Override header that was introduced in the September 2018 release.

Are you using April 2019 or newer?

Regards,

Eva

Highlighted
Partner
Partner

Yes, Im using Apr2019. I have also tried it with June2019 release with same result.

Highlighted
Support
Support

Hello @blaise - 

I saw you listed the version initially.

I'm getting some coffee now. 🙂

I will check if there are any known issues with QS April 2019.

Regards,

Eva

Highlighted
Partner
Partner

I've searched the release notes for Apr2019 for X-HTTP but didn't find anything. Do you have a JIRA issue id i can search for, or some other information about the bug?

Highlighted
Support
Support

Hello @blaise -

Please see the below link:

 
I realize the title states "NPrinting" but this was a Defect that was fixed in Qlik Sense.
 
Also, a colleague found Software Defect: QLIK-94359. This was found in Qlik Sense April 2019 and is fixed in Qlik Sense June 2019. I realize you tried both releases.
 
With QLIK-94359 there were 404 / 403 Errors.
 
It might be the best course of action to open a Support Case so we can further investigate.

Regards,
Eva