HTTP::Throwable::Role::Status::Unauthorized - 401 Unauthorized
The request requires user authentication. The response MUST include a
WWW-Authenticate header field containing a challenge applicable to the
requested resource. The client MAY repeat the request with a suitable
Authorization header field. If the request already included Authorization
credentials, then the 401 response indicates that authorization has been
refused for those credentials. If the 401 response contains the same challenge
as the prior response, and the user agent has already attempted authentication
at least once, then the user SHOULD be presented the entity that was given in
the response, since that entity might include relevant diagnostic information.
This is a required string or array of string that will be used to populate the
'WWW-Authenticate' header(s) when creating a PSGI response.
HTTP Authentication: Basic and Digest Access Authentication -
<http://www.apps.ietf.org/rfc/rfc2617.html>
WWW-Authenticate Header -
<http://www.apps.ietf.org/rfc/rfc2617.html#sec-3.2.1>
- Stevan Little <stevan.little@iinteractive.com>
- Ricardo Signes <rjbs@cpan.org>
This software is copyright (c) 2011 by Infinity Interactive, Inc.
This is free software; you can redistribute it and/or modify it
under the same terms as the Perl 5 programming language system itself.