How to stop form from submitting twice

After filling the form you could redirect to another page to display the "success" message. So if someone refreshes that page he just gets the "success" message again without the POST request before it that creates the data.

@FTIERSCH - At the moment, I have return redirect back with a message. Shouldn’t that do the same thing as what you have mentioned? Or do I have to redirect to a page other than the form page?

As you mentioned, the user refreshed 3 times and the data got entered 3 times. But this couldn't happen like this. As soon as he had refreshed, he would have got a popup saying confirm form submission. And after responding to that only the form would have got submitted and the data would have entered in the database.

So according to the workflow, the page would have redirected with displaying the appropriate message.

@TUSHAR2004 - This makes more sense. Now it could have been that he tapped the submit button twice thinking it wasn’t being submitted. How can I tackle that if that is the case? I mean pressing the button fast 3 times makes it enter 3 datas. How do I avoid doing that

That's a "normal" risk you're taking. But if it's a logical problem for your application you could check before inserting if the same user has entered data in the last... 10 seconds or something like that and then throw an error if that happened.

@FTIERSCH - Thats a good solution. Can you give me perhaps an idea of where to start from? Thanks a bunch

Simply use validation else you can go with the data as like below with isset function condition.

  if(isset($request['column1']) && isset($request['column2']))

@PICKAB00 - Something like:

if (Data::where('user_id', auth()->id())->where('created_at', '>', now()->subSeconds(10))->exists()) {
    throw new Exception('Possible multi submit');
}

abort(429); is the way to go.

@FTIERSCH - This seems like the better solution. 429 abort seems to be a good solution but I don’t want the user to be presented with the http error code but rather a simple message bag would do.

Thanks mate

@PICKAB00 - abort(429) will just throw appropriate exception, you can still display a message. Always remember to return appropriate HTTP status codes.