13 comments

The options do not look correct, please refer to https://docs.oracle.com/javase/7/docs/api/java/net/doc-files/net-properties.html .

-Dhttps.proxyHost=...
-Dhttps.proxyPort=...
-Dhttp.proxyHost=...
-Dhttp.proxyPort=...

You should add these in the VM Options field of the run/debug configuration.

0

Every single example of setting this up shows using the exact settings as the sample example I've used here. Doubt this is the problem.

0

Check that the actual JVM process running your code gets the correct options. It could be that you are running JUnit in forked mode and there is another JVM spawned for the test without the proxy options.

0

and just confirmed... changing those to include https.* didn't have an effect.

0

hmmm, here's what I've done.

Here's my run configuration for my test module:

 

and these are the vm options:

 

where else would/should they wind up? 

0

Check the command line in the Run console.

Add -Djavax.net.debug=all in the VM Options to see the detailed logging.

0

It may be also related to the code you are using to make HTTPS connection in the test. It may be bypassing the proxy or the library you are using needs explicit proxy configuration via API.

0

getting a bunch of these...
main, handling exception: java.net.SocketTimeoutException: Read timed out

trying to work back...

0

So, your proxy settings may be incorrect or fiddler is running on some different port.

0

well, per fiddler options, it's listening on port 8888 so that's not it.

 

0

so is this "normal" ?

System property jdk.tls.client.cipherSuites is set to 'null'
System property jdk.tls.server.cipherSuites is set to 'null'
Ignoring disabled cipher suite: TLS_DH_anon_WITH_AES_256_CBC_SHA
Ignoring disabled cipher suite: TLS_DH_anon_WITH_AES_256_CBC_SHA256
                                                            ...

0

and if I remove the vm options specific to what is recommended to use fiddler, I get the same java.net.SocketTimeoutException: Read timed out messages.

0

so most likely a red herring here..

0

Please sign in to leave a comment.