It is generally considered good practise to use POST for data changing requests, which in my case is done in the task. Also I always try to REDIRECT after a POST to a GET, so that if the user clicks refresh, the same task wouldn't be started.
How do you handle this, in combination with passing around the task_id?
We pass the task ID around. This makes the URL unique, and allows the user to return to the URL later, or even share it, if they want. You could put the task ID in session storage.
It is generally considered good practise to use POST for data changing requests, which in my case is done in the task. Also I always try to REDIRECT after a POST to a GET, so that if the user clicks refresh, the same task wouldn't be started.
How do you handle this, in combination with passing around the task_id?
Do you also put the task_id in the session?