396 karma · joined September 10, 2014
edit: AI
skip the article, read the study at https://www.tandfonline.com/doi/full/10.1080/15502783.2026.2...
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.
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.
This is a great resource to gain a more comprehensive understanding: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
Do you have some examples of this?