I want to launch the Microsoft Edge in IE mode by using server redirection, can some one tell how it works and how to use this XML tag "X-InternetExplorerModeConfigurable"
Related
My application uses IE=9 document mode thru X-UA-Compatible meta tag and some of application pages uses IE =5 as document mode. Our client moving from IE browser to Edge browser. Looks like edge browser doesn't support document mode defined thru X-UA-Compatible meta tag .Is there any way Edge browser can support IE5 document mode?
You can do it from the Edge browser side.
MS Edge (Chromium) browser comes with the IE mode feature.
IE mode on Microsoft Edge makes it easy to use all of the sites your organization needs in a single browser. It uses the integrated Chromium engine for modern sites, and it uses the Trident MSHTML engine from Internet Explorer 11 (IE11) for legacy sites.
You can configure IE mode by setting a group polices for the MS Edge browser.
Below is the list of relevant policies.
Configure Internet Explorer integration
I suggest you enabled this policy and set its value to Internet Explorer mode.
Send all intranet sites to Internet Explorer
With the help of this policy, all intranet sites will be loaded in the IE mode in the MS Edge browser.
Configure the Enterprise Mode Site List
You can create sitelist.xml and pass the file address in this policy. You can create the sitelist.xml file manually. If you are not familiar with the content of this file then I suggest you download the Enterprise Mode Site List Manager (schema v.2). By using this you can easily create a site list and save it to an XML file by following File-> Save to XML.
while creating the site list using Enterprise Mode Site List Manager, you can choose the desired document mode or enterprise mode.
Sample of site list file:
<site-list version="6">
<created-by>
<tool>EMIESiteListManager</tool>
<version>12.0.0.0</version>
<date-created>02/10/2021 01:33:56</date-created>
</created-by>
<site url="localhost">
<compat-mode>IE5</compat-mode>
<open-in>IE11</open-in>
</site>
</site-list>
After applying the above policies, I try to launch the test site.
You can notice that the browser is MS Edge. Page got loaded in the IE mode and page loaded in the IE 5 mode.
Further, you can try to refer to the policies and make the necessary changes according to your requirement and try to make a test on your side.
Reference:
Does Microsoft Edge support rendering in IE8 mode? Is there any solution for this?
Let us know if you have any further questions regarding this issue, I will try to provide suggestions for it.
I do not have access to change company policy that has enabled IE mode for intranet sites.
On one page used by our team, IE cannot be used. Using Edge in IE mode, the page does not work.
There is a 3 minute refresh built into the page with the tag:
<meta http-equiv="refresh" content="180" />
After the first refresh, it switches back to normal Chromium Edge mode, and everything works. How do I force this to load in Chromium Edge every time?
I could fix the page to work in IE, but that seems like a huge waste of effort.
<meta http-equiv="refresh" content="180" />
<meta http-equiv="X-UA-Compatible" content="IE=edge"/>
Can't reproduce the problem on my side, I have created a sample using the above meta tag, after refreshing, it will stay the IE mode or Edge mode.
Generally, there have three ways to enable/disable the internet explorer mode in the Microsoft Edge (Chromium) browser.
Users can enable the IE mode by applying the group policy setting.
Users can enable the IE mode by enabling the Edge flag in the MS Edge Chromium browser.
Users can enable the IE mode using a command-line switch.
If you don't have access to change Edge group policy, you could try to use the second and third method to enable the IE mode in Edge browser.
Users can enable the IE mode by enabling the Edge flag in the MS Edge Chromium browser.
(1) Open MS Edge Chromium browser.
(2) Enter edge://flags/ in the address bar and press Enter key.
(3) Find Enable IE Integration using Search flags search box.
(4) Select the IE mode option from the dropdown control.
(5) Restart the MS Edge Chromium browser.
Users can enable the IE mode using a command-line switch.
(1) Create a shortcut of the MS Edge Chromium browser.
(2) Then try to right-click on the shortcut and go to properties.
(3) Go to the Shortcut tab.
(4) In the target field, try to add --ie-mode-test after the path of Edge exe. make sure there is one space between the path and this argument.
(5) Click on the OK button.
Then, you could click the Edge shortcut (contains "--ie-mode-test") to open the website, click the Edge settings and more, in the More tools option, you could find the option to enable/disable IE mode.
Choose "Open sites in Internet Explorer Mode" or "Open sites in Edge Mode" to enable/disable IE mode. After that, the tab will stay in that status.
For this scenario, the answer was dreadfully simple: Just use another tag to force the browser to use latest IE version installed.
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
This also "Fixed" IE. It turns out the reason IE wasn't working was that intranet sites were using compatibility mode.
One remaining question is why Edge was switching from IE mode to normal mode after a refresh... Might be a bug?
The answer posted by #Zhi Lv - MSFT is outdated(there are no such flags in the newest builds) and thus irellevant. You should try using the latest Dev branch of the browser as they have fixed one bug regarding the IE Mode itself.
This question already has answers here:
Why does Microsoft Edge (formerly Project Spartan) prompt to open this website in Internet Explorer?
(4 answers)
Closed 7 years ago.
I have an application which contains some links in the footer. These links are of type .html and .aspx. Now if I set Microsoft Edge as the default browser (using default programs), then, when trying to open this links from my application, the .html links are opening in Edge, while .aspx links are opening in IE 11, even though Edge is my default browser. I am using the Microsoft Edge Preview version.
I even tried to update the .aspx association using Default Programs -> Set Association, but for .aspx page it is not showing Microsoft Edge in the list as a choice.
While the same case is working fine on IE11 on Windows 10 Preview version.
Be sure you have compatibility mode turned off and that you don't have any compatibility tags or user agent strings in the aspx pages your are linking to. Also, make sure you are using the correct and have the correct meta tag, .
We've been testing our applications on Edge for a while now and these are the two biggest issues encountered.
I am familiar with programming in Delphi stand-alone applications and web-server applications.
Is it possible to have a Delphi application that when launched gets the browser to handle its output? Without a server being between the user and the application.
The reason I would like to do this is because HTML CSS and so on provide a more familiar user-interface to most people.
You can not "let the browser handle its output" without any HTTP connection, so a local web server, then using regular URIs like http://localhost:888/myDelphiApp/FullURI.
What you can is to embed a Web Browser to your Delphi application, then provide the generated web content not via HTTP, but as local content.
You may use
THtmlViewer Open Source component - which I like very much;
Delphi Chromium Embedded;
WebBrowser Component.
All recognize CSS and HTML content.
I've just built a basic ASP MVC web site for deployment on our intranet. It expects users to be on the same domain as the IIS box and if you're not an authenticated Windows User, you should not get access.
I've just deployed this to IIS6 running on Server 2003 R2 SP2. The web app is configured with it's own pool with it's own pool user account. The IIS Directory Security options for the web app are set to "Windows Integrated Security" only and the web.config file has:
<authentication mode="Windows" />
From a Remote Desktop session on the IIS6 server itself, an IE7 browser window can successfully authenticate and navigate the web app if accessed via http://localhost/myapp.
However, also from the server, if accessed via the server's name (ie http://myserver/myapp) then IE7 presents a credentials dialog which after three attempts entering the correct credentials eventually returns "HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials".
The same problem occurs when a workstation browses to the web app url (naturally using the server's name and not "localhost").
The IIS6 server is a member of the only domain we have and has no firewall enabled.
Is there something I have failed to configure correctly for this to work?
Thanks,
I have tried the suggestions from Matt Ryan, Graphain, and Mike Dimmick to date without success. I have just built a virtual machine test lab with a Server 2003 DC and a separate server 2003 IIS6 server and I am able to replicate the problem.
I am seeing an entry in the IIS6 server's System Event Log the first time I try to access the site via the non-localhost url (ie http://iis/myapp). FQDN urls fail too.
Source: Kerberos, Event ID: 4
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/iis.test.local. The target name used was HTTP/iis.test.local. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (TEST.LOCAL), and the client realm.
After extensive Googling I managed to find a solution on the following MSDN article:
How To: Create a Service Account for an ASP.NET 2.0 Application
Specifically the Additional Considerations section which describes "Creating Service Principal Names (SPNs) for Domain Accounts" using the setspn tool from the Windows Support Tools:
setspn -A HTTP/myserver MYDOMAIN\MyPoolUser
setspn -A HTTP/myserver.fqdn.com MYDOMAIN\MyPoolUser
This solved my problem on both my virtual test lab and my original problem server.
There is also an important note in the article that using Windows Authentication with custom pool users constrains the associated DNS name to be used by that pool only. That is, another pool with another identity would need to be associated with a different DNS name.
Sounds like the new Loopback check security feature of Windows Server 2003 SP1. As I understand it, is designed to prevent a particular type of interception attack.
From http://support.microsoft.com/kb/896861
SYMPTOMS
When you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or IIS 6, you may receive an error message that resembles the following:
HTTP 401.1 - Unauthorized: Logon Failed
This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address.
Note You only receive this error message if you try to browse the Web site directly on the server. If you browse the Web site from a client computer, the Web site works as expected.
CAUSE
This issue occurs if you install Microsoft Windows XP Service Pack 2 (SP2) or Microsoft Windows Server 2003 Service Pack 1 (SP1). Windows XP SP2 and Windows Server 2003 SP1 include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name.
Workaround
Method 1: Disable the loopback check
Method 2: Specify host names
See http://support.microsoft.com/kb/896861 for details.
Edit - just noticed that you said you were seeing this from Client PCs as well... that's more unusual. But I'd still look to test one of these workarounds, to see if it corrected the problem (and if so, might indicate a problem with your DNS config).
It sounds to me as though you've done everything right.
I'm sure you are but have you made sure you are using 'DOMAIN\user' as the user account and not just 'user'?
IE7 only sends Windows credentials (NTLM, Kerberos) if it identifies the server as being on the Intranet. IE7 also added an Intranet zone lockdown feature - if you're not on a domain, by default no servers are in the Intranet zone. This was done to prevent zone-migration attacks.
To change this, go to Tools/Internet Options, Security tab, then click Local Intranet. You can then manually add servers that should be treated as Intranet, by clicking the Sites button, then Advanced, or tell IE not to automatically detect your Intranet and selecting the other checkboxes as appropriate.
I just encountered the opposite problem - my site authenticates externally but not locally.
I compared it to the sites we have working and the difference was that the site that failed to authenticate was using Windows Authentication.
However, other sites I work with (this is a dev server) tend to have Basic Authentication.
Not sure why exactly but this fixed it.
However, at the same time I noticed "Default Domain" and "Realm" settings.
I know it's very unlikely but could these perhaps help at all?