Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. READ MORE

Setting Custom HTTP Headers in IIS for QlikView

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

Setting Custom HTTP Headers in IIS for QlikView

Last Update:

Aug 13, 2021 4:05:38 AM

Updated By:

Sonja_Bauernfeind

Created date:

May 15, 2019 11:30:43 AM

QlikView allows for the use of custom HTTP headers.

From version 12.30 onwards, this can be configured with the QlikView Web Server (see QlikView WebServer: Custom HTTP Header). For any previous versions, Microsoft IIS is required. 

HTTP headers are used to utilize inbuilt browser features or other use cases for unique environments. These headers could include and are not limited to X-XSS-Protection, Content-Type, X-Frame-Options ... etc

 

Environment:

QlikView 
Microsoft IIS

 

The information in this article is provided as-is and to be used at your own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

 

 

Using Microsoft IIS to set custom HTTP headers

This article assumes that Microsoft IIS is already installed and used as QlikView's webserver. For more information on how to install and configure IIS, see How to configure: QlikView and IIS.

Adding custom HTTP headers in IIS

  1. Navigate to IIS
  2. Go to Sites
  3. Select your Qlik Site (by default this is the Default Web Site)
  4. Open Custom HTTP Headers

    HTTP Resonse Headers.png

  5. Click Add... in the top right Actions menu

    HTTP Response Header ADD.png

  6. Add your required custom header

    In this example, we used X-Frame-Options.

    HTTP Response Header ADD value.png


     
  7. Click OK and then Apply 

 

Verify the custom HTTP Header

Open a web browser and navigate to the AccessPoint.

Enable the browser debug tools and review the Response Headers. In our case, we are using Google Chrome. the Response headers are currently set, as shown in the below image. 

verify custome header in debug tool IIS.png
 

Labels (1)
Contributors
Version history
Last update:
‎2021-08-13 04:05 AM
Updated by: