I haven't been following this thread too closely, but is there a
reason you aren't using PerlHandlers instead of ModPerl::Registry?
MP::R is meant mostly for CGI migration, so it is probably not widely
tested with Apache2::SubProcess calls. I'd suggest trying your
external call under a PerlHandler
Seriously, you know what, the code below doesn't even work.
And if I get rid of the redirect and replace it with some nice pretty text:
print "Content-type: text/html\n\nTesting";
You know what? The warning for 1 (from the 'for' loop) is printed and
then it all stops, probably as the browser
On Fri, Feb 19, 2010 at 5:47 AM, michael kapelko wrote:
> When invoked directly by the shell or in web page WITHOUT "PerlHandler
> Apache::Registry", the UTF-8 encoded string in Russian is printed just
> fine. But when "PerlHandler Apache::Registry" is used, only are
> printed in web page.
C
Hello.
Here's a short script I used to find out the problem with the Apache::Registry:
#!/usr/bin/perl -wT
use strict;
use warnings;
use CGI;
use DBI;
use DBI qw(:sql_types);
use encoding 'utf-8';
my $cgi = new CGI;
print $cgi->header(-type => "text/html",
-charset => "utf-8"
Hi i asume you using xamp and test.gif is a simple git picture?
The apache webserver will try to execute
myserver.com/cgi-bin/mydir/test.gif
put the picture anywhere else (eg C:\xampp\htdocs\mydir\).
Maybe there are some more infos in your log file (eg.
C:\xampp\apache\logs\error.log)
You ca
