On 28 June 2012 23:12, Gavin Henry gavin.he...@gmail.com wrote:
...
Thanks Tim. Yes, I know that but then the other two realms will fail
and that's the point of progressive. I want to call one -authenticate
which tries all the realms I've defined in progressive_oauth.
Regrettably, the docs for
Will Crawford wrote:
On 28 June 2012 23:12, Gavin Henry gavin.he...@gmail.com wrote:
...
Thanks Tim. Yes, I know that but then the other two realms will fail
and that's the point of progressive. I want to call one -authenticate
which tries all the realms I've defined in progressive_oauth.
This is a how do others do this? post.
In your large (or even not so large) apps I assume at times you experience
dependency regressions. My question is do you manage it on a case-by-case
basis (simply install an older version or fix internally) or is it such a
significant issue that you have a
Here's what we do:
- we have a (VCS-managed) set of tarballs downloaded from CPAN
- we run a CPAN-like server providing those tarballs
- we have a rather large set of distroprefs to skip unreliable tests
and apply local patches
- we usually update to the latest CPAN (and perl) releases
-
Does something like this fix the problem?
--- Password.pm 2012-06-29 11:23:51.0 +0100
+++ Password-new.pm 2012-06-29 11:33:40.0 +0100
@@ -34,6 +34,14 @@
sub authenticate {
my ( $self, $c, $realm, $authinfo ) = @_;
+ my $password_field =
