You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 26, 2023. It is now read-only.
Since the relase of Chrome76, me and several members of my dev team started noticing that we were getting huge amounts of requests blocked by CORS.
For example, the code editor on codepen.io couldn't auto-reload anymore.
After disabling our extensions one by one we noticed that Akamai Debug Headers was the cause of the issue.
Tested in Chrome Version 76.0.3809.100 (Official Build) (64-bit) on MacOS
Unsure if the problems are just related tothe Akamai headers themselves, or the way this extension sets them.
The text was updated successfully, but these errors were encountered:
niklasHagner
changed the title
Causes tons of CORS-issues in Chrome76
This extension causes resources to be blocked by CORS-policy in Chrome76
Aug 21, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since the relase of Chrome76, me and several members of my dev team started noticing that we were getting huge amounts of requests blocked by CORS.
For example, the code editor on codepen.io couldn't auto-reload anymore.
After disabling our extensions one by one we noticed that Akamai Debug Headers was the cause of the issue.
Tested in Chrome Version 76.0.3809.100 (Official Build) (64-bit) on MacOS
Unsure if the problems are just related tothe Akamai headers themselves, or the way this extension sets them.
The text was updated successfully, but these errors were encountered: