og
I'm often faced with users using the browsers history (fwd/rev-buttons) to navigate through pages. They use it instead of breadcrumb, hierachical or indexnavigation. It seems somehow natural to them.
In most cases, this is working. But if there where edits oder searches inbetween, the get unwanted results or dialogs.
Now, one thing is to train users not to use the browsers navigation. But another may be to aid using it. One major problem is resending form params, especially when using POST method in forms. This will trigger browsermessages telling that content is outaged and if user really want's to resend it.
One method to prevent this could be to simply use GET instead of POST. The browser will not be aware of any params and simply "open" the URL from histroy. I use this to make my searches histroy-safe and shareable (one user could send another user a resultpage by mail). The only drawback is a "ugly" URL, but it works.
Another method, i've read of is to use POST but let the server redirect on HTTP-level to a prerendered resultpage with its own ID. Thus, the POST will not remain in history, but the resulting page. This will make it shareable also. Question here is, how long this result should persist. Maybe it could be reorganized by normal cache-cleanup-routines?
My question is if this could be szenarios to include in DokuWiki to gain more user-acceptance?