Inconsistent Behavior of Microsoft Edge Behind Nginx Reverse Proxy

Question

Encountering an unusual issue with a current setup that involves an Nginx reverse proxy in front of several backend services. The environment works perfectly when accessed via Chrome, but Microsoft Edge exhibits inconsistent behavior.

Issue Details:

Browser Differences:

In Chrome, users experience a fully functional connection with no issues.

In Edge, the application either fails to load (connection timeout) or exhibits erratic behavior. After rebooting Edge, it works correctly for a short period, but the problem reappears after some time without configuration changes. Even opening both browsers on a new Windows laptop at the same time shows the issue in Edge.

Potential Causes: Given that the services behind the reverse proxy are accessed consistently via Chrome, this suggests that the problem might be related to how Edge interacts with the reverse proxy. There are suspicions that the issue could be related to differences in header handling or caching implementations between Edge and other browsers. The Nginx configuration appears standard, and it is used as the sole reverse proxy.

Has anyone experienced similar issues with Edge in a similar environment? Any insights or recommendations on troubleshooting steps would be greatly appreciated.