[BUG] openapi-generator-maven-plugin in corporate proxy fails on http references

Description

I've beeing using openapi-generator-maven-plugin for a while on different versions up to 3.3.4. I have my API definition in a YAML file and I tried to use absolute references to make references to common or shared API "components" (or fragments) hosted on a dedicated repository and publicly accessible via http in order to reuse those components in several API definitions.

But it looks that the generator fails to reach these remote API components when I run it in a corporate network (relative references in the filesystem works on the other side). I've tried the same outside the work network and it works fine. So that's why I think the openapi-generator-maven-plugin don't deal properly with proxies. I must point that other maven plugins such as WGET:

<groupId>com.googlecode.maven-download-plugin</groupId>
<artifactId>download-maven-plugin</artifactId>
<version>1.4.1</version>

do work with the same network and setup, that's what I think it is not a Maven or network issue.

The result is that openapi-generator can't reach the referenced components via http and generation fails.

I'm using it to generate for Spring (interfaces and models only).

P.S. The maven is run by corporate Jenkins CI (but I insist that maven wget plugin works fine in the same setup)

openapi-generator version

3.3.4

Command line used for generation

mvn clean install

Start with the openapi-generator-maven-plugin entry point and reproduce the reported mvn clean install generation using an HTTP component reference through a corporate proxy. Compare its behavior with the working Maven WGET plugin; done means Spring interfaces and models generate successfully in the proxy-backed environment.