Redirect in response to POST transaction
Automatic redirection of a POST transaction to GET is entirely feasible, using status 302 or 303. Although the specification for 302 mandates clients to verify the redirection with the user, this mandate seems to be generally ignored.
Note, that if you’re doing an HTTPS -> HTTP redirect, the only way not to get an ‘insecure’ warning message seems to be by using a meta refresh. Going through a lynx shows that this is what Yahoo! does (interesting stuff in the trace). Too bad I didn’t think to look through lynx an hour ago.