Hi, @atripp

Unfortunately, that upstream in private network and it is not accessible from internet. So it is impossible for you do debug using it directly. If you can provide me with some "debug" docker image of ProGet - I can try to reproduce problem and give you back some debug log it will create.

Hello!

I'm trying to evaluate ProGet as caching package repository for my company.
Currently I'm running Free Edition Version 6.0.10 (Build 1) in docker container.
Public Nuget feed I've created works perfectly without any issues.

But when I'm trying to deal with npm feed I've encountered a problem (probably bug in this ProGet version?).
Feed was created as public caching feed and connector is pointing to some "upstream" npm repository (not registry.npmjs.org)

Some packages (for example npm itself and it looks like all unscoped packages) are being installed correctly by npm client using that upstream directly, but fails to install through ProGet using the same upstream.
When inspecting traffic from Proget to upstream repository I've found that instead of http://upstream.address/npm/-/npm-8.5.4.tgz ProGet sends request http://upstream.address/npm/, and thus doesn't get expected package.
But some other packages - for example @types/jasmine (and it seems like all scoped packages) are installed correclty through ProGet and traffic inspection shows correct requests issued by ProGet like http://upstream.address/@types/jasmine/-/jasmine-3.10.3.tgz

Could you please help?