Error if a route can handle no POST. about two-factor-bundle

[ickbinhier]

The problem occurs naturally only on when the user on a route is the no POST can.

I have now resorted me so that I have a fixed route set the POST can. But the commodity is not, of course.

[scheb]

The problem seems to be, that URL validation of the routing component is triggered before two-factor authentication. At the moment I have no idea how to fix it. I'm not deep enough into Symfony internals for that.

[ickbinhier]

Does the form need to be sent to the original route because? Or can I form also be geschcickt to a specially defined Fake route? White Scheb / two-factor-bundle then where I really wanted to go?

I try that tomorrow times ...

[scheb]

I was able to reproduce the problem, but unfortunately I didn't find a way to prevent the RouterListener from throwing that exception.
A solution would be to post to a route which supports POST requests. But you will lose the target URL! The bundle will always redirect (with GET) to the URL the post has been sent to.

[stof]

The bundle will always redirect (with GET) to the URL the post has been sent to.

This seems to be the issue. Storing the needed target URL in the session (as done for form login in symfony) looks better.

[ickbinhier]

@scheb Has someone already tried?

[scheb]

No, not yet. This would require rewriting the parts of the bundle, where the authentication form is being displayed.

[scheb]

This issue is solved in the upcoming 3.0 version. Check out the beta.