[ANNOUNCE] Apache-SizeLimit 0.92
Apache::SizeLimit 0.92 has been released to CPAN. Thanks to several contributors and testers who helped make this happen. md5: 4217dbe7cc071b531091542b3c11b700 Summary of changes: Export USE_SMAPS, VERSION, and REQUEST_COUNT to Apache::SizeLimit from Apache::SizeLimit::Core. Call _platform_check_size as a class method to prevent error when USE_SMAPS=0, RT #33303 Reported by: jgoodri...@alum.dartmouth.edu [Fred Moyer ] *** HEADS UP - SHARED CODE BASE - HEADS UP *** Apache-SizeLimit has been hybridized. It has been split into 3 packages. 1) Apache::SizeLimit - User API for httpd 1.3.x / mod_perl 1.x 2) Apache2::SizeLimit - User API for httpd 2.x / mod_perl 2.x 3) Apache::SizeLimit::Core - Interal Shared Functionality _NEVER_ use this module directly. [Philip M. Gollucci ] Skip tests on OS X (darwin) due to broken getrusage(3) [Fred Moyer , Philip M. Gollucci ] Added a SUPPORT section to the docs. [Dave Rolsky ]
PerlFixupHandler doesn't run after authz phase returns HTTP_UNAUTHORIZED
I've written a module, "auth_any" that allows a user to be authenticated by any mechanism including OpenID (Google), Basic auth, LDAP, or Shibboleth (Protect Network). My PerlAuthenticationHandler checks for a cookie, and if not found, redirects to a page containing a list of links for each auth mechanism. These links go back to mod_perl which adds the appropriate configuration directives for that authentication mechanism. If authentication succeeds, the response phase sets the cookie and writes it into our database. The browser is then redirected back to the originally requested URL. The authentication handler finds the cookie this time and returns "OK". I've written a corresponding PerlAuthorizationHandler, however we would like to be able to replace it with authorization through one of the standard providers mentioned above (authorization provider determined at server initialization time). The problem is that if the user is not authorized, the module returns either a 401 with a "WWW-Authenticate:" header field (LDAP or basic), or a 302 with a "Location:" header field (Shibboleth) and displays a second window requesting credentials. I thought that I might be able to remove these header fields in a PerlFixupHandler and issue my own 302 or 200 return code. However, it seems that the fixup phase does not run after an authorization hook or handler returns HTTP_UNAUTHORIZED or REDIRECT. Is there a way around this, or is there another handler phase that I can use to manipulate the return code and HTTP header? Kim
Re: Mod_Perl 2.0 + Apache2 + Template Toolkit + Apache::Template
FWIW, it installed fine on my setup: Installing /Users/phred/dev/perl-5.12.0/lib/site_perl/5.12.0/Template/Service/Apache.pm Installing /Users/phred/dev/perl-5.12.0/man/man3/Apache::Template.3 Appending installation info to /Users/phred/dev/perl-5.12.0/lib/5.12.0/darwin-2level/perllocal.pod On Wed, Sep 22, 2010 at 3:41 AM, Chris Ray wrote: > Hello, I'm currently attempting to update an Apache Cluster from Apache 1.3 > to Apache2. The Cluster is running Debian (Lenny). The website served by > this cluster uses Template Toolkit extensively. A link to template toolkits > home page: > > > > http://template-toolkit.org/ > > > > Sitting in-between Apache2 and Template Toolkit is a Perl module called > Apache::Template the original version of this module doesn't work with > Mod_Perl 2.0. I have since found that Geoffrey Young had created a port of > this module to support Mod_perl 2.0. Available here: > > > > http://www.modperlcookbook.org/~geoff/modules/experimental/Apache-Template-2.00_01.tar.gz > > > > This module hasn't been worked on in a while. When I attempted to install > the module this morning it came up with an error message saying the > following: > > > > Can't find the mod_perl include dir (reason: path /usr/include/apache2 > doesn't exist) at /usr/lib/perl5/Apache2/Build.pm line 2030. > > > > Which is fair enough since I don't have that directory! does anyone know > what should be in there and how I could go about finding the right content > to put in there? > > > > > > Regards Chris
