Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70173
Return-Path: <rquadling@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 12753 invoked from network); 16 Nov 2013 11:54:35 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 16 Nov 2013 11:54:35 -0000
Authentication-Results: pb1.pair.com header.from=rquadling@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=rquadling@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.169 as permitted sender)
X-PHP-List-Original-Sender: rquadling@gmail.com
X-Host-Fingerprint: 209.85.223.169 mail-ie0-f169.google.com  
Received: from [209.85.223.169] ([209.85.223.169:43719] helo=mail-ie0-f169.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 04/00-12529-BFC57825 for <internals@lists.php.net>; Sat, 16 Nov 2013 06:54:35 -0500
Received: by mail-ie0-f169.google.com with SMTP id tp5so6481689ieb.28
        for <internals@lists.php.net>; Sat, 16 Nov 2013 03:54:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:reply-to:from:date:message-id:subject:to:content-type;
        bh=PQEsDZBS2YjAykJD2I7aCjP2+ugjSOrg6m24H4ocPQM=;
        b=JR2zUZ+jf0X/BeVz/XJjPahXxL/S7w4GrS1If2Eed7n7Wwe8DYGot+aGpsNkMIzdAL
         Dhth0XaTxlLpYrJto0bsBXyTG/aecITggdLzmiPu5uWz0zL59NQnD0t94JtB8QNff/NA
         MYksd9PRsXyeHDvd7kx0qxBCndGNnigbLuKh55jz5+VJVrWTrGlHEkBNNpDd50kgLweS
         scpHhdbZ05BPPRg+SaxbCes6g+8YqvAcT5vj3vH6BCJ2I4W+9zhjNVrByrq0+3fuJPQr
         6uZ4xa58p8MJuVbrsOpsxWclFKcHgEVevMssAM41g0308Qu+NovGzjmZGF8J6pNF1pV/
         Awkg==
X-Received: by 10.50.111.110 with SMTP id ih14mr7419633igb.58.1384602872081;
 Sat, 16 Nov 2013 03:54:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.223.10 with HTTP; Sat, 16 Nov 2013 03:54:11 -0800 (PST)
Reply-To: RQuadling@GMail.com
Date: Sat, 16 Nov 2013 13:54:11 +0200
Message-ID: <CAKUjMCWacU8UyGE6yRBPLMQJPgt-qjkD9_FRBgoOS8xHhxSZjA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0149bb8658746c04eb49fafb
Subject: Allowing [SAPI=] entries in ini files.
From: rquadling@gmail.com (Richard Quadling)

--089e0149bb8658746c04eb49fafb
Content-Type: text/plain; charset=UTF-8

Hi.

I created a patch https://github.com/php/php-src/pull/466 to allow ini
files to have a SAPI section, just like they can have a HOST and PATH
section.

My use case is that the provider we are currently using does not allow us
to have our own INI file, just the additional directory, and there is no
way to differentiate between a CLI and a FAST-CGI setup in the additional
directory.

The patch allows [SAPI=xxx] sections and they operate in a very similar way
to the [HOST] and [PATH] sections.

Please can this be considered for inclusion into PHP at some stage.

Regards,

Richard Quadling.

--089e0149bb8658746c04eb49fafb--