Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75134 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 64257 invoked from network); 29 Jun 2014 23:58:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jun 2014 23:58:55 -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.192.180 as permitted sender) X-PHP-List-Original-Sender: dz@heroku.com X-Host-Fingerprint: 209.85.192.180 mail-pd0-f180.google.com Received: from [209.85.192.180] ([209.85.192.180:64190] helo=mail-pd0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DF/B3-46378-D38A0B35 for ; Sun, 29 Jun 2014 19:58:54 -0400 Received: by mail-pd0-f180.google.com with SMTP id fp1so7262097pdb.11 for ; Sun, 29 Jun 2014 16:58:51 -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=4qf0VnJRp/YVIWOGtVa6RDo7rZImzvyCbz/TNIQPQsk=; b=fq2ROXJCr6oRmop41SU91d91MrsO5LYGUaAWzmzhVQpBkJVT5uXFGGisQzE9TETwCk MHP8VwR/HBzEsjIgAA3oRKCKuep3npQEivvOaKc4VSH8s/xmQ0hANdeAFZVgYJ4+HqB5 cZ1/FY2I+21h6EfBR4G6KxDyoRy6cs3gasj9lM+avbt55QrJ4Vofx/OkLtOJBYUdI5LX sBQyazpF2v3+/Q4JQu7YC1QB1PPt+gGpSfcZSPjVxPAGOSNtB7wNRR/XocAZdBbrm3M1 dJYoPQna007Tl9eme/YZsd0EGwtT7hAovcWFeO3LrIDGsUe1wyhpSZRC4NzEJZoEjMes lATA== X-Gm-Message-State: ALoCoQny/g7aRT99NoHmw+wfHBN3ayy5rb+A0gOPjUrtBKajQLjj83joM2OG3vYa76ljbmZYtpX6 X-Received: by 10.66.147.99 with SMTP id tj3mr48133119pab.47.1404086331513; Sun, 29 Jun 2014 16:58:51 -0700 (PDT) Received: from wombookair.local ([208.66.24.78]) by mx.google.com with ESMTPSA id io8sm24727201pbc.96.2014.06.29.16.58.50 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 29 Jun 2014 16:58:50 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) In-Reply-To: <6ED8D01A-F3B9-4149-AD6D-EC13368ADD6B@heroku.com> Date: Sun, 29 Jun 2014 16:58:48 -0700 Cc: Pierre Joye , Julien Pauli , Stas Malyshev , Antony Dovgal , Ilia Alshanetsky , PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: <8917D73E-2D54-4118-ABF3-48FC02915DD1@heroku.com> References: <035C7115-6871-4FC6-802E-464FD48070EF@heroku.com> <1C110716-6C9D-4EB8-97BA-2CEABE2C4847@heroku.com> <5A82BEA2-7D25-46B8-BFFF-6EB368B46190@heroku.com> <9A3A1383-B237-46FE-977B-A191A76C650A@heroku.com> <53AC5D29.3010707@sugarcrm.com> <8332CA5A-A255-4222-8C06-303813653CB4@heroku.com> <6ED8D01A-F3B9-4149-AD6D-EC13368ADD6B@heroku.com> To: Ferenc Kovacs 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 (to clarify: when using 2.4.10+ with SetHandler and the now merged PR, = the bug doesn't occur, but if people are using mod_rewrite, or = ProxyPass(Match), either because they don't know about the new method or = are stuck on older versions of Apache, bug 65641 is still relevant) On 29.06.2014, at 16:51, David Zuelke wrote: > Hi, >=20 > Thanks for the merge, but the just-merged PR addresses a different = issue than bug 65641. That one is still unaddressed. >=20 > The NEWS entry for the just-merged PR should be something like = "Support Apache 2.4.10+ SetHandler method for mod_proxy_fcgi and = PHP-FPM", and bug 65641 should be re-opened. >=20 > I'll see if I can look at the patches for bug 65641 again the next few = days; my gut feeling is that there should be a much easier way of fixing = this. After all, the patches all strip out parts of a string that = shouldn't be there in the first place. >=20 > David >=20 >=20 > On 27.06.2014, at 15:27, Ferenc Kovacs wrote: >=20 >>=20 >>=20 >>=20 >> On Fri, Jun 27, 2014 at 11:51 PM, David Zuelke wrote: >> On 27.06.2014, at 00:39, Pierre Joye wrote: >>=20 >>> On Jun 26, 2014 10:30 PM, "David Zuelke" wrote: >>>>=20 >>>> On 26.06.2014, at 12:23, Pierre Joye wrote: >>>>=20 >>>>> On Jun 26, 2014 9:12 PM, "David Zuelke" wrote: >>>>>>=20 >>>>>=20 >>>>>> That's what RCs are for, right? :) >>>>>=20 >>>>> In an ideal world with ideal users yes. >>>>>=20 >>>>> But we are not in that world :) >>>>=20 >>>> I know :) >>>>=20 >>>=20 >>> So what is wrong in putting us on the safe? Waiting 2 months max is = not that bad :) >>=20 >> Sure, but then it would be good to have this in the next 5.6 RC, = that'll probably get more testing exposure, too. >>=20 >> Either way, someone should please commit it into some branch soon ;) >>=20 >> David >>=20 >>=20 >> Was waiting for Stas to reply, I will merge it into 5.6 this weekend = if he doesn't reply that he wants to merge it into 5.4, then we can test = it with the 5.6RCs and merge back to 5.4/5.5. >>=20 >> --=20 >> Ferenc Kov=E1cs >> @Tyr43l - http://tyrael.hu >=20