- From: Michal Zalewski <lcamtuf@coredump.cx>
- Date: Sat, 13 Mar 2010 17:58:37 -0800
> As suggested above, could a header be required on compliant browsers to send > a header along with their request indicating the originating server's > domain? Yes, but it's generally a bad practice to release new features that undermine the security of existing systems, and requiring everybody to change their code to account for the newly introduced vectors. Theoretically, GET or OPTIONS should have no side effects, so DoS potential aside, they could be permitted with no special security checks. In practice, much of the Internet uses GET for state-changing actions; or nominally uses POSTs, but does not differentiate between the two in any specific way; plus, the problem of IP auth / Intranet probing remains. Bottom line is, opt-in is offered in several other places; and opt-out solution seems unlikely at this point, I would think? /mz
Received on Saturday, 13 March 2010 17:58:37 UTC