This page is an attempt to document some discrepancies between browsers and RFC 2616 (and its successor, RFC 2616) because the HTTP WG seems unwilling to resolve those issues. Hopefully one day someone writes HTTP5 and takes this into account.
For 301 and 302 redirects browsers uniformly ignore HTTP and use GET for the subsequent request when the initial request used an unsafe method. (The user is not prompted.)
Browsers handle relative URIs and URIs with invalid characters in interoperable fashion.
Browsers cannot support this header.
Requiring two interoperable browser implementations
To proof that RFC 2616 can be implemented there should be two compatible implementations in browsers.