Post/Redirect/Get
Sign in to saveAlso known as Redirect After Post, post-redirect-get
thumb|350px|right|Diagram of a double POST problem encountered in user agents. thumb|350px|right|Diagram of the double POST problem above being solved by PRG. 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.
In the Vinony graph
Vinony's link graph records 5 inbound references to Post/Redirect/Get, and connects out to International Standard Book Number, HTTP and Uniform Resource Identifier.
It is catalogued under the topic Web applications.
Vinony links it to 6 Wikipedia language editions.
Wikidata facts
- Instance of
- software design pattern
Show 2 more facts
- Stack Exchange tag
- stackoverflow.com/tags/post-redirect-get
- facet of
- web form
Sources (1)
via Wikidata · CC0
~2 min read
Encyclopedic overview
3 sectionsContents
- Bookmarks
- References
- External links
thumb|350px|right|Diagram of a double POST problem encountered in user agents. thumb|350px|right|Diagram of the double POST problem above being solved by PRG. 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.
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. Some browsers mitigate this risk by warning the user that they are about to re-issue a POST request.
Excerpted from Wikipedia’s “Post/Redirect/Get” article, available under the CC BY-SA 4.0 licence.