Nobody on this thread pointed out the point of the POST-redirect-GET pattern: to make sure the content displayed in the browser matches the URL in the address bar. When it doesn't, the user hitting reload or forward/back (on what appears to be a page displaying state, not the explanation of the result of a state change operation) might cause the POST action to happen again instead of just reloading the data you display when the POST is complete. If you value server CPU over site usability, by all means use any of the suggestions previously offered.
-Dale --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
