Re^2: Sending data to browser's URI field via POST

Once the form is submitted, the content is fetched, converted, and displayed to the user. If I then use a 302, I will end up doing an additional SELECT to pull the url out of the db with that unique hash, then fetch, convert, and render the content to the user again at that final redirected url....

Then don't send the redirect after fetching and rendering the data, do it instead, that way you only render it once.

We're not surrounded, we're in a target-rich environment!

Comment on Re^2: Sending data to browser's URI field via POST