Affects Version/s: 5.1.4
Fix Version/s: None
Component/s: Reverse Proxy Configuration Generator
The actual snippet generated by artifactory has two directive that brokes any npm request to scoped packages.
The first wrong directive introduced as regression in
The correct value (as declared in your guide here) is
this permit to understand correctly the request https://artifactory.acme.com/artifactory/npm-virtual....../myscope%2fmypackage, where requested package is @myscope/mypackage. If encode is enabled on the proxy the url will be https://artifactory.acme.com/artifactory/....myscope/mypackage and the search fails because it say that myscope is not a valid npm repository :\
The second missing options (days of debug to understand what was the problem) is nocanon at the end of ProxyPass directive.
Without this directive apache (tested on 2.4) mod_proxy attempts to re-encode (double encode) the URL changing %2F (the slash) to %252F (encoding percent to %25) and this cause the @myscope%252Fmypackage not found