azure-storage-node: Refused to set unsafe header "user-agent" in version 2.9.0-preview
I’m using version 2.9.0-preview and while uploading I get Refused to set unsafe header "user-agent" in every chunk upload request. Seems like we are adding user-agent in safe headers from browsers as well. Do we need to remove them or do we have some other work around?
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 24 (10 by maintainers)
@ChristopherParo
FYI, there is a typescript client library based on new architecture being developed, we’ll update this thread when it’s available for public preview, it can support npm well.
Best Regards, Jiachen
I’m hitting this issue from Chrome 67 using the azure-storage-node browser bundle (via webpack) when attempting to upload. The upload still completes successfully but the azure storage node common infrastructure is attempting to override the user agent, which chrome prevents. This causes on flow effects in our automated testing environment which detects this error as a failed test.
Hi, All
JavaScript library version 2.10.101 will involve the change, and it’s under release. Will update further when it’s released.
Thanks, Jiachen
@daiict218
Review is done, and as comments, it’ll be merged after 2.10.0 releases. FYI.
Thanks, Jiachen