U
user2300868
Guest
I apologize if this has already been asked but I've done quite a bit of searching and have not been able to find a question that is similar to mine yet.
On my application I have a password change page that triggers if a person is a new user or had his/her password reset.
The issue is that once the user makes changes and hits submit he/she gets redirected to the main page. Now if the user spams the back button a few times to get to the password change page they encounter an expired page and they can hit refresh. Then the browser asks the user to retry to submit the data. This submit request is a POST and the original data that the user entered previously can be seen in the packet.
I've only been able to replicate this issue on IE so far..tried it on FF and Chrome but nothing there.
My question is, is there a way, using jQuery, HTML, WSS, or otherwise-- to prevent this POST from being resubmitted? My biggest concern is the packet with the data that can be seen.
Thanks.
Continue reading...
On my application I have a password change page that triggers if a person is a new user or had his/her password reset.
The issue is that once the user makes changes and hits submit he/she gets redirected to the main page. Now if the user spams the back button a few times to get to the password change page they encounter an expired page and they can hit refresh. Then the browser asks the user to retry to submit the data. This submit request is a POST and the original data that the user entered previously can be seen in the packet.
I've only been able to replicate this issue on IE so far..tried it on FF and Chrome but nothing there.
My question is, is there a way, using jQuery, HTML, WSS, or otherwise-- to prevent this POST from being resubmitted? My biggest concern is the packet with the data that can be seen.
Thanks.
Continue reading...