REST Connector - No Longer Accepting HTTPHEADER X-HTTP-Method-Override?

[jmcy2408]

Hi,

Using Qlik Cloud i have an analysis app which was reconciling user selection to a correct allocation based on business rules. No issues here.

I was the using the REST Connector (initially setup using the POST request) but utilizing WITH CONNECTION and HTTPHEADER "X-HTTP-Method-Override" "PATCH"  to update a field in our job management system with the correct entry.  This was live for over a year no issues, but just yesterday it has stopped working.

Our job management system is giving a error response 405 (method not allowed).  No change to our job management software, a standard PATCH request using python and postman both work so it is working as intended.  This is leaning me towards the REST connector is no longer accepting the override?

Has any one else came up against this issue?

Has anything changed with the REST Connector?

Thanks in advance for anyones input.

John

[hugo_andrade]

@jmcy2408 ,

Since the same PATCH call still works in Python and Postman, the easiest next step is to prove exactly what Qlik is sending now compared with those tools.

I’d start by pointing the REST call to a request inspection service like RequestBin or Beeceptor, then compare:

• method

• headers

• body

If Qlik is no longer sending the override header in the way the API expects, that should show up quickly.

If you see different results, I would open a support ticket with Qlik.