tedster - 2:23 am on Nov 9, 2012 (gmt 0)
Since the 302 bug of years ago, the handling of 302 redirects by Google is not strictly by protocol, which isn't cool for protocol freaks, but is for those on the receiving end of 302 redirects, because they're treated much closer to 301 'permanent' redirects than they were 'back in the day'.
Absolutely - and a very important observation for many areas of Google before anyone spends significant resources fixing a "problem" which is merely academic today and not really affecting search traffic.
I've recently looked at a couple sites where hundreds of thousands of CMS driven redirects were 302 that "should have been" 301. By strict rules, these sites should have created all kinds of trouble within Google, but Google compensated for the CMS mis-configuration and the sites are not having troubles because of their poor status code choice.