NetTalk Central

Author Topic: Chrome and the next day...  (Read 1655 times)

Alberto

  • Hero Member
  • *****
  • Posts: 1846
    • MSN Messenger - alberto-michelis@hotmail.com
    • View Profile
    • ARMi software solutions
    • Email
Chrome and the next day...
« on: April 09, 2021, 09:05:50 AM »
NTWS
Users use it, suspend or turn off the PC and when they go the next time to Crome, it keeps the last tabs opened, they found this page, please see pic.
In English is something like
Confirm the resend of the form....
They need to refresh the page.
Then a popup appears asking to confirm and all goes ok.

This does not happen with the tabs opened with Twitter, or Google Calendar, etc
Why it is happening with NTWS?

Any way of aviod this?

PD:this happen too it I adda link to Facebook on the same tab and go back.
« Last Edit: April 09, 2021, 11:49:06 AM by michelis »
-----------
Regards
Alberto

DonRidley

  • Don Ridley
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 729
  • donaldridley2011@gmail.com
    • View Profile
    • Email
Re: Chrome and the next day...
« Reply #1 on: April 11, 2021, 06:02:06 AM »
I think this is a Chrome thing, not a NetTalk thing.
"Eliminate the impossible, whatever remains, however unlikely, must be the truth."

NetTalk 12.55
Clarion 11

Alberto

  • Hero Member
  • *****
  • Posts: 1846
    • MSN Messenger - alberto-michelis@hotmail.com
    • View Profile
    • ARMi software solutions
    • Email
Re: Chrome and the next day...
« Reply #2 on: April 11, 2021, 06:30:52 AM »
I dont thnk so because it does not happen with Twitter or Facebook, etc
-----------
Regards
Alberto

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11179
    • View Profile
Re: Chrome and the next day...
« Reply #3 on: April 12, 2021, 12:56:21 AM »
if the last request of the server is a POST then you get this when refreshing, since refreshing is "sending the POST again" - which is sometimes considered bad (like when making a credit card payment.)

Probably your best way around this is the client-side session manager. So the last request is a GET not a POST (assuming the session timesout).