Safari, refused to set unsafe header
See original GitHub issueEcho example doesn’t work in safari. In chrome, firefox everything is fine.
Console log:
[Error] Refused to set unsafe header "Content-Transfer-Encoding"
(анонимная функция) (compiled.js:9396)
forEach (compiled.js:7638)
send (compiled.js:9395)
rpcCall (compiled.js:10597)
Echo (compiled.js:10825)
echo (33.33.33.31:34)
send (33.33.33.31:68)
dispatch (jquery-3.1.1.min.js:3:10321)
Issue Analytics
- State:
- Created 7 years ago
- Comments:5
Top Results From Across the Web
Ajax request: Refused to set unsafe header - Stack Overflow
Therefore I need to post a request to their endpoint with the Referer and the User-Agent properly set. This call should return an...
Read more >Chrome & Safari: Refused to set unsafe header "user-agent" #86
user-agent is actually no longer a forbidden header name per spec and this works fine in Firefox, so Chrome and Safari are not...
Read more >[SOLVED] Refused to set unsafe header Connection in Safari
Solved! For some reason the asynchronous variable in the open() call must be set to false for it to work in Safari, true...
Read more >Refused to set unsafe header Connection - Apple Community
So safari means you cant set the header "Connection". This is probably an safety feature or something, i don't know actualy. So what...
Read more >Refused to get unsafe header - TrackJS
The message describes a failed attempt to access header data from a network request. We discovered this error while working on a prototype...
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
We are actively working on this. Sorry for the delay. Should have a better update this week
Yes we are also aware of this and are working on a fix.