Fix broken synopsis. RT#75254

[catagits/Catalyst-Authentication-Credential-HTTP.git] / lib / Catalyst / Authentication / Credential / HTTP.pm

diff --git a/lib/Catalyst/Authentication/Credential/HTTP.pm b/lib/Catalyst/Authentication/Credential/HTTP.pm
index 629c7b9..78f5948 100644 (file)
--- a/lib/Catalyst/Authentication/Credential/HTTP.pm
+++ b/lib/Catalyst/Authentication/Credential/HTTP.pm
@@ -22,7 +22,7 @@ __PACKAGE__->mk_accessors(qw/
     require_ssl
 /);
 
-our $VERSION = '1.013';
+our $VERSION = '1.014';
 
 sub new {
     my ($class, $config, $app, $realm) = @_;
@@ -433,7 +433,7 @@ for Catalyst.
     sub foo : Local {
         my ( $self, $c ) = @_;
 
-        $c->authenticate({ realm => "example" });
+        $c->authenticate({}, "example");
         # either user gets authenticated or 401 is sent
         # Note that the authentication realm sent to the client (in the
         # RFC 2617 sense) is overridden here, but this *does not*
@@ -574,6 +574,10 @@ Set or get the C<$nonce> object used by the digest auth mode.
 You may override these methods. By default they will call C<get> and C<set> on
 C<< $c->cache >>.
 
+=item authentication_failed
+
+Sets the 401 response and calls C<< $ctx->detach >>.
+
 =back
 
 =head1 CONFIGURATION
@@ -629,7 +633,7 @@ part of the progressive realm.
 
 However use like this is probably not optimum it also means that users in
 browsers ill never get a HTTP authenticate dialogue box (unless you manually
-return a 410 response in your application), and even some programatic
+return a 401 response in your application), and even some automated
 user agents (for APIs) will not send the Authorization header without
 specific manipulation of the request headers.