GoogleBot
Hi,
I use a PerlTransHandler on my server to get a file :
sub handler {
...
if ( $uri =~ /^\/sitemap.xml.gz$/ ) {
my $real_url = $r->unparsed_uri;
$real_url = '/static' . $real_url;
$r->proxyreq(1);
$r->uri($real_url);
$r->filename(sprintf "proxy:http://xxx.xxx.xxx.xxx%s",$real_url);
$r->handler('proxy-server');
return Apache2::Const::OK;
}
...
return Apache2::Const::DECLINED;
}
When I use Firefox to get sitemap.xml.gz, all work fine :
xxx.xxx.xxx.xxx - - [07/Apr/2009:14:59:35 +0200] "GET /sitemap.xml.gz
HTTP/1.1" 200 2924 "-" "Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.0.6)
Gecko/2009020409 Iceweasel/3.0.6 (Debian-3.0.6-1)"
But, when GoogleBot download the file, I see these logs :
66.249.65.228 - - [07/Apr/2009:15:01:41 +0200] "HEAD /sitemap.xml.gz
HTTP/1.1" 302 - "-" "Mozilla/5.0 (compatible; Googlebot/2.1;
+http://www.google.com/bot.html)"
66.249.65.228 - - [07/Apr/2009:15:01:44 +0200] "GET /sitemap.xml.gz
HTTP/1.1" 302 451 "-" "Mozilla/5.0 (compatible; Googlebot/2.1;
+http://www.google.com/bot.html)"
Why 2 requests and why my server return status 302 and not 200 ?
Thanks.
[no subject]
Hi,
I use a PerlTransHandler on my server to get a file :
sub handler {
...
if ( $uri =~ /^\/sitemap.xml.gz$/ ) {
my $real_url = $r->unparsed_uri;
$real_url = '/static' . $real_url;
$r->proxyreq(1);
$r->uri($real_url);
$r->filename(sprintf "proxy:http://xxx.xxx.xxx.xxx%s",$real_url);
$r->handler('proxy-server');
return Apache2::Const::OK;
}
...
return Apache2::Const::DECLINED;
}
When I use Firefox to get sitemap.xml.gz, all work fine :
xxx.xxx.xxx.xxx - - [07/Apr/2009:14:59:35 +0200] "GET /sitemap.xml.gz
HTTP/1.1" 200 2924 "-" "Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.0.6)
Gecko/2009020409 Iceweasel/3.0.6 (Debian-3.0.6-1)"
But, when GoogleBot download the file, I see these logs :
66.249.65.228 - - [07/Apr/2009:15:01:41 +0200] "HEAD /sitemap.xml.gz
HTTP/1.1" 302 - "-" "Mozilla/5.0 (compatible; Googlebot/2.1;
+http://www.google.com/bot.html)"
66.249.65.228 - - [07/Apr/2009:15:01:44 +0200] "GET /sitemap.xml.gz
HTTP/1.1" 302 451 "-" "Mozilla/5.0 (compatible; Googlebot/2.1;
+http://www.google.com/bot.html)"
Why 2 requests and why my server return status 302 and not 200 ?
Thanks.
Re: ModPerl::Registry under Windows
2009/3/29 Octavian Râşniţă : > Hello, > > Does anyone know if ModPerl::Registry really runs the cgi scripts > persistently under Windows? This should work the same under Windows. > I have loaded a Catalyst application using the standard mod_perl way, (as a > PerlRequestHandler) and the httpd process was using 130 MB memory. > Then I have loaded it using ModPerl::PerlRun and ModPerl::Registry and with > any of them, the httpd process used only 12 MB of memory after loading the > application in the browser, exactly like when I load Apache without this > application at all. > > Isn't ModPerl::Registry keeping the application persistent, or Catalyst's > cgi script does something that doesn't allow running it well with > ModPerl::Registry under Windows? That seems like an extreme difference. It might be an idea to ask this on the Catalyst mailing list, as someone there may be more familiar with running Catalyst and mod_perl. I did notice that http://search.cpan.org/~agrundma/Catalyst-Engine-Apache-1.07/lib/Catalyst/Engine/Apache2/MP20.pm recommends against running Catalyst applications under ModPerl::Registry, but no reasons are given. -- best regards, Randy
Re: OT (slightly): build an up-to-date mod_perl development environment on Windows
On Mon, Apr 6, 2009 at 12:17 AM, Michael Lackhoff wrote: > Hello, > > if possible I try to develop on Windows, then deploy on Linux or Solaris > for production. This worked very well in the past with a self compiled > environment (VC6). But as some components are rather old by now I would > like to recompile with recent versions of apache, perl, mod_perl, > openssl and some DBI-drivers but I had some problems with apache 2.2.11. > I have VC6 with SP5 installed, plus the 2003 Platform SDK update from > Microsoft. Perl 5.10.0 and openssl 0.9.8k compile just fine but when it > comes to Apache 2.2.11 or 2.2.10 I get lots of errors in the APR part of > the build. 2.2.9 seems to be the last version that builds o.k. > > My question is twofold: First, any ideas what might be going wrong? As > there are some (VC6?) compiled versions around, this should be possible. > Or, as second choice, what would be a good working combination of > precompiled versions? In the past I had tried XAMPP but had some > problems with DBI and openssl when adding modules that didn't come with > XAMPP. These problems were gone when I compiled everything myself and I > don't want them to come back. As I understand it (I am no C programmer) > it is important for some parts of the chain to be built with the same > compiler/same settings and as it seems impossible to get everything I > need from a single (binary-)source I keep trying to compile it myself. You're right that problems can arise when using components that were compiled with different versions of VC++. There is a Win32 binary version of Apache/2.2.11 available from http://httpd.apache.org/download.cgi, which should be compatible with ActivePerl. If you're having problems compiling the Apache server, the mailing lists for either httpd (http://httpd.apache.org/lists.html) or apr (http://apr.apache.org/mailing-lists.html) would be a good place to report problems. -- best regards, Randy
Re: mod_perl crashes with Perl 5.10
On 29/3/09 15:30, Jozef Kosoru wrote: > Hello, > > I tested my mod_perl application using following combinations recently: > > * Apache/2.2.9 (Debian) mod_apreq2-20051231/2.6.0 mod_perl/2.0.4 Perl/v5.10.0 > (default Debian Lenny packages, mpm-prefork) > > * Apache/2.2.11 (Unix) mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.0 > (apache, apreq and mod_perl compiled from sources, mpm-prefork) > > and I see a crash of Apache process on each request. Just to be sure, is that a 32/64 bit platform ? > Here's the backtrace: > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0xb7ce0ad0 (LWP 11196)] > 0xb7bf2095 in Perl_pp_undef () from /usr/lib/libperl.so.5.10 > (gdb) bt > #0 0xb7bf2095 in Perl_pp_undef () from /usr/lib/libperl.so.5.10 > #1 0xb7bc2dc1 in Perl_runops_standard () from /usr/lib/libperl.so.5.10 > #2 0xb7bbcd38 in Perl_call_sv () from /usr/lib/libperl.so.5.10 > #3 0xb7cb2bfc in modperl_callback (my_perl=0x9ab21a0, handler=0x9639b18, > p=0x9ad4578, > r=0x9ad45b8, s=0x961bfe0, args=0x98a13c0) at modperl_callback.c:101 Hrm, if at all possible, while in gdb, could you dump more information from that frame ? (gdb) info locals Also, I'd love to see as much of the arguments as possible, expecially handler, r and args (gdb) print *handler (gdb) print *r (gdb) print *args Thanks. Also, one thing that always help narrow things down is if you could boil down your application to a small enough test case that you could share it with us. -- Philippe M. Chiasson GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5 http://gozer.ectoplasm.org/ m/gozer\@(apache|cpan|ectoplasm)\.org/ signature.asc Description: OpenPGP digital signature
Re: [SECURITY] [CVE-2009-0796] Vulnerability found in Apache::Status and Apache2::Status
Update - I fat fingered the CVE number in this email body previously (but it was correct in the subject). The correct vulnerability reference number is CVE-2009-0796. On Wed, Apr 1, 2009 at 2:58 PM, Fred Moyer wrote: > mod_perl lists, > > A specific vulnerability [CVE-2009-0795] in Apache::Status and > Apache2::Status has been discovered which may affect the security of > your mod_perl installation. Running Apache::Status on a public server > with no protection has always been a bad idea though, vulnerability or > not. > > The mod_perl1 and mod_perl2 codebases have been updated to protect > against this vulnerability, but your existing server may be > vulnerable. To secure your mod_perl server from this vulnerability, > we recommend that you disallow access to Apache::Status and > Apache2::Status resources (usually located at /perl-status) from > untrusted hosts. > > Q: How do I know if my installation is vulnerable? > > A: If you have enabled the Apache::Status or Apache2::Status modules > in your httpd.conf, your installation may be vulnerable. See the > following links for details on what constitutes potentially vulnerable > httpd.conf directives. > > http://perl.apache.org/docs/1.0/api/Apache/Status.html#Description > http://perl.apache.org/docs/2.0/api/Apache2/Status.html#Description > > If you have a directive in your httpd.conf, > your installation is likely vulnerable. > > Q: What steps do I take to secure my mod_perl installation? > > A: Disallow access from certain clients to your status url (example > /perl-status) in your httpd.conf file. > > mod_perl1 example: > > > Order deny,allow > Deny from all > Allow from 127.0.0.1 > SetHandler perl-script > PerlHandler Apache::Status > > > > mod_perl2 example: > > > Order deny,allow > Deny from all > Allow from 127.0.0.1 > SetHandler perl-script > PerlResponseHandler Apache2::Status > >
Re: mod_perl6 availability?
Foo JH wrote: Hi guys, There's recently some talk on the ActivePerl mailing list on Perl6 (Rakuda) and IIS. Out of curiosity, is anyone experimenting on this on mod_perl6? mod_perl6 was mentioned by Jeff Horwitz in the following articles: 1. http://www.oreillynet.com/onlamp/blog/2008/02/jeff_horwitz_on_mod_perl6.html 2. http://www.smashing.org/jeff/node/21 3. http://www.smashing.org/jeff/node/35 But I can't find any ppds on this. Probably will work in progress? Jeff Horwitz is probably the only person with any answers about mod_parrot / mod_perl6, i'd suggest contacting him directly. Everything that i've seen with it was done on some flavor of *nix. i'm sure sure what Rakudo and/or parrot's status on win32 is. Adam
mod_perl6 availability?
Hi guys, There's recently some talk on the ActivePerl mailing list on Perl6 (Rakuda) and IIS. Out of curiosity, is anyone experimenting on this on mod_perl6? mod_perl6 was mentioned by Jeff Horwitz in the following articles: 1. http://www.oreillynet.com/onlamp/blog/2008/02/jeff_horwitz_on_mod_perl6.html 2. http://www.smashing.org/jeff/node/21 3. http://www.smashing.org/jeff/node/35 But I can't find any ppds on this. Probably will work in progress?
Re: mod_perl configuration
sandhya pawar wrote: > mod_perl.so has been successfully installed to > C:/PROGRA~1/APACHE~1/Apache2.2/modules. > To enable mod_perl, put in the directives >LoadFile "C:/Path/to/Perl/bin/perl510.dll" >LoadModule perl_module modules/mod_perl.so > in httpd.conf. For more information, visit >http://perl.apache.org/ > and especially see >http://perl.apache.org/docs/2.0/rename.html > > done Including LoadFile prior to LoadModule? > But it gives the error when I adds the following line in httpd.conf? > > LoadModule perl_module modules/mod_perl.so > > Error: > The request operation has failed. What does httpd -t say? What does your error log say? What does your windows application event log say about httpd?
mod_perl configuration
operating System: Vista ActivePerl5.10 Apache 2.2.11 mod_perl2.004 Mod_perl has been installed successfully for Perl5.10. C:\>ppm install http://cpan.uwinnipeg.ca/PPMPackages/10xx/mod_perl.ppd Downloading mod_perl-2.04...done Unpacking mod_perl-2.04...done Generating HTML for mod_perl-2.04...done Updating files in site area...done Downloading mod_perl-2.04 install script...done Running mod_perl-2.04 install script... The Apache2 module mod_perl.so is needed to complete the installation, and should be placed in your Apache2 modules directory. I will now fetch and install this for you. Fetching http://cpan.uwinnipeg.ca/PPMPackages/10xx/x86/mod_perl.so ... done! Where should mod_perl.so be placed? [D:/Apache2.2/modules] C:\Program Files\Apac he Software Foundation\Apache2.2\modules\ mod_perl.so has been successfully installed to C:/PROGRA~1/APACHE~1/Apache2.2/mo dules. To enable mod_perl, put in the directives LoadFile "C:/Path/to/Perl/bin/perl510.dll" LoadModule perl_module modules/mod_perl.so in httpd.conf. For more information, visit http://perl.apache.org/ and especially see http://perl.apache.org/docs/2.0/rename.html done But it gives the error when I adds the following line in httpd.conf? LoadModule perl_module modules/mod_perl.so Error: The request operation has failed. Is there need to add the above line in httpd.conf?
