1script - 3:11 am on Feb 12, 2008 (gmt 0)
I guess I am still not clear about why is this happening at all. 302 is supposed to be a temporary redirect. So, where is the logic in putting a temporary location in the place of the final and permanent one? Is this strictly a bug or is there any legitimate logic in Google's treatment of 302 redirects?