Chrome ERROR_TIMED_OUT in latest version

Viewed 961

We have an angular application (served using Tomcat web server) that makes "XHR" requests to "Express" (Node v14) server. Both the web server and app server are hosted on-premise. After updating Chrome from 101.x to 102.0.5005.63 (Mac) and 102.0.5005.61 (Win), we are seeing intermittent API failures in our web application. The "Status" in dev tools shows as "(failed)" for these "xhr" and "prefetch" requests. Console log says "net::ERR_TIMED_OUT". However there are no such intermittent errors when the API calls are made from Postman or from Chrome v102.x. I also tested in "Safari" and "Edge" and there is no error there. Can someone help here?

3 Answers

We were getting the same with an external website (Netlify) then making internal API calls. We 'fixed' it by enabling the policy:

Specifies whether to allow websites to make requests to more-private network endpoints in an insecure manner

As it looks to be a bug that they are patching hopefully that is a temporary work around.

Related