In different unique environments one might require the use of additional HTTP response headers. HTTP headers could be used to utilize inbuilt browser features or other use cases for unique environments. These headers could include and not limited to X-XSS-Protection, Content-Type, X-Frame-Options ... etc
The information in this article is provided as is, and ongoing support on the solution is not provided by Qlik Support.
In order to use custom HTTP headers, QlikView needs to be installed with IIS. Using the default Web Server on its own will not work.
Installing QlikView with IIS (if you have it installed skip this step)
While installing QlikView you will be presented with a Profiles
page, it is important
to check:Full Installation, Single machine with IIS
Adding features in IIS
By default, it is not possible to have IIS provide with custom HTTP headers, we need to add the following features in order to utilize that functionality.
In Server Manager go to Manage -> Add Roles and Features
Navigate to “Web Server (IIS)” and check the following boxes as show in the image.
When done it will prompt you to restart IIS. Please do so.
Adding custom HTTP headers in IIS
Navigate to IIS -> Site -> Your Qlik Site -> Custom HTTP Headers
Here you can customize the HTTP headers you need.
QMC → Virtual Proxies → Default (Central) → Advanced → Additional Response Headers
Add additional HTTP response header(s) here.NOTE:
In this example we used “X-Frame-Options” here as an example. You can use whatever header you need for your deployment, including the one we used.
Once finished, click “Apply”.
Head over to your browser and reload the page. You should see the headers appear. If not, restart IIS.