i know the eap and jws images are supposed to autoconfigure the maven proxy settings if HTTP_PROXY/HTTPS_PROXY is set, not sure why it's not working for you.
@martin: I don't think so, the middleware images have their own logic for how proxies are configured, as noted in comment 3, this isn't the curl problem.
Since image works well with it's special settings, remove the testblocker keyword
> $HTTP_PROXY_HOST
> $HTTP_PROXY_PORT
> $HTTP_PROXY_USERNAME
> $HTTP_PROXY_PASSWORD
> $HTTP_PROXY_NONPROXYHOSTS