Jfrog Artifactory 不适用于@types 的 NPM 包 (NPM organization/scope)
Jfrog Artifactory does not work with NPM packages from @types (NPM organization/scope)
我们在项目中使用 npm、bower 等 artifactory。现在我们想使用新功能 TypeScript 类型定义通过 artifactory 获取 npm 包作为 @types/jasmine (NPM organization/scope) 但是当我们尝试访问它时我们得到 http 400
$ npm install -g protractor
npm http 400 http://artifactory/artifactory/api/npm/npm-virtual/@types%2fjasmine
我们可以直接在 npm public 存储库上访问 link 但是。它不适用于人工制品。还是不支持吗。是否有解决方法或修复方法。
Npm 'slash' character encoding
By default, the npm client encodes slash characters ('/') to their ASCII representation ("%2f") before communicating with the npm registry. If you are running Tomcat as your HTTP container (the default for Artifactory), this generates an "HTTP 400" error since Tomcat does not allow encoded slashes by default. To avoid this error when using npm scope packages, you can override this default behavior by defining the following property in the catalina.properties file of your Tomcat:
org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true
我们在项目中使用 npm、bower 等 artifactory。现在我们想使用新功能 TypeScript 类型定义通过 artifactory 获取 npm 包作为 @types/jasmine (NPM organization/scope) 但是当我们尝试访问它时我们得到 http 400
$ npm install -g protractor
npm http 400 http://artifactory/artifactory/api/npm/npm-virtual/@types%2fjasmine
我们可以直接在 npm public 存储库上访问 link 但是。它不适用于人工制品。还是不支持吗。是否有解决方法或修复方法。
Npm 'slash' character encoding
By default, the npm client encodes slash characters ('/') to their ASCII representation ("%2f") before communicating with the npm registry. If you are running Tomcat as your HTTP container (the default for Artifactory), this generates an "HTTP 400" error since Tomcat does not allow encoded slashes by default. To avoid this error when using npm scope packages, you can override this default behavior by defining the following property in the catalina.properties file of your Tomcat:
org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true