Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Feb 6, 2023 2:22:11 AM
Sep 5, 2018 10:11:37 PM
HTTP Response Header exposes Microsoft-HTTPAPI/2.0 as the server source. An attacker could use this information to expose known vulnerabilities for the server source.
This header is included in the HTTP header by .NET framework, which means it can not be directly controlled by Qlik software.
The header is only added in Qlik software that runs in Windows environment, for example Qlik Sense Enterprise for Windows and QlikView Web Server.
There are two main approaches to removing this HTTP header;
Qlik Sense Enterprise on Windows, all version
QlikView, all versions
Qlik NPrinting, all versions
Hi @Sonja_Bauernfeind ,
is this article still relevant for qlik sense August 2022 Patch 5 on windows server 2019?
If so,how to proceed disabling the server header for WCF Services in Windows registry if the deployment is on a multi-node qlik sense site?
as the registry update usually need a server restart, do we restart from the rim nodes, or the central node when the registry is updated, or is there a specific step to follow?
Hello @Luck
This topic relates to the operating system itself rather than Qlik Sense, so the Qlik Sense Enterprise on Windows version is irrelevant in these situations.
You would need to make this change on whichever node you use to host the hub (so, the proxy nodes).
As for restarting, see How to restart the Qlik Sense Enterprise on Windows services
Rim nodes will not have all services installed. Rim node services can be stopped or started in any order after the central node has been stopped or started.
All the best,
Sonja