Canmove, confirm
1,537
edits
Changes
m
TODO: discuss why we decided this One similar approach to solving CSRF is better than just sending to send a "OKSame-Origin" or header with requests, setting its value to "FAILYES"if the referrer is of the same origin as the requested content and "NO" otherwise. While this one-bit approach can be effective against CSRF, it doesn't seem robust enough for deployment. Some sites post data cross-site when they own multiple domains. Additionally, a state-changing request might not be actually ''intented': an open redirect might be exploited, thus spoofing the content submission. Finally, a small amount of extra complexity (and request size) provides flexibility so this feature can be used not only as CSRF protection but also in other scenarios where knowing the origin of a request (and its redirect chain) might be handy.
→Advantage of more than one bit of data
=== Advantage of more than one bit of data ===
=== Selection of "null" token ===
