News for hackers. Stuff that matters.
Re:Why do we have both CSRF protection and CORS? by LegionMammal978 on Sunday March 02, 2025 @02:07PM (#43233801)
Hotlinking <img>s from other domains has been a thing forever, as far as I'm aware, and that's the archetypical example of a cross-origin request. <iframe>s (or rather, <frame>s) are another old example. And it's not like those would've been considered a security issue, since at worst it would eat up the other domain's bandwidth. The current status quo is a restriction on what scripts are allowed to do, compared to those elements.
Re:Why do we have both CSRF protection and CORS? by IgorPartola on Sunday March 02, 2025 @02:38PM (#43234147)
By definition those do allow you to see the response so that’s not really what is being discussed.
Re:Why do we have both CSRF protection and CORS? by Muromec on Sunday March 02, 2025 @03:06PM (#43234473)
Not really. You as an application generally can't read across origin boundaries, but you can ask browser to show it to the user.