> Passing a :login-uri causes workflows/interactive-from to change what
> uri it checks for. Given the setup above the login form needs to post
> to "/".
>
I was under the impression that the :login-uri was on for only getting the
form. Do you know if the GET and POST uris can be separated
Ah, thanks.
On Feb 21, 2013, at 1:42 AM, larry google groups
wrote:
> > ring.middleware.params/wrap-parms
> > ring.middleware.keyword-params/wrap-keyword-params
>
> No, he already has:
>
> (handler/site))
>
> Which should add in the middleware that you mention. But in my app I have:
>
>
> ring.middleware.params/wrap-parms
> ring.middleware.keyword-params/wrap-keyword-params
No, he already has:
(handler/site))
Which should add in the middleware that you mention. But in my app I have:
handler/site)
instead of:
(handler/site))
I think it gets rolled up and called at the en
Hi Ari,
you have to add wrappers:
ring.middleware.params/wrap-parms
ring.middleware.keyword-params/wrap-keyword-params
---
Ilshad Khabibullin
+7 981 688 26 35
On Feb 21, 2013, at 12:48 AM, Ari wrote:
> Hi,
>
> I'm trying to incorporate authentication via the interactive form workflow;
On Wed, Feb 20, 2013 at 2:48 PM, Ari wrote:
> Hi,
>
> I'm trying to incorporate authentication via the interactive form workflow;
> however, I'm currently unable to receive submitted credentials for
> verification. When I submit the sign-in form that has it's action bound to
> "/login", I get "Pag
Hi,
I'm trying to incorporate authentication via the interactive form workflow;
however, I'm currently unable to receive submitted credentials for
verification. When I submit the sign-in form that has it's action bound to
"/login", I get "Page not found" as per my default route below. I've
inc
