2 ms·
I'm willing to bet that this is due to some browser extension on the user's side messing with CORS headers. But too late, the outrage mob has already assembled.
by paxys 3y ago
I'm willing to bet that this is due to some browser extension on the user's side messing with CORS headers. But too late, the outrage mob has already assembled.
- kapp_in_life 3y agoI wouldn't be so sure, that its a user side issue since CORS is handled on the backend. That is in your server config, explicitly allowing https://secure.hulu.com https://secure.hulu.com to access https://www.hulu.com https://www.hulu.com as an example. That said its likely a bug and nothing nefarious. Not to diminish that this is a really severe issue that you should raise to customer support, who likely has ways of cancelling for you.