Yes, the unique key mechanism as a decent security catch a decade ago.
Nowadays, not so much. The javascript disable event I may have to look at.
Won't keep the user from refreshing the page but the biggest issue
definitely is the double click. Appreciate that little tip.
***
Regards,
Joe W Holt
Sr Programmer/Developer
Jack Onofrio Dog Shows, LLC
405.427.8181
From: Nathan Andelin <nandelin@xxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
<web400@xxxxxxxxxxxx>
Date: 10/24/2014 01:43 PM
Subject: Re: [WEB400] Net.Data and session management
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxx>
I'm vaguely aware of the practice of generating a unique query string
parameter in URLs as a security mechanism. It also as the effect of
ensuring that users never see cached pages.
Regarding the problem of double-clicking on submit buttons and hyperlinks,
some developers use JavaScript to disable the event after the first click,
then re-enable it in the response.
Nathan.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/web400.
midrange.com
