Apache...ie::FAQ(3pm)
β¨ NAME β¨
Apache::AuthCookie::FAQ β Frequently Asked Questions about Apache::AuthCookie π
(you got here via the manual page Apache...ie::FAQ(3pm) β the user-contributed Perl documentation situation, bestie, and yes that truncated-looking name is just how the renderer does it, don't panic π
)
π VERSION π
version 3.32 β this is the one you're reading rn πΈ
πΈ DESCRIPTION πΈ
Okay so this doc? Its whole entire job is answering the most frequently asked questions about Apache::AuthCookie. That's it. That's the vibe. FAQ duties, no filler, let's go π¦
π How can I protect an entire site (/) with Apache::AuthCookie? π
So like, you wanna lock down everything, right? Every single request to /? Bestie you gotta hand Apache a require directive that covers all the requests β except your login handler, obviously, because the login page has to stay reachable or nobody can ever log in and that would be a whole tragedy π
The easiest way to pull this off is to override the auth handlers for your login script. Say your login handler lives at /LOGIN β then you want something that looks exactly like this, no cap:
<Location />
AuthType My::AuthCookieHandler
AuthName Whatever
PerlAuthenHandler My::AuthCookieHandler->authenticate
PerlAuthzHandler My::AuthCookieHandler->authorize
require valid-user
</Location>
<Location /LOGIN>
PerlAuthenHandler Apache2::Const::OK
PerlAuthzHandler Apache2::Const::OK
</Location>
...
(the ... is me saying "and friends" β the point is the outer <Location /> gets the real auth and the inner <Location /LOGIN> gets Apache2::Const::OK for both handlers so the login path stays wide open π«Ά)
π¦ SOURCE π¦
The development version is living its best life on github at <https://github.com/mschout/apache-authcookie> and you can clone it from <https://github.com/mschout/apache-authcookie.git> β¨
π BUGS π
Found a bug? Got a feature request? Please report it on the bugtracker website at <https://github.com/mschout/apache-authcookie/issues> π
And listen β when you do submit a bug or a request, please include a test-file, or a patch to an existing test-file, that illustrates the bug or the desired feature. Give the maintainers something to actually run. That's the group-chat etiquette, fr fr π
π AUTHOR π
Michael Schout <mschout@cpan.org> β the icon who wrote all this π
π COPYRIGHT AND LICENSE π
This software is copyright (c) 2000 by Ken Williams.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. π
and that's the whole page bestie π this rendition came to you courtesy of perl v5.40.1 dated 2025-09-30, which is also the exact footer energy of the original Apache...ie::FAQ(3pm). go forth and protect your site, you absolute main character πβ¨
π¦ where this page comes from
- ubuntu resolute: libapache2-authcookie-perl 3.32-2 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- ubuntu stonking: libapache2-authcookie-perl 3.32-2 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms