An attacker can just as easily follow a 302 as can a legitimate API
developer or user of Twitter. I don't understand why Twitter thinks
this is a solution to the problem. Please stop 302ing.

Thanks,

--
Kyle Mulka
http://twilk.com

Reply via email to