Best IT Recipes

Internet Explorer 11 disables "displaying intranet sites in compatibility mode" using a meta tag does not work

I have been working on an intranet website for more than 6 months whether I use the below html5 doctype and border compatibility meta tag to prevent Internet Explorer from emulating an older version of the browser, and it worked fine.

 <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8" /> <title>My title</title> <meta http-equiv="X-UA-Compatible" content="IE=EDGE" /> </head> <body> </body> </html>

The reason I do this is because the place I work uses a policy setting to enable compatibility viewing for all intranet sites, and this approach using the EDGE option worked in Internet Explorer 9.

Intranet site compatibility view setting

Over a month ago, I was upgraded to Internet Explorer 11, and the site was still working properly.

Today it stopped working as expected, I can’t say for sure, but I think that the policy that forces the compatibility view was not included in IE11, but now it is ... and since it was turned on, the compatibility meta tag no longer does that as expected, and this site starts in Enterprise mode, which emulates IE8.

Does anyone know how to fix this and force IE11 to be used on the intranet site when Enterprise Mode compatibility is applied? and cannot be disabled through browser settings?

EDIT

I just tried adding a custom header to my web.config, as explained in this answer https://stackoverflow.com/a/312618/

and it did not work for me. I am still getting the following message in the console of the developer toolbar

 HTML1122: Internet Explorer is running in Enterprise Mode emulating IE8.

It is as if version 8 is considered as EDGE when this intranet compatibility option is enabled in IE11.

This post: https://www.leapinggorilla.com/Blog/Read/1016/ie-ate-my-css---disabling-compatability-mode explains this well, I have not tried setting this header using code yet, and our users do not have access to change the settings of their browser .. none of the other changes have yet worked.

UPDATE

Please see my comment on this post about the difference between Enterprise mode and compatibility mode, because it is important.

+75
html html5 internet-explorer compatibility internet-explorer-11
Aug 28 '14 at 20:18
source share
9 answers

Make sure that:

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

is the first <meta> on your page, otherwise IE may not respect it.

Alternatively, the problem may be that IE is using Enterprise Mode for this website:

  • Your question mentions that the console shows: HTML1122: Internet Explorer is running in Enterprise Mode emulating IE8.
  • If you may need to disable corporate mode (or something like this ) or disable it for this website from the Tools menu in IE.
  • However, the corporate mode in theory should be overridden by the X-UA-Compatible tag, but IE may have an error ...
+73
Oct 20 '14 at 10:18
source share

This issue is usually caused because the website / intranet URL is located in one of:

  • List of Compatibility Modes
  • Internet Explorer Intranet Zone
    (with display of intranet sites in compatibility view)
  • List of Enterprise Modes

On corporate networks, these compatibility view settings are often controlled centrally through Group Policy. In your case, the reason for this is corporate mode.

IE 11 Enterprise Mode

Unfortunately, the installation of META X-UA-Compatible will not override .

For end users

Sometimes the only way for end users to override this is to press F12 and change the document mode under the emulation tab. However, this parameter is not constant and may return after closing the developer tools.

You can also try to exclude your site from the intranet zone. But the list of domains included in the Intranet zone is also usually controlled by group policy, so the likelihood of this work is thin.

To view the list of domains included in the intranet zone, follow the link:

Tools → Internet Options → Security → Sites → Advanced

If the list contains your subdomain and is inactive, you cannot override the compatibility view until its network administrator allows it.

You really need to contact your network administrator in order to allow the modification of the compatibility view settings in Group Policy.

For network admins

Downloading a website using the Open development tools (F12) often reports the reason IE is transitioning to an older mode.

All 3 settings mentioned above are usually controlled by Group Policy, although sometimes they can be overridden on user machines.

If Enterprise Mode is a problem (this seems to refer to the original poster), the following two articles may be helpful:

+13
Sep 04 '15 at 8:02
source share

For those creating an ASP.NET MVC project, make sure you add:

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

on the Layout page (template). I just spent two hours debugging and tweaking just to realize that I just added this meta tag to my child pages. As soon as I added it to my layout page, the browser loaded into EDGE mode.

+5
Jun 23 '15 at 17:50
source share

This is an old problem with some good information. But I just found that using FQDN disables compatibility mode in IE 9-11. Example. I have a compatibility issue with
http: // lrmstst01: 8080 / JavaWeb / login.do
but problems go away with
http://lrmstst01.mydomain.int:8080/JavaWeb/login.do
NB: .int is part of our internal domain

+2
Aug 03 '15 at 21:08
source share

The marked answer is correct. However, Pricey, you must keep an eye on this using the AD administration groups and the desktop. They misuse the site list in IE11 Enterprise Mode. Microsoft does NOT intend to use it for all intranet sites within the organization. This will spread the existing settings of “make all intranet sites in compatibility mode”, which is the scourge of promoting a corporate site around the world.

It is intended to be implemented as a “black list”, with several sites that actually require an outdated browser mode specified in the “Enterprise mode” list with the specified requirements for their rendering. Then all other sites in your organization are exempted from using Edge. The people in your organization who implemented it with all the intranets turned on for a start, did not fully understand how Enterprise Mode should be implemented.

+1
Apr 09 '15 at 6:04
source share

The question is a bit old, but I solved a very similar problem. We have several intranet sites, including one for which I am responsible, while others require a compatibility mode or they break. For this reason, the IE rules site by default supports compatibility mode on intranet sites. I update my things and no longer need it; in fact, some of the features I'm trying to use do not look right in compatibility mode. I use the IE-Edge meta tag like you.

IE assumes that websites without a fully qualified address are intranets and operate accordingly. With that in mind, I just changed the bindings in IIS to only listen to a full address, and then set up a dummy website that listened to an unqualified address. The second redirects all traffic to a fully qualified address, forcing IE to consider it an external site. The site displays correctly with or without the Intranet Compatibility Mode option.

0
Jan 09 '15 at 16:45
source share

Move it to the Trusted Sites zone by adding it to the Trusted Sites list or local setting. This will remove it from the intranet zone and will not appear in the Compatibility application. View.

0
Jul 14 '15 at 13:20
source share

Add the property below to the web.config file for IIS sites. This worked for me on my intranet on IE11.

 <system.webServer> <httpProtocol> <customHeaders> <clear /> <add name="X-UA-Compatible" value="IE=edge" /> </customHeaders> </httpProtocol> </system.webServer>
0
Aug 17 '16 at 2:31 on
source share

I solved this problem by redirecting the user to the FQDN of the server hosting the intranet.

IE probably uses the world's worst algorithm to detect "intranet" sites ... indeed, specifying server.domain.tld solves the problem for me.

Yes, you read it correctly, IE does not detect intranet sites by their private IP address, as, for example, any developer who has heard of TCP / IP would not make the host part of the URL, if it does not have a domain, the part should be internal.

It is scary to know that IE developers do not understand the basic concepts of TCP / IP.

Please note that this was the case of the BIG business client, and force them to change the GPO, because you are trying to move the Alps east by 4 meters, rather than collecting.

0
Oct. 16 '16 at 6:11
source share


More articles:


All Articles