I have this flow but don’t know how to deal with it. I think “Forward” button should use GET because it is safe and idempotent but the textarea contains a large amount of text so I think can’t put in in URI. I changed to POST.
The OK button on confirmCreateAlbum surely POST.
The flow says When click “Cancel” on confirmCreateAlbum, it returns to nameAlbum with the fields were filled for editing. I put OK button in a form with action=”confirmCreateAlbum”. The problem is how to back to nameAlbum?
Note: nameAlbum will show errors if the required fields are not provided.
Although there is no specific length limitation for GET requests in the RFC, browsers impose limits on URI lengths. There are also considerations with some server implementations.
You said the textarea “contains a large amount of text” so it is recommended to use POST in this situation because it won’t be subjected to URI limitations.
On to your original question, “The problem is how to back to nameAlbum?”
In your confirmCreateAlbum form, you can actually use two separate forms. A form for the “OK” which the action calls your specified script for confirming, and a form for the “Cancel” which has an action calling your nameAlbum form.
Anther option is getting clever with hidden input fields and passing the data around but that can get messy.
Personally, if it were up to me, I’d be using jQuery/Javascript for confirming form submission. It’s a simple client side solution that doesn’t require you to leave your original form if “Cancel” is pressed. But that’s just me…