@campersau yes, looks good -- and your test proves it! :)

I'd have to agree, it probably should have done this from the beginning, however, I'm slightly concerned this could be a BC break, as this would change the default behavior of the plugin slightly.

I'm not saying they should, but if anyone who is using the prg plugin sets query parameters on their form action, but is, for any reason, relying on those parameters not being present after the redirect, this could possibly present an issue.

So we should either, A) acknowledge that this likely affects so few users (none?) that it's not worth worrying about, or B) perhaps add a third parameter to the __invoke() method to toggle this option, and default it to off so that behavior doesn't change.

@EvanDotPro a breakage here seems ok as long as it is documented. Manually redirecting is always possible anyway.

@Ocramius fine by me. :)

Corrected the title of this PR from Post/Request/Get to Post/Redirect/Get.