#Forms to go submit redirect code

With the PRG pattern, the URI of the request can safely be bookmarked. Because of this, a response based on the body of the HTTP POST request cannot be bookmarked. User agents (such as browsers) store only the URL of an HTTP request as a bookmark. For example, if a web user refreshes before the initial submission completes, possibly because of server lag, a duplicate POST occurs in certain user agents.

The PRG pattern cannot address every scenario of duplicate form submission.

#Forms to go submit redirect code

The HTTP 1.1 specification introduced the HTTP 303 ('See other') response code to ensure that in this situation, browsers can safely refresh the server response without causing the initial POST request to be resubmitted. To avoid this problem, many web developers use the PRG pattern -instead of responding with content, the server responds to a POST request by redirecting the client to another location. Some browsers mitigate this risk by warning the user that they are about to re-issue a POST request.

When a web form is submitted to a server through an HTTP POST request, attempts to refresh the server response can cause the contents of the original POST to be resubmitted, possibly causing undesired results, such as a duplicate web purchase. Post/Redirect/Get (PRG) is a web development design pattern that lets the page shown after a form submission be reloaded, shared, or bookmarked without ill. Post/Redirect/Get ( PRG) is a web development design pattern that lets the page shown after a form submission be reloaded, shared, or bookmarked without ill effects, such as submitting the form another time. Diagram of the double POST problem above being solved by PRG.