Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
We get error {"message": "The requested resourcedoes not support http method 'POST'"}
when click delete button in "Items in queue"
How can we fix this problem?
Our environment:
Server 1: QlikView Server(12.10) + NPrinting on-demand-add(September 2018)
Server 2: NPrinting Server(September 2018) + NPrinting Engine(September 2018)
Server OS (Windows Server 2016 Standard)
We had a degrade in Sept 2018
API not worked with X-HTTP-Method-Override:PUT
Jira issue ID: OP-8050 Qlik NPrinting REST APIs were not working correctly. They responded only to POST calls. In this case, calls that used the override method. Only Qlik NPrinting September 2018 was affected
i thought it was only impacting API based solution but reading the notes carefully you may be getting exactly the same impact from initiating a DELETE through the supported on-demand capability (which also uses the API).
Can you upgrade to the brand new Nov 2018 edition ? It has a nice feature in the web console where you can monitor on-demand executions of all users.
Hi,
Do you have a proxy that stops the method override?
Are you logged in?
Did you accepted the certificates from the Web Console?
Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.
We had a degrade in Sept 2018
API not worked with X-HTTP-Method-Override:PUT
Jira issue ID: OP-8050 Qlik NPrinting REST APIs were not working correctly. They responded only to POST calls. In this case, calls that used the override method. Only Qlik NPrinting September 2018 was affected
i thought it was only impacting API based solution but reading the notes carefully you may be getting exactly the same impact from initiating a DELETE through the supported on-demand capability (which also uses the API).
Can you upgrade to the brand new Nov 2018 edition ? It has a nice feature in the web console where you can monitor on-demand executions of all users.