I have created a Maven composite mirror that contains both a local and a remote Maven repository. Using properties for artifact resolution works fine with artifacts from the local repository but breaks the resolution of any remote artifacts. Only when the property is removed from the URL the composite finds the artifact in the remote. Remote repositories should either completely ignore properties during resolution or behave the same as local repositories (in case the remote is also an Artifactory instance), i.e. artifacts are returned if they either have a matching property or none.
Example: https://artifactory.xxx/artifactory/composite-proxy;*branch=master*/com/github/tomakehurst/wiremock/2.25.1/wiremock-2.25.1.jar won't find anything whereas https://artifactory.xxx/artifactory/composite-proxy/com/github/tomakehurst/wiremock/2.25.1/wiremock-2.25.1.jar does. Interestingly the first URL also starts to work once Artifactory has cached the remote artifact.