Consider an environment where the OS on which this needs to be installed only sees a jfrog artifactory server and has a proxy to check outside in rare cases.
The proxy is very slow so it is best to avoid using it.
The jfrog artifactory has a miktex mirror set up as a remote repository.
Installation flow
The compiled installer checks the mirror url if it matches any publicly listed url and it won't match any because it is an internal, mapped url and the installer will fail.
Proposal
Why is this url check so strict in the first place?
What would be the drawbacks of opening this option up a bit more? For example adding a --trusted-mirrors option or just not checking the viability at all so the proxy is not needed at all?
First of all this is not a general bug.
Context
Consider an environment where the OS on which this needs to be installed only sees a jfrog artifactory server and has a proxy to check outside in rare cases.
Installation flow
The compiled installer checks the mirror url if it matches any publicly listed url and it won't match any because it is an internal, mapped url and the installer will fail.
Proposal
Why is this url check so strict in the first place? What would be the drawbacks of opening this option up a bit more? For example adding a
--trusted-mirrors
option or just not checking the viability at all so the proxy is not needed at all?Submitting a MiKTeX problem report