-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] "npm install" fails with private registry https://host/path/ but works with https://host:443/path/ #1180
Comments
Debug logs: Failure, using implicit port:
Success, using explicit port 443:
|
~/.npmrc (failure, implicit port)
~/.npmrc (success, explicit port 443)
|
@isaacs how can we find out if this is an NPM bug, or an Artifactory bug? |
We are hitting this as well, are you using nginx in front of your Artifactory as well? Also which Artifactory version?
|
Hi Josh, we're using Artifactory 7.2.1. |
@heidemn do you have a public link to that issue I could use? Searching their Jira returned nothing with that number |
@joshbranham no it's not a public issue. |
npm If your bug is preproducible on If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo Closing: This is an automated message. |
What / Why
It seems that NPM makes a difference between https://artifactory.ourcompany.com/artifactory/api/npm/npm/
and
https://artifactory.ourcompany.com:443/artifactory/api/npm/npm/
(URL redacted)
Only when using the explicit port notation with ":443", the "npm install" command succeeds.
When
Current Behavior
It only makes a difference for "npm install", "npm ci" & co (commands that download stuff).
Steps to Reproduce
Expected Behavior
References
The text was updated successfully, but these errors were encountered: