This is a multi-part message in MIME format.
--------------090004030902090109070803
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Okay, it's been a while, despite the name, that I've done any serious
playing around with MP. Since 1.0. I've just installed and gotten
running MP 2.0 on Apache 2.2.8... I'm doing the "ground up" and trying
to get registry scripts working first and I've run into the following,
right-off-the-bat head scratchers:

(1) The documentation says that:


|ParseHeaders|


Scan output for HTTP headers, same functionality as mod_perl 1.0's
|PerlSendHeader|, but more robust. This option is usually needs to
be enabled for registry scripts which send the HTTP header with:

print "Content-type: text/html\n\n";


Doesn't work for me... When I run registry scripts using in httpd.conf:

Alias /mp "/var/www/mp"
PerlModule ModPerl::Registry

SetHandler perl-script
Options +ExecCGI
PerlHandler ModPerl::Registry
*PerlOptions ParseHeaders*
Order allow,deny
Allow from all


The content-type is never sent and the response delivers text/plain -- I
see the HTML in plain text. When I go back to the MP 1.0 way in
httpd.conf, it works:

Alias /mp "/var/www/mp"
PerlModule ModPerl::Registry

SetHandler perl-script
Options +ExecCGI
PerlHandler ModPerl::Registry
*PerlSendHeader On*
Order allow,deny
Allow from all


What's the story here....?

ALSO...

(2) It took me a while to figure out that Apache::Registry has become
ModPerl::Registry. I saw nothing and still see nothing in the MP 2.0
docs about this, what I would consider MAJOR change, and as I said, it
took me a while to realize what happened here... What gives? What was
wrong with Apache::Registry???

I had Stas' book, which I know was written during MP 1.0, so between
these two things, it leaves me wondering how much more of the book is
now practically worthless?? I'm fast beginning to feel MP 2.0 has now
become the domain of "old MP 1.0 hands" and if you didn't follow MP from
1.0 days -- which I did not in a consistent way, then you are out of
luck... Where can I get the latest MP 2.0 beef? I think the MP 2.0
documentation at perl.apache.org leaves a lot to be desired...

Anyways, if someone can explain the ParseHeaders versus PerlSendHeader
and the ModPerl::Registry versus Apache::Registry changes, that would
help at least get registry scripts running in the optimal way. If the
MP 2.0 docs say that ParseHeaders is better, than I'd like to be able to
use it, but right now, it doesn't seem to work as the docs say. :-(

-PJ


--------------090004030902090109070803
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit






Okay, it's been a while, despite the name, that I've done any serious
playing around with MP.  Since 1.0.  I've just installed and gotten
running MP 2.0 on Apache 2.2.8...  I'm doing the "ground up" and trying
to get registry scripts working first and I've run into the following,
right-off-the-bat head scratchers:



(1) The documentation says that:


href="http://perl.apache.org/docs/2.0/user/config/config.html#toc_C_ParseHeaders_">ParseHeaders


Scan output for HTTP headers, same functionality as mod_perl 1.0's
PerlSendHeader, but more robust. This option is usually
needs to
be enabled for registry scripts which send the HTTP header with:


  print "Content-type: text/html\n\n";




Doesn't work for me...  When I run registry scripts using in httpd.conf:



    Alias /mp "/var/www/mp"

    PerlModule ModPerl::Registry

    <Directory "/var/www/mp">

       SetHandler perl-script

       Options +ExecCGI

       PerlHandler ModPerl::Registry

       PerlOptions ParseHeaders

       Order allow,deny

       Allow from all

    </Directory>



The content-type is never sent and the response delivers text/plain --
I see the HTML in plain text.  When I go back to the MP 1.0 way in
httpd.conf, it works:



    Alias /mp "/var/www/mp"

    PerlModule ModPerl::Registry

    <Directory "/var/www/mp">

       SetHandler perl-script

       Options +ExecCGI

       PerlHandler ModPerl::Registry

       PerlSendHeader On

       Order allow,deny

       Allow from all

    </Directory>



What's the story here....?



ALSO...



(2) It took me a while to figure out that Apache::Registry has become
ModPerl::Registry.  I saw nothing and still see nothing in the MP 2.0
docs about this, what I would consider MAJOR change, and as I said, it
took me a while to realize what happened here...  What gives?  What was
wrong with Apache::Registry???



I had Stas' book, which I know was written during MP 1.0, so between
these two things,  it leaves me wondering how much more of the book is
now practically worthless??  I'm fast beginning to feel MP 2.0 has now
become the domain of "old MP 1.0 hands" and if you didn't follow MP
from 1.0 days -- which I did not in a consistent way, then you are out
of luck...  Where can I get the latest MP 2.0 beef?  I think the MP 2.0
documentation at perl.apache.org leaves a lot to be desired...



Anyways, if someone can explain the ParseHeaders versus PerlSendHeader
and the ModPerl::Registry versus Apache::Registry changes, that would
help at least get registry scripts running in the optimal way.  If the
MP 2.0 docs say that ParseHeaders is better, than I'd like to be able
to use it, but right now, it doesn't seem to work as the docs say. :-(



-PJ






--------------090004030902090109070803--