New Reply

We have an issue with a (popular) non-url-friendly package name:


When requesting this package at the following url (as generated by NPM install) works:

And this doesn't:

When requesting the package in our (IIS hosted) ProGet server (names pacman) this doesn't work,

but this does:

We fixed this by using an IIS rewrite rule:

        <rule name="Proget npm Resolve UrlEncode">
            <match url="^npm/(.+)/(.+)$" />
            <action type="Rewrite" url="/npm/{R:1}/{UrlDecode:{R:2}}" />

Is smelling like either incorrect encoding/decoding at ProGets' part, do you agree?
Please note: we are not using the integrated ProGet server.

Product: ProGet
Version: 4.7.6

Looks related to:, but wasn't fixed in our case (we're running Version 4.7.6 (Build 5))

We of course can't reproduce it either...

Something before it gets to proget is munging the url. But I guess we'll just add a string.replace to unescape %2f in the URL. it might help, shouldn't hurt.

PG-763 in the next maintence release.

Answer Details