Daniel J. Cody wrote: > the problem, as demonstrated above, is that we're using the wrong > protocol version to test this out. in http 1.1 301 is a permanent move, > 302 is 'found'. in http 1.0 301 is temporarily moved and 302 is perm. No it isn't. 302 is "Moved temporarily" in 1.0, and "Found" in 1.1. Their meanings are the same, though. 301 and 302 have not been switched in between versions. But the browser support for all 30x responses is basically really crappy. I don't know of any major browser that doesn't interpret 302 as "go here. now.", though. <http://rfc1945.x42.com/#s9.3> <http://rfc2616.x42.com/#s10.3.3> /filip -- trained by sea lions.