Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75064
Return-Path: <dz@heroku.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 32319 invoked from network); 24 Jun 2014 22:15:33 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 24 Jun 2014 22:15:33 -0000
Authentication-Results: pb1.pair.com smtp.mail=dz@heroku.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=dz@heroku.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 209.85.160.43 as permitted sender)
X-PHP-List-Original-Sender: dz@heroku.com
X-Host-Fingerprint: 209.85.160.43 mail-pb0-f43.google.com  
Received: from [209.85.160.43] ([209.85.160.43:35995] helo=mail-pb0-f43.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 57/C2-39652-188F9A35 for <internals@lists.php.net>; Tue, 24 Jun 2014 18:15:30 -0400
Received: by mail-pb0-f43.google.com with SMTP id um1so799048pbc.30
        for <internals@lists.php.net>; Tue, 24 Jun 2014 15:15:26 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:content-type:mime-version:subject:from
         :in-reply-to:date:cc:content-transfer-encoding:message-id:references
         :to;
        bh=lffnLw++e35Ke/fYc0fVDNsoM+zqYKneuAxj0ZntBow=;
        b=BL7Mzl9yQDwBYeio3Wd/EEo3HN+L5pXCauVa6H3fte6rlsDHdQSnd/EdHzrFG2MOIH
         Pd0Ve07aB3jKphL7UPDfZnlewg7iCj3XcCNKlrMmxjh97bvqKxfOWlHuLJrnup37grfE
         cjL5to7WodunfqIzuCZeHh3T8y2c40zwJQT/0Em2zbAOFT2W/7XlZXFRY3K7whanpOMR
         yryKPjjQ1T610+w/V62417eYVLjbG7FgCX/HW2wF9O96utxyunICq+XIJIP9vCJW8FTd
         NOfdmPuyVThLObfwDGoPdF3Xyd5eRk7nNJBpf3gOZBR7e293r3siyJ/jrfx0PvCm7HuL
         WTZQ==
X-Gm-Message-State: ALoCoQm+bN4c/w6XLM86uOr9DXq+/qnfRQAefRJP3VNlPsm5iDFoaeig9cvLxuEIGMiYcBi43WYd
X-Received: by 10.66.158.132 with SMTP id wu4mr5669054pab.66.1403648126820;
        Tue, 24 Jun 2014 15:15:26 -0700 (PDT)
Received: from [10.100.38.215] ([152.179.69.246])
        by mx.google.com with ESMTPSA id ee5sm1991652pbc.47.2014.06.24.15.15.25
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Tue, 24 Jun 2014 15:15:26 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
In-Reply-To: <5A82BEA2-7D25-46B8-BFFF-6EB368B46190@heroku.com>
Date: Tue, 24 Jun 2014 15:15:24 -0700
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <9A3A1383-B237-46FE-977B-A191A76C650A@heroku.com>
References: <035C7115-6871-4FC6-802E-464FD48070EF@heroku.com> <CAH-PCH4TWkYUE3EN8JmLByVZB-Y3OB1b5izeYGtJXbgBNBN2dw@mail.gmail.com> <CAMUwpuTerXZb68mqbzRDeozgnW-BOauamsVmFfn6cJMxQ5PJGg@mail.gmail.com> <CAEZPtU6QG6Si9oetv29Ot_uXmCmmQynE4=vb--oA1QBGqSM7CA@mail.gmail.com> <1C110716-6C9D-4EB8-97BA-2CEABE2C4847@heroku.com> <5A82BEA2-7D25-46B8-BFFF-6EB368B46190@heroku.com>
To: Ilia Alshanetsky <ilia@prohost.org>,
 Julien Pauli <jpauli@php.net>,
 Ferenc Kovacs <tyra3l@gmail.com>,
 Pierre Joye <pierre.php@gmail.com>,
 Stas Malyshev <smalyshev@sugarcrm.com>
X-Mailer: Apple Mail (2.1510)
Subject: Re: [PHP-DEV] Fixing (and making easier) Apache mod_proxy_fcgi with PHP-FPM
From: dz@heroku.com

The change is now in Apache 2.4.x =
(http://svn.apache.org/viewvc?view=3Drevision&revision=3D1604378) and =
they're planning a release soon: =
http://thread.gmane.org/gmane.comp.apache.devel/53822

Can someone please at least merge the pull request? Would be a shame IMO =
if this didn't make it into 5.6.0.

I'll gladly provide docs for this, too.

David


On 20.06.2014, at 07:11, dz@heroku.com wrote:

> Bump?
>=20
> We've been running http://github.com/php/php-src/pull/694 in =
production at Heroku for a while now, with no issues.
>=20
> I really think this should be in 5.6, too. It'll make setting up =
PHP-FPM so much less painful on Apache once their new release is out.
>=20
> And if someone could also please review and commit =
https://bugs.php.net/bug.php?id=3D65641 (or find a better way; I'll be =
glad to help with anything like setting up Apache accordingly etc), then =
even with current versions of Apache, PHP will finally work fine. =
Currently, quite a few frameworks etc that use (or rewrite to) PATH_INFO =
are plainly broken.
>=20
> Thanks,
>=20
> David
>=20
>=20
> On 17.06.2014, at 14:33, David Zuelke <dz@heroku.com> wrote:
>=20
>> On 13.06.2014, at 17:19, Pierre Joye <pierre.php@gmail.com> wrote:
>>=20
>>> On Fri, Jun 13, 2014 at 9:30 AM, Julien Pauli <jpauli@php.net> =
wrote:
>>>> On Thu, Jun 12, 2014 at 10:11 PM, Ferenc Kovacs <tyra3l@gmail.com> =
wrote:
>>>>>>=20
>>>>>> Could we still squeeze this fix into 5.2.14? I know you just =
rolled RC1
>>>>>> (while I was fiddling with this stuff), but it would be so, so =
huge to have
>>>>>> this in=85 or at least in 5.2.15.
>>>>>>=20
>>>>>=20
>>>>> just to prevent confusion, you meant 5.5.14 and 5.5.15 here.
>>>>=20
>>>> Obviously 5.5.X yes.
>>>>=20
>>>> I myself answered that I dont see any criticity to roll out an RC2 =
for
>>>> 5.5.14, just for this specific bug.
>>>> I think it can go to 5.5.15 or any version as far as the patch is
>>>> tested and merged up.
>>>=20
>>> Given the security issues fixes waiting to be released, I would not
>>> delay the releases any longer.
>>=20
>> So, who wants to merge the PR? :)
>>=20
>> And if someone could review and possibly apply any of the =
https://bugs.php.net/bug.php?id=3D65641 attachments that'd be great too, =
although I suspect that it's possible to fix the problem way further up =
in the code so that this stripping of stuff isn't even necessary at such =
a "late" stage.
>>=20
>> With those two out of the way, PHP-FPM and Apache will be a lot, lot =
easier to set up together. One bit of config, done.
>>=20
>> David
>>=20
>> P.S. would be great for 5.4 too I think, not just 5.5+!
>>=20
>>=20
>=20