Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36511 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40167 invoked from network); 25 Mar 2008 17:11:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Mar 2008 17:11:42 -0000 Authentication-Results: pb1.pair.com smtp.mail=gwang@litespeedtech.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=gwang@litespeedtech.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain litespeedtech.com designates 64.18.140.195 as permitted sender) X-PHP-List-Original-Sender: gwang@litespeedtech.com X-Host-Fingerprint: 64.18.140.195 mail.litespeedtech.com Received: from [64.18.140.195] ([64.18.140.195:41768] helo=mail.litespeedtech.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FB/92-28012-D4239E74 for ; Tue, 25 Mar 2008 12:11:42 -0500 Received: from ool-43515bdf.dyn.optonline.net ([67.81.91.223] helo=[192.168.0.154]) by mail.litespeedtech.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1JeCgO-0003gO-RK; Tue, 25 Mar 2008 13:11:38 -0400 Message-ID: <47E93244.4060001@litespeedtech.com> Date: Tue, 25 Mar 2008 13:11:32 -0400 User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: Pierre Joye CC: internals@lists.php.net References: <47E80EB9.60900@litespeedtech.com> <698DE66518E7CA45812BD18E807866CE0165A861@us-ex1.zend.net> <20080325100552.00o51usgg04oogw0@mail.litespeedtech.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -3.2 (---) X-Spam-Report: Spam detection software, running on the system "mail.litespeedtech.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see admin@litespeedtech.com for details. Content preview: Pierre, > As of php 5.3, it is possible to have a per directory configuration, > either using the system php.ini or using a .htaccess-like php.ini > (.user.ini). The concept is based on what you have in htscanner but in > a much better way (same syntax than in any php.ini). The goal is to > enable this feature in all SAPIs. > We do not use htscanner. [...] Content analysis details: (-3.2 points, 5.3 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP 1.1 SPF_FAIL SPF: sender does not match SPF record (fail) [SPF failed: Please see http://spf.pobox.com/why.html?sender=gwang%40litespeedtech.com&ip=67.81.91.223&receiver=mail.litespeedtech.com] -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.1 AWL AWL: From: address is in the auto white-list Subject: Re: [PHP-DEV] Inclusion of PHP LiteSpeed SAPI in the standard PHP distribution? From: gwang@litespeedtech.com (George Wang) Pierre, > As of php 5.3, it is possible to have a per directory configuration, > either using the system php.ini or using a .htaccess-like php.ini > (.user.ini). The concept is based on what you have in htscanner but in > a much better way (same syntax than in any php.ini). The goal is to > enable this feature in all SAPIs. > We do not use htscanner. LiteSpeed web server is fully compatible with Apache .htaccess configuration file, and we use a highly efficient htaccess cache to reduce the overhead of reload configuration in .htaccess for each request like what Apache does. PHP related configuration will be passed to PHP process through a IPC socket along with other request data. I am sure the new per directory configuration should work with LiteSpeed SAPI. However, if it needs to scan each directory repeatedly for each request, it will slow down PHP even further. Best Regards, George