<font face="arial" size="2">Ooh, I like that. Nice, functional, and fully server-side.<br /><br />I assume they could just hit the Back button twice to get to the post page... but then again, you could get really clever and use location.replace for your GET... or would that still be considered part of the original POST request?<br /><br />Peter<br /><br /></font>
<font face="Tahoma, Arial, Sans-Serif" size="2">
<b>From</b>: Scott Reynen <a href="mailto:scott@randomchaos.com">scott@randomchaos.com</a><br /></font>
<br />On Aug 29, 2006, at 9:54 PM, Peter Lauri wrote:<br /><br />> The only real reason for this is that I do not want them to use the <br />> back<br />> button when the system have posted information, they then get the <br />> "page has<br />> expired" message.<br />><br />> How can I avoid this then? :)<br /><br />I solve this problem by redirecting POST to GET. When data is <br />posted, I generate the resulting HTML, save it to a database, and <br />immediately redirect to a GET request for the database record I just <br />created. The POST will not show up in the history, and the HTML <br />result of the POST request will only expire when I decide to remove <br />it from the database. Much less annoying than breaking the back button.<br /><br />Peace,<br />Scott