I don't think this will work well, because it will cause a double-fetch and double-render of the content. 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....

Though, I store the original and converted content in the db also, so I could avoid a re-fetch over port 80 at least, if I just do a SELECT from there...

But I'll have to do a pretty significant rewrite to avoid this from happening.

I'll have to think about this a bit more. Thanks for the suggestion.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.