I’m currently working on an automation test suite where I use Selenium WebDriver to navigate a web application and retrieve configuration data from the browser’s local storage. I can successfully access the health endpoint of the application using Selenium WebDriver by performing a simple driver.get() request. However, when I attempt to replicate the same request using Java’s HttpClient, the request fails with a ConnectException or UnresolvedAddressException.

Details:

I use Selenium WebDriver to load a non-existent URL in the application, which then stores configuration details (such as service URLs) in localStorage. I successfully retrieve this configuration data from localStorage using JavaScript executed via the WebDriver. The configuration includes a service URL, which is then used to construct the endpoint for a health check.

Issue:

When I navigate to the health endpoint using Selenium (driver.get()), everything works as expected. However, when I attempt to send an identical request using Java’s HttpClient, I encounter exceptions like ConnectException or UnresolvedAddressException. It seems that the Selenium WebDriver can resolve the hostname correctly, but the Java HttpClient cannot.

Questions:

How can I extract all the necessary details from the Selenium WebDriver’s request (e.g., headers, cookies, resolved IP, etc.) to ensure that the HttpClient request is identical to the Selenium one? Is there a way to replicate the exact request that Selenium WebDriver makes using Java’s HttpClient? Could this issue be related to DNS resolution differences between the Selenium WebDriver environment and the HttpClient? How can I resolve this?

Any advice or code snippets on how to address this discrepancy would be greatly appreciated!

What did you try and what were you expecting?

I tried extracting the service URL from localStorage and using it to build the health check request with HttpClient. The request made by HttpClient was expected to behave the same way as the one made by Selenium WebDriver, but it fails with connection errors.

I’m looking for a way to extract all necessary details from the Selenium WebDriver’s request (e.g., headers, cookies, resolved IP, etc.) and ensure that the HttpClient request is identical to the Selenium one.

Questions:

• How can I extract all the necessary details from the Selenium WebDriver’s request to ensure the HttpClient request is
• Is there a way to replicate the exact request that Selenium WebDriver makes using Java’s HttpClient?
• Could this issue be related to DNS resolution differences between the Selenium WebDriver environment and the HttpClient? How can I resolve this?

Any advice or code snippets on how to address this discrepancy would be greatly appreciated!