team didn't like it for
performance reasons.
On 1/20/2016 8:50 PM, Scott Rossillo wrote:
There's s pattern to handle the back button during flows.
It's that a
post should never render a view but redirect (HTTP get) to the failure
or success view.
http://www.codeproject.com/Tips/433399/PRG-Pattern-Post-Redirect-Get
On Wed, Jan 20, 2016 at 7:22 PM Bill Burke <bburke(a)redhat.com
<mailto:bburke@redhat.com>> wrote:
On 1/20/2016 3:49 PM, Stian Thorgersen wrote:
>
> One additional thought. Maybe we could add a field to
> autheticators to say if they support back, cancel or nothing.
> Then the flow would allow going back if previous supports back.
> It would allow cancel if all supports it, or nothing is one says
> nothing
>
> On 20 Jan 2016 19:48, "Stian Thorgersen" <sthorger(a)redhat.com
> <mailto:sthorger@redhat.com>> wrote:
>
> Firstly, let's drop KEYCLOAK-2325 from 1.8 and see if we can
> fix it for 1.9.
>
> Secondly, the back button should not navigate backwards in
> the flow. Also, the refresh button should just redisplay the
> page as it does now (ignoring the post). A couple ideas to
> improve things though:
>
> 1) Set cache-control to "Cache-Control: no-store,
> must-revalidate, max-age=0". This should force a reload of
> the page when the user clicks the back button
>
Really? That's cool then, this will basically "disable" the back
button :) I'll try it out.
> 2) Can we add a back link to some steps in the flow?
> 3) Can we add a cancel link to some steps in the flow?
>
You can reset the flow to the beginning, but can't go back one step.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org <mailto:keycloak-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/keycloak-dev