Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20969 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 59044 invoked by uid 1010); 1 Dec 2005 17:31:34 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 59028 invoked from network); 1 Dec 2005 17:31:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Dec 2005 17:31:34 -0000 X-Host-Fingerprint: 195.197.172.116 gw02.mail.saunalahti.fi Linux 2.4/2.6 Received: from ([195.197.172.116:53553] helo=gw02.mail.saunalahti.fi) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id C5/8E-14828-4733F834 for ; Thu, 01 Dec 2005 12:31:32 -0500 Received: from nest.netphobia.fi (YZDCXXXI.dsl.saunalahti.fi [85.76.35.232]) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id 46B03D94EC; Thu, 1 Dec 2005 19:31:27 +0200 (EET) Received: from nest.netphobia.fi (nest.netphobia.fi [127.0.0.1]) by nest.netphobia.fi (8.13.1/8.13.1) with ESMTP id jB1HVTpL000701; Thu, 1 Dec 2005 19:31:29 +0200 Received: from localhost (jani@localhost) by nest.netphobia.fi (8.13.1/8.13.1/Submit) with ESMTP id jB1HVSl6000698; Thu, 1 Dec 2005 19:31:29 +0200 X-Authentication-Warning: nest.netphobia.fi: jani owned process doing -bs Date: Thu, 1 Dec 2005 19:31:28 +0200 (EET) Reply-To: Jani Taskinen To: Ben Ramsey cc: internals@lists.php.net In-Reply-To: <438F1C6A.70400@php.net> Message-ID: References: <438D5B2E.3030203@php.net> <438F1C6A.70400@php.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [PHP-DEV] filter extension From: sniper@iki.fi (Jani Taskinen) On Thu, 1 Dec 2005, Ben Ramsey wrote: >> Definately experimental. It still crashes for me when >> I pass something like ?foo=
in either POST or GET. :) > > I've submitted a patch for this problem here: > http://pecl.php.net/bugs/bug.php?id=6124 And patch applied, thanks. > Are there any other known issues besides this one that continue to render this > extension as experimental? Not that I know right now, but it's still experimental. --Jani