-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warden failure fails when using autolocales #34
Comments
Hm, I'm not seeing warden in your Gemfile? There is even padrino-warden although I haven't tested it. You can find a post about it under https://workaround.org/articlehow-to-use-user-authentication-in-your-padrino-apps-with-padrino-warden/. |
I know, already read this article, thank you. I'm using padrino-warden (0.20.2), warden (>= 0.10.3). Padrino contrib autolocales make /sessions/login path unavailable... |
Can you make a reproducible Github repo? Something we can clone and immediately see the failure. |
@adam12 is right, this would make helping you much easier. |
There it is ;-) See https://github.com/happycze/autolocales Shown autolocale issues:
If you disable autolocales, everything works as expected... |
Thanks for the reproducable app.
I believe this is expected, as
The empty screen is a 405 error. It's the result of the You can easily get something on the screen by using something like this in your set :warden_failure_app, proc {
->(env) { [200, {}, ["Foobar"]] }
} Unfortunately, I think you're hitting this bug #5 which has no fix. |
Thank you for workaround, seems to work fine ;-) |
Hi guys,
im struggling with warden authentication failure when using autolocales from padrino-contrib. Without autolocales works following gist OK, with autolocales im getting empty screen on failure.
Please see gist for details https://gist.github.com/happycze/d09e337008f8ba209d6fc54899a2ebc7
Can you help me how to setup autolocales to get it work?
Thank you.
The text was updated successfully, but these errors were encountered: