Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > IIS handler mapping requirements

IIS handler mapping requirements

Table of contents

Updated: May 4, 2018

Overview

This article lists the file extensions that IIS must allow in order for Orion Platform products to function.

Environment

NPM 12.2

Detail

For the Orion Web Console to function, the IIS handler mapping must allow the following file extensions:

  • Pages - .aspx, .html, .htm
  • Services - .asmx, .ashx
  • Resources - .js, .css
  • Images - .ico, .gif, .jpg, .png
  • Docs -  .pdf, .txt
  • Fonts -  .svg, .woff, .woff2, .ttf
  • Import samples - .csv, .xls
  • No extension - "." (files with no extension)

 

For Handler Mappings, the IAO must document and approve all allowable file extensions the website allows (whitelist) and denies (blacklist) by the website. The whitelist and blacklist will be compared to the Handler Mappings in IIS. Handler Mappings at the site level take precedence over Handler Mappings at the server level.

 

Last modified

Tags

Classifications

Public