Easy Steps to Get your Web Site to Support IE8 in 5Mins


Put simply, IE8 running in standard rendering mode will not display sites created to support IE7 very well, based on new standards that IE8 is supporting around HTML and CSS formats. There are two ways to resolve this. The first is to re-write your web application to render IE8 correctly or the second option ( the best to choose first off ) is to instruct IE8 to run a certain site in IE7 emulation mode.

On a Per-site basis, site owners and administrators can include the following custom HTTP header to force Internet Explorer 8 to render Web pages like Internet Explorer 7:

X-UA-Compatible: IE=EmulateIE7

To add a custom HTTP response header at the Web site level in Internet Information Services 7 on a Windows Server 2008-based computer, follow these steps:

  • Click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.
  • Under Connections, double-click the server that you want, and then double-click Sites.
  • Click the Web site where you want to add the custom HTTP response header.
  • Under Web site name Home, double-click HTTP Response Headers in the IIS section.

    Note In this step, Web site name is the name of the Web site.

  • Under Actions, click Add.
  • In the Name box, type X-UA-Compatible.
  • In the Value box, type IE=EmulateIE7.
  • Click OK.

To add a custom HTTP response header at the Web site level in Internet Information Services 6 and earlier versions, follow these steps:

  • Click Start, click Run, type inetmgr.exe, and then click OK.
  • Expand the server that you want, and then expand Web Sites.
  • Right-click the Web site that you want, and then click Properties.
  • Under Custom HTTP headers, click Add.
  • In the Custom header name box, type X-UA-Compatible.
  • In the Custom header value box, type IE=EmulateIE7.
  • Click OK two times.
Per-page basis

Site owners and administrators can include the following special HTML tag after the <Head> tag on the page:

<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

The following example shows use of this Internet Explorer 7 compatibility mode tag on a per-page basis:

<html>
<head>
  <!-- Use IE7 mode -->
  <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
  <title>My Web Page</title>
</head>
<body>
  <p>Content goes here.</p>
</body>
</html>

 

For more information about the EmulateIE7 tag, visit the IEBlog Web site:

http://blogs.msdn.com/ie/archive/2008/06/10/introducing-ie-emulateie7.aspx

Comments (7)

  1. You’ve been kicked (a good thing) – Trackback from DotNetKicks.com

  2. wisemx says:

    <system.webServer>

    <httpProtocol>

       <customHeaders>

           <add name="X-UA-Compatible" value="IE=EmulateIE7" />

       </customHeaders>

    </httpProtocol>

    </system.webServer>

  3. steve says:

    Beg to differ.

    1.) This isn’t "New Standards", these are standards set 5,6,7 years ago that MSFT was too slow to follow.

    2.) Setting this header is only a *very* temporary solution.  Developers need to week out the IE hack code, and only serve it up to legacy versions of IE (e.g. IE6/IE7)

  4. neilhut says:

    5,6,7 years ago we had a very different browsing experience and you have to admit that the standards documentation led to lead to quite a lot of interpretation. The browser has come a long way in the last 3 years ( no thanks to the kinds of AJAX apps running within them ) and it is great that all the browser companies are working together around the standards and more importantly when there is confusion, to get consensus. For sure IE6/IE7 was no standards angel but the team has put a lot of work into IE8 make this the case.

    Lets make sure that the consumer get the best web site experience on your site. That is what it is all about.

  5. With IE8 Beta 2 ante portals people start talking more about the next major release of the Internet Explorer.

  6. News says:

    With IE8 Beta 2 ante portals people start talking more about the next major release of the Internet Explorer

  7. With the release of IE8 Beta2, I thought it might be interesting to pull together some useful tips for