I see it is fixed now. I thought up this work-around back in 2014, when NPAPI was phased out. Spotify and another large player came up with similar solutions.
Re:Developers don't understand CORS
by chrisfosterelli on Wednesday July 10, 2019 @03:26PM
(#20405517)
Totally. I do get the constraints and I imagine Zoom had similar thinking here. The image approach, although hacky, can even be secure as-is if they need it for backward-compatibility but it needs to check the headers and not honour requests with the wrong value.
I kind of like the ingenuity of the approach. Never occurred to me to use non-active content.
Re:Developers don't understand CORS
by smallnamespace on Wednesday July 10, 2019 @03:40PM
(#20405686)
It seems that the Chromium patches are from 2016, so presumably this would still break older Chrome users?
2016 is in the 50s, and this[1] claims that version <67 has single-digit usage share.
If for some reason that doesn't work for your app, the post also mention two secure alternatives: the native client can install a self-signed cert, or you can use a browser extension with the native messaging API. You touched on this too!
My point here is not the specific example solution -- there's lots of alternatives and yes it depends on the situation and browser support requirements. But NONE of them are a reason to allow requests from every origin.
[0]: https://bugzilla.mozilla.org/show_bug.cgi?id=903966
[1]: https://chromium.googlesource.com/chromium/src.git/+/130ee68...
[2]: https://github.com/w3c/webappsec-mixed-content/commit/349501...