I am having a very hard time understanding the exact process of "post/redirect/get".
I have combed through this site and the web for several hours and cannot find anything other than "here's the concept".
How to understand the post/redirect/get pattern?
If the users are being redirected, then there should never be a form re-submission.
Redirect them to submitted.php and use the following:
if(isset($_SESSION['error'])){ echo'the error';}
else if(isset($_SESSION['success'])){ echo'your petition was successfully signed!');}
else{ echo 'unknown error.'; }
xs' would be bound to the string "ello".
xs would be bound to the string "hello".
The @ pattern lets you give a name to a variable while also matching its structure and possibly giving name to the components.
I believe there was an error.
First condition is fairly easy to understand. When LCP length == pattern length, it's done. When your pattern is even smaller than or equal to the smallest one, then only choice is the smallest one.
The second condition is wrong. We can prove it by contradiction. r < P || Wr <= a... means r >= P && Wr > a... If r >= P, then how can we have Lw = N(not found), since we already have r length common prefix?
The pattern is to GET a blank form, modify the contents of the form, then POST that to the server, which then sends a redirect to another page which is a GET, perhaps to a page saying Form submitted successfully.. (Get->)Post->Redirect->Get
The first action is not really POST. That's the end result of completing a form and submitting it. The guide is more about what to do after that POST, as if you do not do a redirect, then the user is left on a page saying Form submitted successfully where they could just hit F5 and do another POST. With that redirect however, they're on that results page via a safe GET which will not result in a double post.
As for the implementation, you should have each be its own action on the server side. This is inline with the MVC / RESTful implementation.
You could use 3 actions here instead if you wanted to have the 2nd action call save. Most REST/CRUD conventions use the 4, but the choice is yours. The benefits are the same as going the REST/MVC route in the first place.
See these resources as well:
As you may know from your research,
POST-redirect-GETlooks like this:POSTs to the server.For example, say we have this structure of the website:
/posts(shows a list of posts and a link to "add post")/<id>(view a particular post)/create(if requested with theGETmethod, returns a form posting to itself; if it's aPOSTrequest, creates the post and redirects to the/<id>endpoint)/postsitself isn't really relevant to this particular pattern, so I'll leave it out./posts/<id>might be implemented like this:/posts/createmight be implemented like this:GETrequest:POST.POSTrequest:/posts/<id>(where<id>is returned from the call to the database)