Kinyon, Rob wrote:
t/filter/both_str_con_add.t 4 3 75.00% 2-4 t/protocol/echo.t 22 5632 3 2 66.67% 2-3 t/protocol/echo_filter.t 22 5632 3 2 66.67% 2-3
Interesting, all 3 test have one thing in common - they use a raw socket
to communicate with the client. So this is probably something that doesn't
work on your machine. Are there known socket problems in perl on your
platform?
---------------
No, there are not. I just tested it against my currently-running webserver and got a response back. I used the following script to test: ---- #!/usr/local/bin/perl
use IO::Socket::INET;
my $socket = IO::Socket::INET->new( PeerAddr => '127.0.0.1', PeerPort => '80', );
print "Socket: '$socket'\n";
print $socket "Hello\n"; chomp( my $reply = <$socket>); print "$reply\n";
Good. In which case libapr sockets could be broken. The client side does what you did in the test. The server side does:
sub handler {
my Apache::Connection $c = shift;
my APR::Socket $socket = $c->client_socket;my $buff;
for (;;) {
my($rlen, $wlen);
$rlen = BUFF_LEN;
$socket->recv($buff, $rlen);
last if $rlen <= 0;
$wlen = $rlen;
$socket->send($buff, $wlen);
last if $wlen != $rlen;
}Apache::OK; }
Someone on Solaris 8 needs to arm themselves with a debugger and step through the server side C code and check why doesn't it work.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
