544030 - Implement PRG for post_bug.cgi.

Status: RESOLVED DUPLICATE of bug 427913

(Bugzilla :: Creating/Changing Bugs, enhancement)

Description

[Christian Höltje]

Currently, if you post a change to a bug, you are left on the post_bug.cgi page which was submitted via POST with all the changes.

This is bad because a refresh can cause a confusing message.

This is apparent when you have the preference "After changing a bug" set to "Show the updated bug" and you want to see if anyone has replied to the bug -- refreshing at that URL causes the already-made-changes page to come up.

Instead, the PRG[1] pattern should be applied.  It should POST, REDIRECT if successful, and then do a GET that doesn't change anything.

Specifically, the messages about what bugs were updated and who the email was sent to should be on a GET url that can be harmlessly refreshed.

Ciao!

[1] http://en.wikipedia.org/wiki/Post/Redirect/Get

Comment 1

[David Lawrence [:dkl]]

Bugzilla (at least in recent versions) issues an unique token in enter_bug.cgi and show_bug.cgi that cannot be re-used if someone hits submit twice. So this is in place to keep these duplicate submissions from occurring by throwing an error screen saying the form had bit submitted once before. So I am not sure this new functionality is needed.

Comment 3

[Christian Höltje]

 The goal is to make the user experience better.