You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a quite specific .NET network issue in Windows by using "localhost". On some machines it can take a couple of seconds (2 for example) during HTTP request to just connect to "localhost" which targets "127.0.0.1". But if you replace "localhost" with "127.0.0.1" the delay disappears. There is a long story regarding this issue. For Atata and WebDriver this issue reproduces for creating Chrome and Edge DevTools session by using WebDriver's GetDevToolsSession() method.
In order to overcome this issue for DevTools, we can replace "localhost" with "127.0.0.1" in "debuggerAddress" Chrome and Edge capability. But do that only if "debuggerAddress" port is obtained by IPv4.
The text was updated successfully, but these errors were encountered:
There is a quite specific .NET network issue in Windows by using "localhost". On some machines it can take a couple of seconds (2 for example) during HTTP request to just connect to "localhost" which targets "127.0.0.1". But if you replace "localhost" with "127.0.0.1" the delay disappears. There is a long story regarding this issue. For Atata and WebDriver this issue reproduces for creating Chrome and Edge DevTools session by using WebDriver's
GetDevToolsSession()
method.In order to overcome this issue for DevTools, we can replace "localhost" with "127.0.0.1" in "debuggerAddress" Chrome and Edge capability. But do that only if "debuggerAddress" port is obtained by IPv4.
The text was updated successfully, but these errors were encountered: