Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Refused to set unsafe header "user-agent" in version 2.9.0-preview
See original GitHub issueI’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?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:24 (10 by maintainers)
Top Results From Across the Web
NWJS Refused to set unsafe header "User-Agent"
This api requires to set some user agent headers to work. Docs: enter image description here. I tried to set the headers this...
Read more >Browser Error: "Refused to set unsafe header 'User Agent'"
Must be a pretty recent patch. I had to clear the cache and quit out of chrome, then it automatically updated the version....
Read more >Refused to set unsafe header "User-Agent"
Compatibility issue between Chrome and Salesforce AJAX Toolkit error: Refused to set unsafe header "User-Agent".
Read more >LTS Changelog - Jenkins
Plugins have already been prepared to support the new version of Guava. Use ... (pull 4623); Add a Jenkins User-Agent header to outgoing...
Read more >Google Cloud release notes | Documentation
You can set the data retention limit for the offline store at the entity type level. Virtual Private Cloud. Preview: You can use...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@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.