Stop POST when refreshing the page

[clockon]

hi

does anyone know if there is a way to stop or know if a page is POST'ing from a page refresh? e.g. submit a page and save changes, press F5 and the page wants to POST again rather than GET. I have read a few different ways for other systems but wanted to see if anyone has come up with a neat way for RTC?

[D.Tkalcec (RTC)]

When writing a Web Server with RTC SDK, you have access to all the data received from Clients, and you have full control of everything you want to send back. The complete request content body received from a Client will be available to you through the TRtcDataServer(Sender).Read and ReadEx methods, with all the request headers in the TRtcDataServer(Sender).Request object. You just need to use these to access the data, then use the TRtcDataServer(Sender).Response object and the Write or WriteEx methods to send a response back to the Client. That's really all there is to using RTC.

But, to write a Web Application, you also need to understand how HTTP works, learn a lot about the HTML standard and how different Web Browsers handle HTTP requests and HTML content. I do not write Web Applications, so I can't help you with questions related to HTML without googling it myself, but if you find an example for PHP, Java or any other technology, and you can't get it working with RTC, feel free to post it here and I will take a look at it.

Best Regards,
Danijel Tkalcec

[clockon]

thanks for the info, just thought id ask the question. There are only basically a few ways most people guard against it from what ive read, these are the options if you didnt already know that i cameacross.

1. After each POST redirect the page so that its in a GET state and refreshing the page wont send a POST request. Which is the easiest way to handle it.
http://en.wikipedia.org/wiki/Post/Redirect/Get

2. POST pages using ajax.
3. Use a NOnce, this requires a little bit of thought, seems to be used quite a bit and is the most secure if done right. You basically generate an encrypted key with an expiration, store that against the page and the user's session. Once the user sends a POST with a matching key, handle the request and generate a new one so that if the user or any hackers that attempt to request the same page with the same key is not accepted.
https://codex.wordpress.org/WordPress_Nonces

im using the first option at the moment but having a look at the nonce and seeing whats involved. But might have to come back to that part of it