trying to compile mod_perl against httpd-2.4.1
Well, its a no go, even after checking out the latest SVN code, Problem is the ‘conn_rec’ structure has changed. It no longer has 'remote_ip' defined in it. [bpm]$ make cd "src/modules/perl" && make make[1]: Entering directory `/home/bpm/src/apache/mod_perl-2.0/src/modules/perl' gcc -I/home/bpm/src/apache/mod_perl-2.0/src/modules/perl -I/home/bpm/src/apache/mod_perl-2.0/xs -I/usr/include/apr-1 -I/usr/include/httpd -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -I/usr/lib64/perl5/CORE -DMOD_PERL -DMP_COMPAT_1X -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fPIC \ -c modperl_interp.c && mv modperl_interp.o modperl_interp.lo modperl_interp.c: In function ‘modperl_interp_select’: modperl_interp.c:503:35: error: ‘conn_rec’ has no member named ‘remote_ip’ make[1]: *** [modperl_interp.lo] Error 1 make[1]: Leaving directory `/home/bpm/src/apache/mod_perl-2.0/src/modules/perl' make: *** [modperl_lib] Error 2 Did see the following in the httpd-2.4.1 src, httpd-2.4.1/include/ap_mmn.h that seems to be a major API change. * 2030.0 (2.4.0-dev) c->remote_ip becomes c->peer_ip and r->client_ip, * c->remote_addr becomes c->peer_addr and r->client_addr I guess I'm asking is anyone has made any progress with mod_perl with the new httpd 2.4 ?? -- Brian Millett "We used to have them back home long ago. They use science to achieve the effect of magic. I haven't seen one in years. They almost never travel. They don't like to leave their places of power. To see even one of them is a rare thing. To see more than one at a time is considered a very bad omen." [3 mages walk by] "Three...this is definitely not good." -- [ Londo (re: technomages), "The Geometry of Shadows"]
Re: trying to compile mod_perl against httpd-2.4.1
Thanks for the spot. We're rolling rc3 for 2.0.6 right now, I have cc'd the dev list about this issue. I may have some tuits to look at this, but am guessing someone else will fix it more quickly. On Tue, Feb 21, 2012 at 11:49 AM, Brian Millett wrote: > Well, its a no go, even after checking out the latest SVN code, > > Problem is the ‘conn_rec’ structure has changed. It no longer has 'remote_ip' > defined in it. > > > [bpm]$ make > cd "src/modules/perl" && make > make[1]: Entering directory > `/home/bpm/src/apache/mod_perl-2.0/src/modules/perl' gcc > -I/home/bpm/src/apache/mod_perl-2.0/src/modules/perl > -I/home/bpm/src/apache/mod_perl-2.0/xs -I/usr/include/apr-1 > -I/usr/include/httpd -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe > -fstack-protector -I/usr/local/include -I/usr/lib64/perl5/CORE -DMOD_PERL > -DMP_COMPAT_1X -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions > -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fPIC \ -c > modperl_interp.c && mv modperl_interp.o modperl_interp.lo modperl_interp.c: In > function ‘modperl_interp_select’: modperl_interp.c:503:35: error: ‘conn_rec’ > has no member named ‘remote_ip’ make[1]: *** [modperl_interp.lo] Error 1 > make[1]: Leaving directory > `/home/bpm/src/apache/mod_perl-2.0/src/modules/perl' make: *** [modperl_lib] > Error 2 > > > Did see the following in the httpd-2.4.1 src, httpd-2.4.1/include/ap_mmn.h > that seems to be a major API change. > > * 2030.0 (2.4.0-dev) c->remote_ip becomes c->peer_ip and r->client_ip, > * c->remote_addr becomes c->peer_addr and > r->client_addr > > I guess I'm asking is anyone has made any progress with mod_perl with the new > httpd 2.4 ?? > -- > Brian Millett > "We used to have them back home long ago. They use science to achieve the > effect of magic. I haven't seen one in years. They almost never travel. > They don't like to leave their places of power. To see even one of them > is a rare thing. To see more than one at a time is considered a very > bad omen." > [3 mages walk by] > "Three...this is definitely not good." > -- [ Londo (re: technomages), "The Geometry of Shadows"]
Apache::ASP v2.62 available!
Hi modperl-ers, Its been a while since an Apache::ASP module release announcement to the modperl list! We have some good news here! Greg Youngblood has been promoted to be co-maintainer of Apache::ASP, and has publishing rights for CPAN/PAUSE. The original 2.62 release has been replublished to CPAN and is available immediately. Shaking off the monolithic contribution model, Greg also nicely set up this project over at SourceForce: https://sourceforge.net/projects/apache-asp/ Also we have Thanos Chatziathanassiou, & Tsirkin Evgeny looking to contribute further! Please see http://www.apache-asp.org for more about this module. Regards, Josh ### Apache-ASP 2.62 has just been released. This is the first release since moving to SourceForge. The file is pending upload and release to CPAN. Until then, you can get the release from SourceForge at: http://sourceforge.net/projects/apache-asp/files/CPAN/Apache-ASP-2.62.tar.gz/download Changes in this release: + = improvement;- = bug fix;(d) = documentation $MODULE=Apache::ASP; $VERSION = 2.62; $DATE="2011/08/16" - Fixed 'application/x-www-form-urlencoded' for AJAX POSTs post Firefox 3.x + First sourceforge.net hosted version + Incremented version number to actually match SVN branch tag + Switched to Big-endian date format in the documentation. Less chance of misunderstandings
Re: disabling directives in .htaccess files
On Mon, Feb 13, 2012 at 11:58 PM, Aaron Knister wrote: > Hi Tuomo, > > I don't mean 80,000 virtual hosts. I have over 80k unix accounts for which > content is being served via mod_userdir. And I consider each one it's own > "site". It's critical to the environment that users be prevented from > specifying handlers in htaccess files in part exactly for the reasons you > specified. The other issue is the potential for suexec abuse. I only have one > perl access handler I need to use and it has no global variables. Hi Aaron, In the end would it not be safer to remove mod_perl all together? You don't mention exactly what you are doing with mod_perl so this may not be practical, but you do mention you only have one perl access handler. Can that not be rewritten in C? Is there no existing third party C module that can do what you need (or be modified slightly to do what you need)? Also, you briefly mentioned sections. These are generally pretty easy to get around by just pre-generating your apache.conf file using a simple perl script and a templating module. This is how I understand most people create complex apache.conf files and this is how I have always done it. It might sound odd for someone to tell you not to use mod_perl on the mod_perl mailing list, but I think in your situation a lighter-weight solution would save you a lot of headaches. Cheers, Cees
