This doesn't seem to work at all, at least for me.
First, the test claimed that my connection suffers from isp header injection but didn't actually indicate which headers my isp might be injecting, or even what the consequence of thus is.
Second, it claimed I am using my isp DNS, which is not correct.
I agree with you, and especially identify with the last sentence. However, I’m fed up with Apple and Google, and any alternative that doesn’t tie me to Google and has all functioning hardware and usable 5G or at least LTE with reasonable specs is a major win in my book. I’ve preordered the FLX1s. The FLX1, which is no longer in production, had a replaceable battery, but lack of a replaceable battery or non-pure Linux in an alternative phone certainly isn’t going to keep me chained to Apple or Google.
CORS doesn’t protect you from anything. Quite the opposite: it _allows_ cross origin communication (provided you follow the spec). The same origin policy is what protects you.
Are you referring to the 30 second quip or the generic non-response?
> Asked whether Dell has any financial data that suggests working from the office leads to better productivity or results, a spokesperson said, "We continually evolve our business so we're set up to deliver the best innovation, value and service to our customers and partners. That includes more in-person connections to drive market leadership."
I honestly can't believe how unreliable Github is. Outages are commonplace. It boggles my mind how nothing has been done to address the reliability regressions that have been creeping in ever since MS took over.
Caution to anyone who clicks this link: mute your speakers first, or else you'll have to deal with blaring obnoxious music via an auto-play video that isn't visible without scrolling.
Not anything concrete, just memories of things not working, me looking at the JS console, seeing CORS errors, and seeing it work in Chrome, as I described. And the comment I replied to showed that it works differently between websites, namely:
if (host == "tripadvisor.com"_s || host.endsWith(".tripadvisor.com"_s))
m_needsRelaxedCorsMixedContentCheckQuirk = true;
That's a site-specific partial exemption from the same origin policy, as far as i can tell (without further context at the moment). Not a difference in how CORS works generally across Safari.
CORS is frustrating for a lot of developers as it can be tough to gain a complete understanding of the spec, and an understanding of the same origin policy is required. But implementation of the CORS spec(s) isn't notably different across modern browsers, now that IE is out of the picture. CORS was a real nightmare in IE. Microsoft even introduced an XHR cousin named XDR in IE10 to handle cross-origin requests, and it wasn't even a complete implementation of CORS.
I don't hate CORS from a developer perspective, I hate it from a user perspective, and from a broader "health of the web" perspective. Because, as I said, it works differently between browsers and it works differently between websites within the same browser. Mostly these differences just mean I have to use Chrome instead of my preferred browser.
Sounds like you’re projecting a bit. Lots of reasons one might be up at 6, other than hype or a “meme”. For me, it’s the only time I have to work out (with a job and smaller kids).
First, the test claimed that my connection suffers from isp header injection but didn't actually indicate which headers my isp might be injecting, or even what the consequence of thus is.
Second, it claimed I am using my isp DNS, which is not correct.