I'm still hoping for a good answer on my previous build problem.
But for now I'm proceeding with testing using the mod_perl that
my hosting provider set up.
The first script that I've tested that uses Apache2::Request gives
a problem. The browser sits and waits for its timeout period,
then the complete expected response is available. My limited
experience suggests this is probably because the response's
content-length value is fouled up (or the header isn't sent?).
My "server signature" is
Apache/2.2.3 (Unix) mod_ssl/2.2.3 OpenSSL/0.9.7e-p1
mod_apreq2-20051231/2.5.7 mod_perl/2.0.2 Perl/v5.8.7 Server at
mackenna1.securesites.net
OS is FreeBSD 6. The problem happens under both http: and https:.
mod_deflate and mod_include are also active for the transaction.
Anyone can see the problem at
http://mackenna1.securesites.net/contact.html
which is the site's contact form. If you just hit "send" without
entering
anything, you'll get a response that says you didn't enter anything,
but it will take a long time.
Apache2::Request had bigger problems until I included the following
line in httpd.conf:
LoadModule apreq_module modules/mod_apreq2.so
That .so was also provided by my hosting provider (Verio).
Does this sound familiar? Could it be avoided by newer versions of
any of the software?
Craig MacKenna
Los Gatos, CA
