Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75065 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34899 invoked from network); 24 Jun 2014 22:55:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jun 2014 22:55:22 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.172 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.216.172 mail-qc0-f172.google.com Received: from [209.85.216.172] ([209.85.216.172:48524] helo=mail-qc0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9C/23-39652-7D10AA35 for ; Tue, 24 Jun 2014 18:55:19 -0400 Received: by mail-qc0-f172.google.com with SMTP id o8so983390qcw.17 for ; Tue, 24 Jun 2014 15:55:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Urfma/ILtVgWGMtwZ9P724qNnrb+QL+CGYm6Xah1jnQ=; b=WkiaEe9z6/fhEpE8iZ2Ge1pbehosTANTaF/rqOqEIHbhELxzhrPjt8wjbm3hkZmVLr vZB+Gu3qhXa8JBD53n+hOoWK9NNMikbPhH25WKJlwDDnII3eGCxZIU039dZVeZzQLQHk c21uEBsZzJ3CbyhYdneqp7XapX0GQcqXdoWATakEKi0CihK/kioImMN7daspWGIcqZos mQC5RrDX4tCzQO+ddois+lwnPHq/DKzTyr+53udEkPzbYIYHTuiT6VUVjOmX05CqSI2C a9zg5D35RKXJ5MaLa5w+ZMS4DxXkJZ3kGy+mLF5U2rPZ/yLxD+WWT7EcpkcnMb+KdRnT pK5A== MIME-Version: 1.0 X-Received: by 10.229.70.196 with SMTP id e4mr6563151qcj.16.1403650516192; Tue, 24 Jun 2014 15:55:16 -0700 (PDT) Received: by 10.140.25.36 with HTTP; Tue, 24 Jun 2014 15:55:16 -0700 (PDT) In-Reply-To: <9A3A1383-B237-46FE-977B-A191A76C650A@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> Date: Wed, 25 Jun 2014 00:55:16 +0200 Message-ID: To: David Zuelke , julien pauli Cc: Ilia Alshanetsky , Pierre Joye , Stas Malyshev , PHP internals Content-Type: multipart/alternative; boundary=001a1133bb5868145204fc9cda4e Subject: Re: [PHP-DEV] Fixing (and making easier) Apache mod_proxy_fcgi with PHP-FPM From: tyra3l@gmail.com (Ferenc Kovacs) --001a1133bb5868145204fc9cda4e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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)? 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 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? > > > > We've been running http://github.com/php/php-src/pull/694 in production > 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-FP= M > 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 gl= ad > 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. > > > > 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 rolle= d > RC1 > >>>>>> (while I was fiddling with this stuff), but it would be so, so hug= e > 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 f= or > >>>> 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 too, > although I suspect that it's possible to fix the problem way further up i= n > 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+! > >> > >> > > > > --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --001a1133bb5868145204fc9cda4e--