[Compatibility]: Using private repositories

[arp-mbender]

Compatibility difference

I'm trying to set up kkRepo as a proxy for some on-prem DevOps artifact stores (Nuget). We are using a split-DNS for DevOps, so that requests from the internal network avoid the proxy.

This makes kkRepo throw an error:

Save failed: proxy.remoteUrl URL resolves to a private or local address: ADDRESS -> IP

Nexus handles such cases without issues.

Repository format

NuGet

Request or client command

POST internal/repositories

{"name":"devops-arp-projects","recipe":"nuget-proxy","online":false,"strictContentTypeValidation":false,"blobStoreName":"default","proxy":{"remoteUrl":"https://<URL>/ARP/_packaging/ARP.Projects/nuget/v3/index.json","allowedRedirectHosts":[],"contentMaxAgeMinutes":1440,"metadataMaxAgeMinutes":1440,"minimumReleaseAgeMinutes":null,"autoBlock":false,"remoteUsername":"arp\\tfs_renovate","remotePassword":"tfs_ren","remotePasswordConfigured":null,"remoteBearerToken":null,"remoteBearerTokenConfigured":null,"outboundProxyType":"","outboundProxyHost":null,"outboundProxyPort":null,"outboundProxyUsername":null,"outboundProxyPassword":null,"outboundProxyPasswordConfigured":null}}

Nexus behavior

I'm not in a position to re-create repositories in Nexus ATM. Suffice to say it's possible to create Nexus proxy Nuget repositories which point towards a local address.

kkrepo behavior

{
    "message": "proxy.remoteUrl URL resolves to a private or local address: devops.arpideas.pl -> 10.150.1.42"
}

Client impact

kkRepo is completely unusable in our scenario as a replacement for Nexus.

Reproduction notes

• 1.0.1
• proxy via Traefik in docker (I don't think it matters)
• target repository is accessible from kkRepo, but split-DNS reports it using a local IP (10.0.0.0/8).