> I can confirm those results on my Apache2+Interchange::Link setup.
>
I haven't tested this, but I've been looking at the Interchange::Link
code and may have a lead.
Backup your Link.pm module and try the following patch:
*** Link.pm- Wed Jun 14 00:37:36 2006
--- Link.pm Wed Jun 14 00:39:13 2006
***************
*** 483,489 ****
#warn("Connection=$c");
- my (@tmp) = keys %ENV;
my ($str);
my $val = '';
my $count = 0;
--- 483,488 ----
***************
*** 558,564 ****
my $val = $r->headers_in->{$_};
my $k = uc $_;
$k =~ s/-/_/g;
- $k =~ s/-/_/g;
$k = $header_map{$k} || "HTTP_$k";
$header{$k} = $val;
#warn "header $_/$k=$val\n";
--- 557,562 ----
***************
*** 572,577 ****
--- 570,576 ----
QUERY_STRING => $query,
REMOTE_ADDR => $c->remote_ip,
%header,
+ %ENV,
);
while (@pairs) {
I've never used a patch so I removed the two "-" lines and added the "+" line manually according to the context and restarted apache2. It basically broke the site. When I tried to access a page it always came up blank. It's actually the same thing that happens intermittently with my site anyway. Normally, it seems to correspond with this in error_log: ALERT: bad pipe signal received for /whatever.file [Tue Jun 13 19:40:48 2006] [notice] child pid 31790 exit signal Segmentation fault (11) I'd be happy to test further if you'd like. - Grant _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.