Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:33040 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16814 invoked by uid 1010); 6 Nov 2007 19:06:40 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 16798 invoked from network); 6 Nov 2007 19:06:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Nov 2007 19:06:40 -0000 Authentication-Results: pb1.pair.com header.from=stef@noc.uoa.gr; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=stef@noc.uoa.gr; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain noc.uoa.gr from 195.134.100.72 cause and error) X-PHP-List-Original-Sender: stef@noc.uoa.gr X-Host-Fingerprint: 195.134.100.72 msa.uoa.gr Received: from [195.134.100.72] ([195.134.100.72:37875] helo=msa.uoa.gr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 25/D4-31692-F3BB0374 for ; Tue, 06 Nov 2007 14:06:39 -0500 Received: by MSA with id CFFECE19639E02014695E52BD93F1030319F7724 Received: from webmail.noc.uoa.gr (webmail.noc.uoa.gr [195.134.100.73]) by msa.uoa.gr (8.14.1/8.14.1) with ESMTP id lA6J6aaf026733; Tue, 6 Nov 2007 21:06:36 +0200 (EET) Received: from 195.134.100.34 (SquirrelMail authenticated user stef) by webmail.uoa.gr with HTTP; Tue, 6 Nov 2007 21:06:36 +0200 (EET) Message-ID: <52993.195.134.100.34.1194375996.squirrel@webmail.uoa.gr> Date: Tue, 6 Nov 2007 21:06:36 +0200 (EET) Sender: "Stefanos Stamatis" To: internals@lists.php.net User-Agent: SquirrelMail/1.4.12 [SVN] [email.uoa.gr] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-7 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-UoAMSAId: CFFECE19639E02014695E52BD93F1030319F7724 Subject: Disabling the built-in POST handler From: stef@noc.uoa.gr ("Stefanos Stamatis") Trying to find a way to disable the built-in post form handler for the reasons discussed here: http://marc.info/?l=php-general&m=119160177617046&w=2 I looked at the code of php and found out that inside main/rfc1867.c in function rfc1867_post_handler there is a check whether the posted data content length exceeds the post_max_size parameter. If so it aborts the function (with a warning). (php-5.2.4, main/rfc1867.c, line 798) if (SG(request_info).content_length > SG(post_max_size)) { sapi_module.sapi_error(E_WARNING, "POST Content-Length of %ld bytes exceeds the limit of %ld bytes", SG(request_info).content_leng th, SG(post_max_size)); return; } So setting post_max_size to zero for the script with php_value in the apache configuration disables the built-in post form handler resulting in the desired behaviour! My question is whether this is the expected behavior of php that we can count on and can be used as a solution to our problem. Thanks in advance, Stefanos Stamatis.