Nexus Repository Manager 3.x central-maven proxy edits pom to match https instead of http and produces Warnings

Our maven-central proxy edits every pom.xml file to match https instead of http.

For instance:

http ://www.apache.org/licenses/LICENSE-2.0
changes to
“https ://www.apache.org/licenses/LICENSE-2.0”

< <project xmlns=“http ://maven.apache.org/POM/4.0.0”…
changes to :
< <project xmlns=“https ://maven.apache.org/POM/4.0.0”…

The builds are still a success but we still need to find out what is causing this URL replacement to stop the checksum warnings, which is preventing us from specifying a build-fail on wrong checksum policy.

Warnings:

> [INFO] Downloading from nexus: 
.../nexus/content/groups/public/org/apache/maven/maven-plugin-api/3.0.5/maven-plugin-api-3.0.5.pom

> [WARNING] Checksum validation failed, expected 2f55191dd97251cff704810574175106e9e1855c but is 0a151d14f99c13d9783a47f4e11664ec5277e0fb from nexus for
..../nexus/content/groups/public/org/apache/maven/maven-plugin-api/3.0.5/maven-plugin-api-3.0.5.pom

> [WARNING] Could not validate integrity of download from
 .../nexus/content/groups/public/org/apache/maven/maven-plugin-api/3.0.5/maven-plugin-api-3.0.5.pom: Checksum validation failed, expected 2f55191dd97251cff704810574175106e9e1855c but is 0a151d14f99c13d9783a47f4e11664ec5277e0fb

Nexus Repo absolutely does not rewrite the contents of pom files. It sound like there is something on your network outside of Nexus that is doing this.

Regards,

Rich