Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75067 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68606 invoked from network); 25 Jun 2014 09:13:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jun 2014 09:13:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=julienpauli@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=julienpauli@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.182 as permitted sender) X-PHP-List-Original-Sender: julienpauli@gmail.com X-Host-Fingerprint: 209.85.128.182 mail-ve0-f182.google.com Received: from [209.85.128.182] ([209.85.128.182:37729] helo=mail-ve0-f182.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F5/51-55756-AA29AA35 for ; Wed, 25 Jun 2014 05:13:15 -0400 Received: by mail-ve0-f182.google.com with SMTP id oy12so1662491veb.13 for ; Wed, 25 Jun 2014 02:13:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=AaHUiFygQjVWPU+z42BXV+BQzo+TIthNkK88bUAomNQ=; b=E+2rijGbOMvGanRM65vIIxi70OWAUevBFSIzggmib8EVpKS9GyZrTtgH2dUJ1Diayy d2UdCHxL32ztc0nCTif8gtUXGtCcNOjhiveDJA450mrG40wUV+UJ+PzU6UCuCdy/MsWJ qG6UMd7o5WBRi+RxlsT8UMthqlwNrCJrC3+x3ipnK10lGpgIxTw9qWdMJjkSyNvu52Dl g9SXlh7qGkj+Od6Ey3aPliK9gngWAPeOQuiJPtSLBJwQdC5/ivGCL9GbjdnOT1D4hJcX tYeqy7V6KbvkFlQ5KO3ico6DN0edhSKMJNjuQ0fOc8zM3YKu9R1U+oi4c4WEoCNdz/OG YIow== X-Received: by 10.220.105.136 with SMTP id t8mr5752097vco.13.1403687592193; Wed, 25 Jun 2014 02:13:12 -0700 (PDT) MIME-Version: 1.0 Sender: julienpauli@gmail.com Received: by 10.220.81.68 with HTTP; Wed, 25 Jun 2014 02:12:31 -0700 (PDT) In-Reply-To: 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> Date: Wed, 25 Jun 2014 11:12:31 +0200 X-Google-Sender-Auth: K33GvZB08RujonTFqyIXlVv7lKY Message-ID: To: Ferenc Kovacs Cc: David Zuelke , Ilia Alshanetsky , Pierre Joye , Stas Malyshev , PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Fixing (and making easier) Apache mod_proxy_fcgi with PHP-FPM From: jpauli@php.net (Julien Pauli) On Wed, Jun 25, 2014 at 12:55 AM, Ferenc Kovacs wrote: > Julien, do you have any problem merging this PR to PHP-5.5(and merging > upwards) so it can be released with 5.5.15 (and with 5.6.0RC2)? Don't we take 5.4 as basis ? Julien > > > On Wed, Jun 25, 2014 at 12:15 AM, wrote: >> >> The change is now in Apache 2.4.x >> (http://svn.apache.org/viewvc?view=3Drevision&revision=3D1604378) and th= ey'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? >> > >> > We've been running http://github.com/php/php-src/pull/694 in productio= n >> > at Heroku for a while now, with no issues. >> > >> > I really think this should be in 5.6, too. It'll make setting up PHP-F= PM >> > so much less painful on Apache once their new release is out. >> > >> > 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, qui= te a >> > few frameworks etc that use (or rewrite to) PATH_INFO are plainly brok= en. >> > >> > Thanks, >> > >> > David >> > >> > >> > On 17.06.2014, at 14:33, David Zuelke wrote: >> > >> >> On 13.06.2014, at 17:19, Pierre Joye wrote: >> >> >> >>> On Fri, Jun 13, 2014 at 9:30 AM, Julien Pauli wrote= : >> >>>> On Thu, Jun 12, 2014 at 10:11 PM, Ferenc Kovacs >> >>>> wrote: >> >>>>>> >> >>>>>> Could we still squeeze this fix into 5.2.14? I know you just roll= ed >> >>>>>> RC1 >> >>>>>> (while I was fiddling with this stuff), but it would be so, so hu= ge >> >>>>>> to have >> >>>>>> this in=E2=80=A6 or at least in 5.2.15. >> >>>>>> >> >>>>> >> >>>>> just to prevent confusion, you meant 5.5.14 and 5.5.15 here. >> >>>> >> >>>> Obviously 5.5.X yes. >> >>>> >> >>>> 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. >> >>> >> >>> Given the security issues fixes waiting to be released, I would not >> >>> delay the releases any longer. >> >> >> >> So, who wants to merge the PR? :) >> >> >> >> And if someone could review and possibly apply any of the >> >> https://bugs.php.net/bug.php?id=3D65641 attachments that'd be great t= oo, >> >> 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. >> >> >> >> 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. >> >> >> >> David >> >> >> >> P.S. would be great for 5.4 too I think, not just 5.5+! >> >> >> >> >> > >> > > > > -- > Ferenc Kov=C3=A1cs > @Tyr43l - http://tyrael.hu