I switched nginx's proxy_pass to a new application server, but the behavior is strange only when accessing with Microsoft Edge.

Question

※I am using a translation, so please forgive me if there are any grammar inaccuracies.

※Information for each server and browser is as follows.

・Proxy server (nginx) placed in DMZ

・Server A　Existing server, Windows server2012, belonging to old domain ①

・Server B New server, Windows Server 2022, belongs to new domain ②

・Currently, domain ② is mainly operated, but domain ① is also available for use.

・Microsoft edge version 134.0.3124.83 (official build) (64 bit)

・Chrome version 134.0.6998.118 (Official Build) (64 bit)

・safari version 604.1

I'm using nginx with a proxy server on my DMZ.

I have "server A" on my internal network set to proxy_pass in nginx.conf, but I'm trying to switch to "server B".

When I changed the proxy_pass server name to "server B" and restarted nginx, it worked fine with Chrome, but I was now unable to log in to the web application with Microsoft Edge and Safari.

After correcting and verifying the proxy_pass syntax, I found the following:

・Normalize the location directive, set the DNS server IP of domain 2 in resolv.conf, set the DNS server IP of domain 2 in resolver in nginx.conf, replace server B with a variable like "backend_servers" in the set directive, and set "proxy_pass" in proxy_pass. http://$backend_servers/$1$is_args$args;", it was possible to access and log in to Server B from Safari. I was still able to access and log in to chrome.

・I can access the first login screen of application server B using Microsoft Edge. After entering the user ID and password and logging in using JavaScript, the screen does not move to the next screen and the error message "INET_E_RESOURCE_NOT_FOUND" is displayed.

・I further confirmed the behavior of Microsoft Edge in this state.

First, I checked the URL of the screen where the error message "INET_E_RESOURCE_NOT_FOUND" appeared, and found that

The correct name is “https://××××(public server domain)/location/_link.do”, but it is “http://××××(public server domain)/location/_link.do”.

I confirmed that it was changed to http.

・If l accessed the URL after login authentication, “https://××××(public server domain)/location/_link.do” in another tab while the error screen for “INET_E_RESOURCE_NOT_FOUND” of Microsoft Edge was open, I could access the application screen after login authentication.

Based on the above situation, I would appreciate it if you could tell me a solution to successfully access and log in to the new server B from Microsoft Edge.

Answer 1

Hi @M.R,

Thank you for your information. Since we know regular Microsoft Edge works well but IE mode does not work well on that page, it would be a good idea to remove the login page from IE mode site list if it does not impact user experience.

On the other hand, if you need to stick with IE mode, please consider the following suggestions:

1. Clear DNS cache. You can use ipconfig /flushdns in Command Prompt (cmd).
2. Clear IE cache. You can go to edge://settings/privacy --> Clear browsing data for Internet Explorer and clear up the cache.

UPDATE

You may also try clearing or disabling IE HSTS settings following these steps:

1. Open a Run box by pressing Windows key + R. Type regedit and press Enter to launch the Registry Editor.
2. Navigate to the following path:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl
   

3. Right-click FeatureControl, select New > Key, and name it FEATURE_DISABLE_HSTS.
4. Right-click FEATURE_DISABLE_HSTS, choose New > DWORD (32-bit) Value.
5. Name it iexplore.exe and press Enter.
6. Right-click on iexplore.exe, select Modify, set the Value data to 1, and click OK. Note: For x86 systems, save and reboot to apply changes. For x64 systems, continue below.
7. Go to:

      HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\Main\FeatureControl
   

8. Repeat the steps to create FEATURE_DISABLE_HSTS and iexplore.exe as before.
9. Double-click iexplore.exe, change the Value data to 1, and click OK.
10. Reboot your computer to apply the changes and check if the issue is fixed in IE mode.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Best Regards,

Shijie Li