CHW-2310 ArtifactUnresolved
download refused: the path looks like a package artifact but names no package and version the proxy can judge, so it is not passed upstream; request the artifact by the path your package manager's …
Default message: download refused: the path looks like a package artifact but names no package and version the proxy can judge, so it is not passed upstream; request the artifact by the path your package manager’s metadata gives
HTTP status:403(client)
Reason:ARTIFACT_UNRESOLVED
Problem. A download returned 403 saying the path looks like a
package artifact but names no package. Cause. The path ends in an
artifact extension for the repository’s format (.tgz for npm, yarn and
bun; .whl, .tar.gz, .tar.bz2, .zip, .egg for pip; .gem and
.gemspec.rz for RubyGems; .jar, .war, .aar for Maven and Gradle;
.nupkg; .crate) but the proxy cannot read a package name and version
from it — for example gems/payload.gem,
lodash/-/express-4.0.0.tgz, or a wheel whose filename carries no
version. With no coordinate there is nothing to judge, so it is refused
rather than passed upstream. Sidecars (.sha1, .asc, .module,
.whl.metadata), indexes and metadata are unaffected. Fix. Request
the artifact at the path your package manager’s metadata gives. HTTP 403.