Return-Path: 
 <users-return-103900-apmail-httpd-users-archive=httpd.apache.org@httpd.apache.org>
X-Original-To: apmail-httpd-users-archive@www.apache.org
Delivered-To: apmail-httpd-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id E232E998E
	for <apmail-httpd-users-archive@www.apache.org>;
 Thu,  7 Jun 2012 00:49:39 +0000 (UTC)
Received: (qmail 74571 invoked by uid 500); 7 Jun 2012 00:49:36 -0000
Delivered-To: apmail-httpd-users-archive@httpd.apache.org
Received: (qmail 74550 invoked by uid 500); 7 Jun 2012 00:49:36 -0000
Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
list-help: <mailto:users-help@httpd.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@httpd.apache.org>
List-Post: <mailto:users@httpd.apache.org>
List-Id: <users.httpd.apache.org>
Delivered-To: mailing list users@httpd.apache.org
Received: (qmail 74541 invoked by uid 99); 7 Jun 2012 00:49:36 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jun 2012 00:49:36 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [88.198.7.174] (HELO pless.xiqit.de) (88.198.7.174)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jun 2012 00:49:29 +0000
Received: from [192.168.12.34] (p50892C52.dip.t-dialin.net [80.137.44.82])
	by pless.xiqit.de (Postfix) with ESMTPSA id CB404DC0A9
	for <users@httpd.apache.org>; Thu,  7 Jun 2012 02:49:08 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mailathome.or.at;
	s=default; t=1339030148;
	bh=r8vg8DCZ31c/Nqi4mJTosd75steyYz6PxwmssDtd5Fk=;
	h=From:Content-Type:Content-Transfer-Encoding:Subject:Date:
	 Message-Id:To:Mime-Version;
	b=exBP6U+JS6+SohfA9lCmRAbmzCTn4ova0eLESNlrwkpPwK2FbDdu29x/gkiZ+ykfG
	 d66V/mDSBEonzaMwZCeOcFcwdo9rPRM/UGX2iwdK84QKlOfXnFNAaYwZ2drwpfuGMh
	 KZZIqv85KsMNFidXA8WDdUzSQUGAwZKrZfEiGkQg=
From: Konrad Neuwirth <konrad@mailathome.or.at>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Thu, 7 Jun 2012 02:49:12 +0200
Message-Id: <4DAF6CEE-13E2-4B8D-9FD8-61303B5DEF8C@mailathome.or.at>
To: users@httpd.apache.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Subject: [users@httpd] Problem with mod_proxy_fcgi

Dear reader,

I have a problem with mod_proxy_fcgi. More probably than not it's just =
me not having understood things, but I do hope somebody out there might =
be of help.=20

We are running php-fpm against apache 2.4.2, and are quite happy with =
that. Alas, one of our sites is using a CMS that generates URLs of the =
form=20

hostname/index.php/directory/page

So this means that our=20

<LocationMatch \.(.*\.php)$>
  ProxyPass fcgi://127.0.0.1/...
</LocationMatch>

Rule of course does not catch the link.=20

But changing that to=20

<LocationMatch \.php>
  ProxyPass
</LocationMatch>

Also didn't solve the problem.=20

How can I get those request properly forwarded to the php-fpm process =
pool?=20

Thank you!
 Konrad=

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org