Never used Safari. I've examined the network packets though and there's some non-standard stuff going on when using Firefox. HTTP/1.0 302 Moved Date: Fri, 15

Never used Safari. I've examined the network packets though and there's some non-standard stuff going on when using Firefox. HTTP/1.0 302 Moved Date: Fri, 15 Jun 2007 15:40:40 GMT Location: item?id=28352 The Location header should have an absolute URI: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.30 http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.30 Also, you're using a 302 response to a POST request which, strictly speaking, means the browser should re-do the POST to the new URI in the Location header. Many don't, they do a GET instead. The 303 response can be used to say you insist they GET the new URI despite the original being a POST. http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.3 http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.3 Just noticed you're using HTTP/1.0. I've referred you to 1.1. You may wish to switch.