-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Closed
Labels
Bugthing that needs fixingthing that needs fixingNeeds Triageneeds review for next stepsneeds review for next stepsRelease 8.xwork is associated with a specific npm 8 releasework is associated with a specific npm 8 release
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
When running npm install there is a request for the json packument. In this request there is a Authorization header present with the token-value defined in ~/.npmrc:
//my.registry/:_authToken=<token>
But when requesting the tarball, using the tarball-url found in the packument, the Authorization header is missing.
It should be possible to authenticate that the request comes from a source that has rights to the tarball. Otherwise the tarball is essentially public, only hidden by obscurity.
Are there any settings i can change to make sure the Authorization header is present in the tarball request?
Expected Behavior
Authorization header should be present in the tarball request.
Steps To Reproduce
No response
Environment
- npm: 8.13.1
- Node.js: v16.13.1
- OS Name: macOS Monterey 12.3.1
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixingNeeds Triageneeds review for next stepsneeds review for next stepsRelease 8.xwork is associated with a specific npm 8 releasework is associated with a specific npm 8 release