i am not much of a mp hacker but as I understand it, one problem with
making per-session persistent connections would be that there is no guarantee
that future requests in the same apache session will be handled by the same
mod_perl process. This means that any backend that provided what you are
Hi everybody. I ran into a problem with Perl scripts stored in utf-8 and I
couldn't find the answer to it on the Internet or mailing lists. Please tell me
what I'm missing.
SYSTEM: Windows XP SP2, Active Perl 5.8.4.810, Apache 2.048, mod_perl 1.9912.
I need to run scripts stored in utf-8. Here
wrote:
I use the Windows' Notepad and save the file as utf-8. Everything works fine
while I run the script from the command line or through CGI without mod_perl.
PROBLEM: When I try to run the script using mod_perl, I get the following ERROR:
[error] 3320: ModPerl::PerlRun: Unrecognized
wrote:
Hi everybody. I ran into a problem with Perl scripts stored in utf-8
and I couldn't find the answer to it on the Internet or mailing lists.
Please tell me what I'm missing.
SYSTEM: Windows XP SP2, Active Perl 5.8.4.810, Apache 2.048, mod_perl
1.9912.
I need to run scripts stored in utf-8.
Thanks for your response. However at the moment what I needed was perl to work
on my webserver for testing purpose only on a global level. I found a way to
enable perl using an apache directive and bypassed mod_perl altogether. So for
the time being everything is fine. Thanks for you
Stas Bekman wrote:
It seems as if mod_perl doesn't recognize the format of the script file
correctly. Any tips why this may occur? Thanks a bundle in advance!
Wow! That's interesting.
Please take a look at the code in function
convert_script_to_compiled_handler at
Markus Wichitill wrote:
Stas Bekman wrote:
It seems as if mod_perl doesn't recognize the format of the script file
correctly. Any tips why this may occur? Thanks a bundle in advance!
Wow! That's interesting.
Please take a look at the code in function
convert_script_to_compiled_handler at
Stas Bekman wrote:
Markus Wichitill wrote:
The reason for the failure is pretty clear, the BOM ends up somewhere
in the middle of the string that is eval'ed to generate the package.
On Linux, I was able to fix that by removing the BOM in
RegistryCooker::read_script():
It's certainly a bad idea
Markus Wichitill wrote:
[...]
But first I would like to know why the script doesn't fail when run
outside mod_perl. We do nothing special here, other than read+eval,
compared to require. So it looks like a bug in perl.
No, Perl can deal with a BOM at the start of a file. But
Stas Bekman wrote:
Markus Wichitill wrote:
No, Perl can deal with a BOM at the start of a file. But
convert_script_to_compiled_handler() puts the BOM in the middle of the
string that is eval'ed. A bunch of raw bytes has no place in the
middle of a script.
Aha! Now it's clear. Thanks Markus.
Do
Markus Wichitill wrote:
Stas Bekman wrote:
Markus Wichitill wrote:
No, Perl can deal with a BOM at the start of a file. But
convert_script_to_compiled_handler() puts the BOM in the middle of
the string that is eval'ed. A bunch of raw bytes has no place in the
middle of a script.
Aha! Now it's
The uploaded file
Apache-SessionManager-1.03.tar.gz
has entered CPAN as
file: $CPAN/authors/id/E/EN/ENRYS/Apache-SessionManager-1.03.tar.gz
size: 30712 bytes
md5: 85b412074edde465fcf291a1fef0e5e2
Changes from previous version
-
* Adopted
This is a bug-fix version. Upgrade is recommended for all users.
It was noticed that Content-Type was overwritten to default text/html
during the streaming of some static files through the compression
because $r-header_out('Content-Type') was not set yet at the time when
$r-content_type indeed is
PerlHandler is a mod_perl 1 directive.
PerlResponseHnalder is a mod_perl 2 directive.
replace -- PerlHandler ModPerl::Registry with
PerlResponseHandler ModPerl::Registry
[EMAIL PROTECTED] wrote:
Hi,
I have probelms with modperl installation; have read through the manuals and
also mailing lists but
Cure wrote:
PerlHandler is a mod_perl 1 directive.
PerlResponseHnalder is a mod_perl 2 directive.
Both work just fine under mp2, unless compiled with MP_COMPAT_1X=0
http://perl.apache.org/docs/2.0/user/install/install.html#MP_COMPAT_1X
replace -- PerlHandler ModPerl::Registry with
15 matches
Mail list logo
