Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Using the SDK in Chrome generates lots of 'Refused to set unsafe header "accept-encoding"' errors' #246

Closed
pimterry opened this issue Dec 20, 2016 · 1 comment
Closed

Using the SDK in Chrome generates lots of 'Refused to set unsafe header "accept-encoding"' errors' #246

pimterry opened this issue Dec 20, 2016 · 1 comment

Comments

@pimterry
Copy link
Contributor

Might well be a resin-request issue, haven't investigated yet. Reproduced by just running the test suite in Chrome, where almost every test hits this at least once.

Doesn't break anything, but lots of noise, and we should fix it before we put the SDK to use in the UI.
@pimterry
Copy link
Contributor Author

Resin-requests issue, moving to balena-io-modules/balena-request#91

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pimterry