When doing 303 redirects after a POST, RFC 2616 mentions adding a hyperlink in the body of the response (i.e. the POST's 303 response body, not the response of the subsequent GET on newly created resource).
10.3.4 303 See Other
The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. The 303 response MUST NOT be cached, but the response to the second (redirected) request might be cacheable.
The different URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
I have two questions about this:
Are there any implementations (browsers or otherwise) that make use of such a link in the body of a 303?
If adding a link to the body, what would the most appropriate link relationship be?
rel="self",rel="alternate"? Neither seems totally appropriate. I realize there may not be a standard link relation for something like this, and if that is the case, so be it.
1) I believe all common browsers will display the response for a POST->303, although this may not be the case for GET (see http://greenbytes.de/tech/tc/httpredirects/#t303body)