HTTP: Gatling shouldn't resolve remote address when connecting through a proxy

After upgrading to Gatling 3.0.0 doesn’t seem to work with our proxy. I am trying to access our pre production environment, an external web page that can only be accessed from a small number of IP addresses (like our proxy). This did work in 2.3.1 but stopped working after i upgraded.

I have already tried to clear my DNS cache but this didn’t resolve the issue.

StackTrace:

java.net.UnknownHostException: "https://customer-pre-production.company.com/Application/Logon"
	at java.net.InetAddress.getAllByName0(InetAddress.java:1280)
	at java.net.InetAddress.getAllByName(InetAddress.java:1192)
	at java.net.InetAddress.getAllByName(InetAddress.java:1126)
	at io.gatling.http.resolver.ShuffleJdkNameResolver.doResolveAll(ShuffleJdkNameResolver.scala:33)
	at io.netty.resolver.SimpleNameResolver.resolveAll(SimpleNameResolver.java:81)
	at io.gatling.http.cache.DnsCacheSupport$$anon$1.resolveAll(DnsCacheSupport.scala:124)
	at io.gatling.http.client.impl.DefaultHttpClient.resolveRemoteAddresses(DefaultHttpClient.java:441)
	at io.gatling.http.client.impl.DefaultHttpClient.sendTx(DefaultHttpClient.java:338)
	at io.gatling.http.client.impl.DefaultHttpClient.lambda$sendRequest$0(DefaultHttpClient.java:247)
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:462)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:897)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.lang.Thread.run(Thread.java:748)

Http configuration:

val httpProtocol: HttpProtocolBuilder = http
       .baseURL(Properties.intranetURL)
       .warmUp(Properties.intranetURL)
       .inferHtmlResources(BlackList(Properties.blackList), WhiteList())
       .proxy(Proxy("proxy.company.local", 3128).httpsPort(3128))
       .noProxyFor("test325.company.local", "test078.company.local", "localhost")
       .acceptHeader("application/json, text/javascript, */*; q=0.01")
       .maxConnectionsPerHostLikeIE7
       .acceptEncodingHeader("gzip, deflate")
       .acceptLanguageHeader("en-US,en;q=0.5")
       .userAgentHeader("Gatling/3.0.0")

[slandelle]

it would be great if you throw some light when this new version will be out?

Most likely mid-December

[mailtoshrb]

@slandelle Thanks for the update, we installed both old and new versions in the same server and somewhere it was referencing to old version so seen above exceptionsc(resolved it now). We have workaround for now for proxy redirection and will wait until gatling 3.0.2 release, it would be great if you throw some light when this new version will be out?