Julia EvansFeb 3
what makes CORS hard to use?
Show threaddextercd

@b0rk I think people can get stun locked when they see request failed along with '200 OK' in the browser console.

On the flip side, when the service that you're doing CORS requests to goes down and returns 5xx errors, it often stops including the headers. This means there are *also* CORS errors in the console and makes people think that's where the issue lies and not the fact the service is simply down.

Feb 4 at 9:30pmWeb
Show threadJulia EvansFeb 4
@dextercd thanks, what browser is that? it's also interesting to me that part of the error is hidden (i guess the fact that it's a CORS error would display when you expand it?)
Show threaddextercdFeb 4
@b0rk This is Chromium on Arch. Yes, above this it also says the request has been blocked by CORS.
Show threaddextercdFeb 4
@b0rk This is what it displays in full