Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51079
Return-Path: <danielc@analysisandsolutions.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 95364 invoked from network); 18 Dec 2010 19:05:31 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 18 Dec 2010 19:05:31 -0000
Authentication-Results: pb1.pair.com smtp.mail=danielc@analysisandsolutions.com; spf=permerror; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=danielc@analysisandsolutions.com; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain analysisandsolutions.com from 166.84.1.73 cause and error)
X-PHP-List-Original-Sender: danielc@analysisandsolutions.com
X-Host-Fingerprint: 166.84.1.73 mail2.panix.com  
Received: from [166.84.1.73] ([166.84.1.73:65195] helo=mail2.panix.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 0F/54-05093-AF50D0D4 for <internals@lists.php.net>; Sat, 18 Dec 2010 14:05:31 -0500
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail2.panix.com (Postfix) with ESMTP id 4D79238E43
	for <internals@lists.php.net>; Sat, 18 Dec 2010 14:05:28 -0500 (EST)
Received: by panix5.panix.com (Postfix, from userid 14662)
	id 3451C24255; Sat, 18 Dec 2010 14:05:28 -0500 (EST)
Date: Sat, 18 Dec 2010 14:05:28 -0500
To: PHP Internals List <internals@lists.php.net>
Message-ID: <20101218190527.GA17792@panix.com>
References: <vmime.4d0cea96.6a1e.c940661aa2ef34f6@zarafa.edigitalresearch.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <vmime.4d0cea96.6a1e.c940661aa2ef34f6@zarafa.edigitalresearch.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [PHP-DEV] [PATCH] Add option to disable POST data processing
From: danielc@analysisandsolutions.com (Daniel Convissor)

Hi James:

On Sat, Dec 18, 2010 at 05:08:38PM +0000, James Butler wrote:
> What about people on shared hosting?

One option may be to put a <Limit POST> in an .htaccess file.

Oh, and keep in mind <Limit TOP_POSTING>.

--Dan

-- 
 T H E   A N A L Y S I S   A N D   S O L U T I O N S   C O M P A N Y
            data intensive web and database programming
                http://www.AnalysisAndSolutions.com/
 4015 7th Ave #4, Brooklyn NY 11232  v: 718-854-0335 f: 718-854-0409