Server configuration

Enable SVG MIME type

Certain webservers (e.g. IIS 6, 7.x) do not serve .svg files by default. If not already configured, you will need to add the image/svg+xml MIME type. Example configuration steps below:

Note: If this MIME type is not enabled, it can result in 404 "File Not Found" errors, or display issues with the GCWU and other themes headers.

IE Compatibility Mode

By default, IE displays Intranet web pages using Compatibility View (IE7 standards mode). This causes display and JavaScript problems with the WET template. To fix the problem, configure your web server to send the "X-UA-Compatible" "IE=Edge" HTTP header. Instructions for configuring IIS and for configuring Apache can be found on MSDN. The HTTP header ensures that IE 8, 9, and 10 use their most recent rendering engine, as opposed to Compatibility View.

Note: Setting the meta tag in the HTML document (<http-equiv="X-UA-Compatible" content="IE=edge" />) will '''not''' work for WET because of the conditional comments that configure the HTML element at the top of the page. These conditional comments force IE's rendering engine and the meta tag can't override it:

<!--[if IE 7]><html lang="en" class="no-js ie7"><![endif]-->
<!--[if IE 8]><html lang="en" class="no-js ie8"><![endif]-->
<!--[if gt IE 8]><!-->


It is possible for public facing, Internet webpages to display in Compatibility View because of user or administrator settings:

To troubleshoot display problems in IE 8 and above, use the F12 Developer Tools which are accessible by pressing F12 on your keyboard:

F12 Developer Tools showing a web page rendering in Compatibility View
F12 Developer Tools showing a web page rendering in Compatibility View

Fixing a web page that's displaying in Compatibility View can be accomplished by:

  1. sending the "X-UA-Compatible" "IE=Edge" HTTP header,
  2. disabling the user or administrator setting that is triggering Compatibility View, or
  3. configuring the group policy objects that control Compatibility View.
Date modified: