It's funny - about a month ago there was a discussion here that you should be using the 303 redirect in response to a post. The discussion was here: http://new

It's funny - about a month ago there was a discussion here that you should be using the 303 redirect in response to a post. The discussion was here: http://news.ycombinator.com/item?id=2791663 http://news.ycombinator.com/item?id=2791663 In there, I commented (http://news.ycombinator.com/item?id=2792357 http://news.ycombinator.com/item?id=2792357) that I would recommend against 303 because of possibly broken proxies and mainly because browser were already doing the right thing in response to a 302. How wrong I was as we now have an instance where at least one browser is doing it the way the spec has probably intended for it to be handled. I would assume they are still handling 302 in response to a POST like every other browser but for 303 they are doing it the way the spec was initially worded. This is, IMHO, not an IE issue but an IE standards-compliancy-feature at least until somebody here tries whether it works as expected with a 303 status code. If it does and you want it to work differently with a 302 code, then it's probably your turn to get the spec fixed :-)