Well, the referer is set by the browser, so it is the browser that it not setting said HEADER.
I'm not sure it is mandatory to be set either [1], so it might be correct correct behaviour according to the spec, even though it's not what might be expected.
I agree with the logic for sure - My point is more about using the active verb "Removes", as if iOS 6 gets really close to passing the referer header, but removes it at the last second.
Maybe something like "omits" or "doesn't pass" would have been more true to the story - but I understand a writer needing to have a catchy title.
> However, it does seem like this issue is specific with Google. So I suspect it is either a bug on Google’s side (or a feature).
If this is what he suspects, why does he phrase the title as if it is something in iOS 6 that is causing the issue.