You ever go to jump on a webex and suddenly find they’ve blocked their own content? There’s this standard, Cross-Origin-Resource-Sharing. Its designed to prevent your application from leaking something somewhere. And, its a right PITA to implement.
It appears from the below that webex (here *.webex.com) might be struggling with it, and, sadly, has blocked themself.
Anyone else experience this? is this the 2020 equivalent of being late for class?
Access to font at 'https://akamaicdn.webex.com/pb/web/18.104.22.168/mc/ui/v3/css/fonts/CiscoSansTTLightOblique.woff' from origin 'https://cira-acei.webex.com' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header has a value 'https://ramosjosetrial.my.webex.com' that is not equal to the supplied origin.
Leave a Reply