Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44117 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66153 invoked from network); 1 Jun 2009 22:37:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jun 2009 22:37:11 -0000 Authentication-Results: pb1.pair.com header.from=andrei@gravitonic.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=andrei@gravitonic.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain gravitonic.com from 209.85.222.199 cause and error) X-PHP-List-Original-Sender: andrei@gravitonic.com X-Host-Fingerprint: 209.85.222.199 mail-pz0-f199.google.com Received: from [209.85.222.199] ([209.85.222.199:32984] helo=mail-pz0-f199.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 50/A7-27635-618542A4 for ; Mon, 01 Jun 2009 18:37:11 -0400 Received: by pzk37 with SMTP id 37so1692811pzk.29 for ; Mon, 01 Jun 2009 15:37:07 -0700 (PDT) Received: by 10.142.246.19 with SMTP id t19mr2258714wfh.216.1243895827262; Mon, 01 Jun 2009 15:37:07 -0700 (PDT) Received: from barley.local (64-71-7-198.static.wiline.com [64.71.7.198]) by mx.google.com with ESMTPS id 30sm1865429wfc.38.2009.06.01.15.37.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 01 Jun 2009 15:37:05 -0700 (PDT) Message-ID: <4A245810.20503@gravitonic.com> Date: Mon, 01 Jun 2009 15:37:04 -0700 User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807) MIME-Version: 1.0 To: PHP internals Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: ext/filter and rfc1867 problem From: andrei@gravitonic.com (Andrei Zmievski) I ran into an issue today that seems to be a genuine bug. In rfc1867.c there is code like this: if (sapi_module.input_filter(PARSE_POST, param, &value, value_len, &new_val_len TSRMLS_CC)) { /* register the variable */ } The sapi_module.input_filter points to php_sapi_filter(). That return value of that function is based on "retval" variable which defaults to 0 at the top of the function and is set to 1 only when arg is PARSE_STRING. The end result is that it returns 0 and rfc1867 handler never registers the variable. Am I totally missing something or is this a real bug? -Andrei