The portion that appears to be unique to iOS (maybe it's not), is the default cache policy for 301 redirects. Its in the HTTP spec: > This response is cacheab

The portion that appears to be unique to iOS (maybe it's not), is the default cache policy for 301 redirects. Its in the HTTP spec: > This response is cacheable unless indicated otherwise. - http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.2 http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10... I'm fairly certain without doing any research whatsoever, that most every browser on most every platform is vulnerable to this attack. It is literally a DNS cache poisoning and MITM. Nothing more. The difference with a mobile platform is you're dealing with apps that don't have a URL bar to tell you that you've actually on qwerty.info/paypal instead of paypal.com, which is an indicator of an attack.